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.

352,427

Total vulnerabilities in the database

Vulnerabilities for products matching "neutron"

Found 2 matching products. Filters apply to all results.

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

openstack / neutron

91 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2022-3277	Medium	March 6, 2023 3/6/23	>= 19.0.0 < 19.5.0 < 18.6.0
CVE-2021-40797	High	September 8, 2021 9/8/21	< 16.4.1 >= 18.0.0 < 18.1.1 >= 17.0.0 < 17.2.1
CVE-2021-40085	High	August 31, 2021 8/31/21	< 16.4.1 >= 18.0.0 < 18.1.1 >= 17.0.0 < 17.2.1
CVE-2021-38598	High	August 23, 2021 8/23/21	== 18.0.0 < 16.4.1 >= 17.0.0 < 17.1.3
CVE-2021-20267	High	May 28, 2021 5/28/21	== 18.0.0 >= 17.0.0 < 17.1.3 < 16.3.3
CVE-2019-10876	High	April 5, 2019 4/5/19	>= 11.0.0 < 11.0.7 >= 12.0.0 < 12.0.6 >= 13.0.0 < 13.0.3
CVE-2019-9735	High	March 13, 2019 3/13/19	< 10.0.8 >= 11.0.0 < 11.0.7 >= 12.0.0 < 12.0.6 >= 13.0.0 < 13.0.3
CVE-2018-14635	High	September 10, 2018 9/10/18	>= 11.0.0 <= 11.0.5 == 13.0.0.0-b1 >= 12.0.0 <= 12.0.3
CVE-2018-14636	Medium	September 10, 2018 9/10/18	>= 12.0.0 <= 12.0.2 == 13.0.0-b1 >= 7.0.0 <= 11.0.4
CVE-2017-7543	Medium	July 26, 2018 7/26/18	>= 7.0.0 < 7.2.0-12.1 >= 8.0.0 < 8.3.0-11.1 >= 9.0.0 < 9.3.1-2.1 >= 10.0.0 < 10.0.2-1.1
CVE-2016-5363	High	June 17, 2016 6/17/16	== 7.0.1 == 8.0.0 == 7.0.2 == 7.0.3 == 7.0.4 == 8.1.0 == 7.0.0
CVE-2016-5362	High	June 17, 2016 6/17/16	>= 7.0.0 < 7.0.4 >= 8.0.0 <= 8.1.0
CVE-2015-8914	Critical	June 17, 2016 6/17/16	>= 7.0.0 < 7.0.4 >= 8.0.0 <= 8.1.0
CVE-2015-5240	Low	October 27, 2015 10/27/15	== 2015.1.1 == 2014.2.3 == 2015.1.0
CVE-2015-3221	Medium	August 26, 2015 8/26/15	>= 2014.2 < 2014.2.4 >= 2015.1.0 < 2015.1.1
CVE-2014-8153	Low	January 15, 2015 1/15/15	== 2014.2.1 == 2014.2
CVE-2014-7821	Low	November 24, 2014 11/24/14	>= 2014.2 < 2014.2.1 >= 2012.2.1 < 2014.1.4
CVE-2014-3632	High	October 7, 2014 10/7/14	>= 2014.1 <= 2014.1.2
CVE-2014-6414	Low	October 2, 2014 10/2/14	>= 2014.1 < 2014.1.2 >= 2014.2 <= 2014.2.4 >= 2013.2 <= 2013.2.4
CVE-2014-4615	Medium	August 19, 2014 8/19/14	== 2014.1 == 2014.1.1 == juno1
CVE-2014-3555	Medium	July 23, 2014 7/23/14	== 2014.1 == 2014.1.1 == juno-1 == 2013.2.4
CVE-2014-4167	Low	July 11, 2014 7/11/14	>= 2011.1 <= 2013.2.3 == 2014.1 == 2014.1.1
CVE-2013-6433	High	June 2, 2014 6/2/14	>= 2013.1 <= 2013.2.3
CVE-2014-0056	Medium	May 8, 2014 5/8/14	== 2013.2.2 == 2012.2.4 == 2013.1.1 == 2012.2.2 == 2013.1.3 == 2012.2.1 == 2013.2 == 2013.1.4 == 2013.1.5 == 2013.1 == 2012.2.3 == 2013.1.2 == 2012.2 == 2013.2.1
CVE-2014-0187	High	April 28, 2014 4/28/14	== 2014.1 == 2013.2.2 == 2013.1.1 == 2013.1.3 == 2013.2 == 2013.1.4 == 2013.1.5 == 2013.1 == 2013.2.3 == 2013.1.2 == 2013.2.1

neutron

51 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2024-53916	Medium	November 25, 2024 11/25/24	>= 23.0.0 < 23.2.1 >= 24.0.0 < 24.0.2 >= 25.0.0 < 25.0.1
CVE-2023-3637	Medium	July 25, 2023 7/25/23	<= 22.0.2
CVE-2022-3277	Medium	March 6, 2023 3/6/23	>= 19.0.0.0rc1 < 19.5.0 < 18.6.0 >= 20.0.0.0rc1 < 20.3.0
CVE-2021-40797	High	September 8, 2021 9/8/21	< 16.4.1 >= 17.0.0 < 17.2.1 >= 18.0.0 < 18.1.1
CVE-2021-40085	High	August 31, 2021 8/31/21	< 16.4.1 >= 17.0.0 < 17.2.1 >= 18.0.0 < 18.1.1
CVE-2021-38598	High	August 23, 2021 8/23/21	< 16.4.1 >= 17.0.0 < 17.1.3 == 18.0.0
CVE-2021-20267	High	May 28, 2021 5/28/21	>= 16.0.0 < 16.3.1 < 15.3.3 >= 17.0.0 < 17.1.1
CVE-2013-2255	Medium	November 1, 2019 11/1/19	< 7.0.0a0
CVE-2019-10876	High	April 5, 2019 4/5/19	>= 11.0.0 < 11.0.7 >= 12.0.0 < 12.0.6 >= 13.0.0 < 13.0.3
CVE-2019-9735	High	March 13, 2019 3/13/19	< 10.0.8 >= 11.0.0 < 11.0.7 >= 12.0.0 < 12.0.6 >= 13.0.0 < 13.0.3
CVE-2018-14635	High	September 10, 2018 9/10/18	== 13.0.0.0b1 >= 13.0.0.0b1 < 13.0.0.0b2 < 11.0.6 >= 12.0.0 < 12.0.4
CVE-2018-14636	Medium	September 10, 2018 9/10/18	== 13.0.0.0b1 >= 13.0.0.0b1 < 13.0.0.0b2 >= 12.0.0 < 12.0.3 >= 11.0.0 < 11.0.5
CVE-2017-7543	Medium	July 26, 2018 7/26/18	< 7.2.0-12.1 >= 8.0.0 < 8.3.0-11.1 >= 9.0.0 < 9.3.1-2.1 >= 10.0.0 < 10.0.2-1.1
CVE-2016-5363	High	June 17, 2016 6/17/16	< 7.1.0 >= 8.0.0 < 8.1.0
CVE-2016-5362	High	June 17, 2016 6/17/16	< 7.0.5 >= 8.0.0 < 8.1.1
CVE-2015-8914	Critical	June 17, 2016 6/17/16	< 7.0.5 >= 8.0.0 < 8.1.1
CVE-2015-5240	Low	October 27, 2015 10/27/15	< 7.0.0
CVE-2015-3221	Medium	August 26, 2015 8/26/15	< 2014.2.4 >= 2015.1.0 < 2015.1.1
CVE-2014-3555	Medium	July 23, 2014 7/23/14	< 2013.2.4 >= 2014.1.0 < 2014.1.2
CVE-2014-0056	Medium	May 8, 2014 5/8/14	>= 2012.2 < 2013.2.3

Showing vulnerabilities for 2 products matching "neutron". 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.