How should we interpret CVSS severity scores?

CVSS estimates technical severity, but it does not automatically equal business risk. Prioritize using context like internet exposure, asset criticality, known exploitation, and whether compensating controls exist. A Medium CVSS on an exposed production system can be more urgent than a Critical on an isolated non-production host.

Vulnerability Database

Q: What is a Vulnerability (CVE) and why does it matter?

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

Q: What's the difference between a vulnerability, an exploit, and a zero-day?

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. Risk increases sharply when exploitation becomes reliable or widespread.

Q: Why do vulnerabilities keep reappearing in our environment?

Recurring findings usually come from incomplete asset discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host.

Q: How do we prioritize remediation without burning out the team?

Use a repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress so remediation is steady, not reactive.

Q: How can SynScan help reduce vulnerability risk over time?

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.

328,409

Total vulnerabilities in the database

Vulnerabilities for products matching "horizon"

Found 5 matching products. Filters apply to all results.

You can search for specific versions with /product/horizon/1.2.3

openstack / horizon

22 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2022-45582	Medium	August 22, 2023 8/22/23	>= 19.4.0 <= 20.1.4
CVE-2020-29565	Medium	December 4, 2020 12/4/20	>= 16.0.0 < 16.2.1 >= 17.0.0 < 18.3.3 >= 15.3.0 < 15.3.2 >= 18.4.0 <= 18.5.0
CVE-2012-5474	Medium	December 30, 2019 12/30/19	>= 2012.1 < 2012.1.1
CVE-2012-5476	Medium	December 30, 2019 12/30/19	== 2012.2
CVE-2017-7400	Low	April 3, 2017 4/3/17	== 9.0.0 == 9.1.1 == 9.0.0-b1 == 10.0.0-b3 == 10.0.0 == 9.0.0-rc1 == 11.0.0 == 9.0.0-rc2 == 10.0.1 == 10.0.0-rc1 == 10.0.0-b1 == 10.0.2 == 9.1.0 == 10.0.0-b2 == 9.0.0-b3 == 9.0.1 == 10.0.0-rc3 == 9.0.0-b2 == 10.0.0-rc2
CVE-2016-4428	Medium	July 12, 2016 7/12/16	== 9.0.0 == 9.0.1 >= 8.0.0 <= 8.0.1
CVE-2015-3219	Low	August 20, 2015 8/20/15	== 2014.2.1 == 2015.1.0 == 2014.2.0 == 2014.2.3 == 2014.2.2
CVE-2015-3988	Low	May 19, 2015 5/19/15	== 2015.1.0
CVE-2014-8124	Medium	December 12, 2014 12/12/14	>= 2014.1 < 2014.1.3 >= 2014.2.0 < 2014.2.1
CVE-2014-3474	Low	October 31, 2014 10/31/14	== juno-1 >= 2013.2 < 2013.2.4 >= 2014.1 < 2014.1.2
CVE-2014-3475	Low	October 31, 2014 10/31/14	== juno-1 >= 2013.2 < 2013.2.4 >= 2014.1 < 2014.1.2
CVE-2014-8578	Low	October 31, 2014 10/31/14	== juno-1 >= 2013.2 < 2013.2.4 >= 2014.1 < 2014.1.2 <= juno-1
CVE-2014-3473	Low	October 31, 2014 10/31/14	== juno-1 >= 2013.2 < 2013.2.4 >= 2014.1 < 2014.1.2
CVE-2014-3594	Low	August 22, 2014 8/22/14	== juno-1 == juno-2 >= 2013.2 < 2013.2.4 >= 2014.1 < 2014.1.2
CVE-2013-4471	Medium	May 14, 2014 5/14/14	>= 2013.1 < 2013.2
CVE-2014-0157	Low	April 15, 2014 4/15/14	== 2013.2.3 == 2013.2.2 == 2013.2.1 == 2013.2
CVE-2013-6858	Low	November 23, 2013 11/23/13	>= 2013.1 <= 2013.2
CVE-2012-3540	Medium	September 5, 2012 9/5/12	== 2012.1
CVE-2012-3542	Low	September 5, 2012 9/5/12	== folsom-3
CVE-2012-3426	Low	July 31, 2012 7/31/12	== folsom-1
CVE-2012-2094	Low	June 5, 2012 6/5/12	== 2012.1 == folsom-1
CVE-2012-2144	Medium	June 5, 2012 6/5/12	== 2012.1 == folsom-1

vmware / horizon

6 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2022-22962	High	April 11, 2022 4/11/22	< 2203
CVE-2022-22964	High	April 11, 2022 4/11/22	< 2203
CVE-2022-22938	Medium	January 28, 2022 1/28/22	>= 5.0.0 < 5.5.3
CVE-2020-3997	Medium	October 23, 2020 10/23/20	>= 7.11.0 < 7.13.0 >= 7.0 < 7.10.3
CVE-2019-5527	High	October 10, 2019 10/10/19	< 5.2.0
CVE-2019-5513	Medium	April 9, 2019 4/9/19	>= 6.0.0 < 6.2.8 >= 7.0 < 7.8 >= 7.5.0 < 7.5.2

opennms / horizon

22 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2023-40314	Medium	November 16, 2023 11/16/23	< 32.0.5
CVE-2023-40612	Medium	August 23, 2023 8/23/23	>= 31.0.8 < 32.0.2
CVE-2023-40315	Medium	August 17, 2023 8/17/23	>= 31.0.8 < 32.0.2
CVE-2023-40313	High	August 17, 2023 8/17/23	< 32.0.2
CVE-2023-40312	Medium	August 14, 2023 8/14/23	>= 31.0.8 < 32.0.2
CVE-2023-40311	Medium	August 14, 2023 8/14/23	>= 31.0.8 < 32.0.2
CVE-2023-0872	High	August 14, 2023 8/14/23	>= 31.0.8 < 32.0.2
CVE-2023-0871	Medium	August 11, 2023 8/11/23	>= 32.0.0 < 32.0.2 == 31.0.8
CVE-2023-0870	High	March 22, 2023 3/22/23	< 31.0.6
CVE-2023-0867	Medium	February 23, 2023 2/23/23	< 31.0.4
CVE-2023-0868	Medium	February 23, 2023 2/23/23	< 31.0.4
CVE-2023-0869	Medium	February 23, 2023 2/23/23	< 31.0.4
CVE-2023-0815	Medium	February 23, 2023 2/23/23	< 31.0.4
CVE-2023-0846	Medium	February 22, 2023 2/22/23	< 31.0.4
CVE-2021-25934	Medium	May 25, 2021 5/25/21	>= 18.0.0 <= 27.1.0
CVE-2021-25935	Medium	May 25, 2021 5/25/21	>= 17.0.0 <= 27.1.0
CVE-2021-25929	Low	May 20, 2021 5/20/21	>= 1.0 < 27.1.1
CVE-2021-25931	High	May 20, 2021 5/20/21	>= 1.0 < 27.1.1
CVE-2021-25933	Low	May 20, 2021 5/20/21	>= 1.0 < 27.1.1
CVE-2021-25930	Low	May 20, 2021 5/20/21	>= 1.0 < 27.1.1
CVE-2021-3396	High	February 17, 2021 2/17/21	>= 16.0.0 <= 27.0.3
CVE-2020-11886	High	April 17, 2020 4/17/20	< 25.2.1

horizon_project / horizon

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2014-125078	Low		January 15, 2023 1/15/23	< 2014-07-08

horizon

2 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2022-45582	Medium		August 22, 2023 8/22/23	< 19.4.0
CVE-2014-0157	Low		April 15, 2014 4/15/14	>= 2013.2 < 2013.2.4

Showing vulnerabilities for 5 products matching "horizon". Each product has independent pagination.

Deep Security Visibility Without the Complexity

SynScan provides clear, real-time security insights so you can monitor your attack surface, spot risks early, and act fast—without extra complexity.

No setup fees
5-min deployment
Cancel anytime

Book a Demo

Frequently Asked Questions

What is a Vulnerability (CVE) and why does it matter?

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

CVSS (Common Vulnerability Scoring System) estimates technical severity, but it doesn't automatically equal business risk. Prioritize using context like internet exposure, affected asset criticality, known exploitation (proof-of-concept or in-the-wild), and whether compensating controls exist. A "Medium" CVSS on an exposed, production system can be more urgent than a "Critical" on an isolated, non-production host.

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. In practice, risk increases sharply when exploitation becomes reliable or widespread.

Recurring findings usually come from incomplete Asset Discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host. Unknown or unmanaged assets (often called Shadow IT) are a common reason the same issues resurface.

Use a simple, repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress using consistent metrics so remediation is steady, not reactive.

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.