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 "network_security_services"

Found 1 matching product.

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

mozilla / network_security_services

46 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2022-3479	High	October 14, 2022 10/14/22	>= 3.77 < 3.87
CVE-2018-18508	Medium	October 22, 2020 10/22/20	< 3.36.7 >= 3.41 < 3.41.1
CVE-2019-17006	Critical	October 22, 2020 10/22/20	< 3.46
CVE-2019-17007	High	October 22, 2020 10/22/20	< 3.44
CVE-2020-25648	High	October 20, 2020 10/20/20	< 3.58
CVE-2018-12404	Low	May 2, 2019 5/2/19	< 3.41
CVE-2018-12384	Low	April 29, 2019 4/29/19	< 3.39
CVE-2016-8635	Low	August 1, 2018 8/1/18	>= 3.21 <= 3.21.4
CVE-2016-9574	Low	July 19, 2018 7/19/18	< 3.30
CVE-2017-5462	Medium	June 11, 2018 6/11/18	< 3.28.4
CVE-2017-7502	Medium	May 30, 2017 5/30/17	== 3.25.0 == 3.29.1 == 3.29.0 == 3.30.0 == 3.29.2 == 3.25.1 == 3.28.1 == 3.26.2 == 3.30.1 == 3.24.0 == 3.27.0 == 3.29.3 == 3.28.0 == 3.27.2 == 3.28.3 == 3.28.2 == 3.27.1 == 3.26.0
CVE-2017-5461	High	May 11, 2017 5/11/17	< 3.21.4 >= 3.22.x < 3.28.4 >= 3.29 < 3.29.5 >= 3.30 < 3.30.1
CVE-2016-2834	High	June 13, 2016 6/13/16	<= 3.22
CVE-2016-1979	Medium	March 13, 2016 3/13/16	<= 3.21
CVE-2016-1978	High	March 13, 2016 3/13/16	<= 3.20.1
CVE-2016-1950	Medium	March 13, 2016 3/13/16	== 3.19.2 == 3.20 == 3.20.1 == 3.21
CVE-2015-7575	Low	January 9, 2016 1/9/16	<= 3.20.1
CVE-2015-7183	High	November 5, 2015 11/5/15	<= 3.19.2.0 == 3.20.0
CVE-2015-7182	High	November 5, 2015 11/5/15	<= 3.19.2.0 == 3.20.0
CVE-2015-7181	High	November 5, 2015 11/5/15	<= 3.19.2.0 == 3.20.0
CVE-2015-2730	Low	July 6, 2015 7/6/15	<= 3.19
CVE-2015-2721	Low	July 6, 2015 7/6/15	== 3.19
CVE-2015-4000	Low	May 21, 2015 5/21/15	== 3.19
CVE-2014-1569	High	December 15, 2014 12/15/14	== 3.16.2.1 == 3.17.2 <= 3.16.2.3 == 3.17.0 == 3.16.2.2 == 3.16.2.0 == 3.17.1
CVE-2014-1568	High	September 25, 2014 9/25/14	<= 3.16.2.0 == 3.11.2 == 3.11.3 == 3.11.4 == 3.11.5 == 3.12 == 3.12.1 == 3.12.10 == 3.12.11 == 3.12.2 == 3.12.3 == 3.12.3.1 == 3.12.3.2 == 3.12.4 == 3.12.5 == 3.12.6 == 3.12.7 == 3.12.8 == 3.12.9 == 3.14 == 3.14.1 == 3.14.2 == 3.14.3 == 3.14.4 == 3.14.5 == 3.15 == 3.15.1 == 3.15.2 == 3.15.3 == 3.15.3.1 == 3.15.4 == 3.15.5 == 3.16 == 3.16.1 == 3.16.3 == 3.16.4 == 3.2 == 3.2.1 == 3.3 == 3.3.1 == 3.3.2 == 3.4 == 3.4.1 == 3.4.2 == 3.5 == 3.6 == 3.6.1 == 3.7 == 3.7.1 == 3.7.2 == 3.7.3 == 3.7.5 == 3.7.7 == 3.8 == 3.9
CVE-2014-1544	High	July 23, 2014 7/23/14	== 3.11.2 == 3.6.1 == 3.12.5 == 3.2 == 3.15 == 3.11.4 == 3.7.7 == 3.14.1 == 3.7.5 == 3.7.1 == 3.12.9 == 3.15.3 == 3.12.3.1 == 3.6 == 3.12.6 == 3.2.1 == 3.12.8 == 3.15.1 == 3.12.11 == 3.14.3 == 3.14.4 == 3.9 == 3.4 == 3.14 == 3.8 == 3.4.1 == 3.11.5 == 3.15.5 == 3.7 == 3.12.2 == 3.7.2 == 3.12.10 == 3.3 == 3.12.4 == 3.12.1 == 3.12.3.2 == 3.7.3 == 3.15.2 == 3.4.2 == 3.12.3 == 3.3.2 == 3.14.5 == 3.5 == 3.15.3.1 == 3.14.2 == 3.12.7 == 3.16 == 3.15.4 == 3.11.3 == 3.12 == 3.3.1
CVE-2014-1492	Low	March 25, 2014 3/25/14	== 3.11.2 == 3.6.1 == 3.12.5 == 3.2 == 3.15 == 3.11.4 == 3.7.7 == 3.14.1 == 3.7.5 == 3.7.1 == 3.12.9 == 3.15.3 == 3.12.3.1 == 3.6 == 3.12.6 == 3.2.1 == 3.12.8 <= 3.15.5 == 3.15.1 == 3.12.11 == 3.14.3 == 3.14.4 == 3.9 == 3.4 == 3.14 == 3.8 == 3.4.1 == 3.11.5 == 3.7 == 3.12.2 == 3.7.2 == 3.12.10 == 3.3 == 3.12.4 == 3.12.1 == 3.12.3.2 == 3.7.3 == 3.15.2 == 3.4.2 == 3.12.3 == 3.3.2 == 3.14.5 == 3.5 == 3.15.3.1 == 3.14.2 == 3.12.7 == 3.15.4 == 3.11.3 == 3.12 == 3.3.1
CVE-2014-1490	High	February 6, 2014 2/6/14	< 3.15.4
CVE-2014-1491	Low	February 6, 2014 2/6/14	< 3.15.4
CVE-2013-1740	Medium	January 18, 2014 1/18/14	== 3.11.2 == 3.6.1 == 3.12.5 == 3.2 == 3.15 == 3.11.4 == 3.7.7 == 3.14.1 == 3.7.5 == 3.7.1 == 3.12.9 == 3.12.3.1 == 3.6 == 3.12.6 == 3.2.1 == 3.12.8 == 3.15.1 == 3.12.11 == 3.14.3 == 3.14.4 == 3.9 == 3.4 == 3.14 == 3.8 == 3.4.1 == 3.11.5 == 3.7 == 3.12.2 == 3.7.2 == 3.12.10 == 3.3 == 3.12.4 == 3.12.1 == 3.12.3.2 == 3.7.3 == 3.15.2 == 3.4.2 == 3.12.3 == 3.3.2 == 3.14.5 == 3.5 == 3.14.2 == 3.12.7 == 3.11.3 <= 3.15.3 == 3.12 == 3.3.1
CVE-2013-1741	High	November 18, 2013 11/18/13	== 3.15 == 3.15.1 == 3.15.2
CVE-2013-5605	High	November 18, 2013 11/18/13	== 3.15 == 3.14.1 == 3.15.1 == 3.14.3 == 3.14.4 == 3.14 == 3.15.2 == 3.14.2
CVE-2013-5606	Medium	November 18, 2013 11/18/13	== 3.15 == 3.15.1 == 3.15.2
CVE-2013-1739	Medium	October 22, 2013 10/22/13	== 3.12.5 == 3.15 == 3.14.1 == 3.12.9 == 3.12.3.1 == 3.12.6 == 3.12.8 == 3.12.11 == 3.14.3 == 3.14 == 3.12.2 == 3.12.10 == 3.12.4 == 3.12.1 == 3.12.3.2 == 3.12.3 == 3.14.2 <= 3.15.1 == 3.12.7 == 3.12
CVE-2013-0791	Medium	April 3, 2013 4/3/13	< 3.15
CVE-2013-1620	Low	February 8, 2013 2/8/13	< 3.14.3
CVE-2011-5094	Low	June 16, 2012 6/16/12	== 3.11.2 == 3.11.3 == 3.11.4 == 3.11.5 == 3.2 == 3.2.1 == 3.3 == 3.3.1 == 3.3.2 == 3.4 == 3.4.1 == 3.4.2 == 3.5 == 3.6 == 3.6.1 == 3.7 == 3.7.1 == 3.7.2 == 3.7.3 == 3.7.5 == 3.7.7 == 3.8 == 3.9
CVE-2012-0441	Medium	June 5, 2012 6/5/12	<= 3.12.3 == 3.11.2 == 3.11.3 == 3.11.4 == 3.11.5 == 3.12 == 3.12.1 == 3.12.2 == 3.2 == 3.2.1 == 3.3 == 3.3.1 == 3.3.2 == 3.4 == 3.4.1 == 3.4.2 == 3.5 == 3.6 == 3.6.1 == 3.7 == 3.7.1 == 3.7.2 == 3.7.3 == 3.7.5 == 3.7.7 == 3.8 == 3.9
CVE-2009-2404	High	August 3, 2009 8/3/09	== 3.12.3
CVE-2009-2408	Medium	July 30, 2009 7/30/09	< 3.12.3
CVE-2009-2409	Medium	July 30, 2009 7/30/09	< 3.12.3
CVE-2007-0008	Medium	February 26, 2007 2/26/07	== 3.11.2 == 3.11.4 == 3.11.3
CVE-2007-0009	Medium	February 26, 2007 2/26/07	< 3.11.5
CVE-2006-5462	Medium	November 8, 2006 11/8/06	== 3.11.3
CVE-2006-4340	Low	September 15, 2006 9/15/06	<= 3.11.2
CVE-2004-0826	High	December 31, 2004 12/31/04	== 3.2 == 3.2.1 == 3.3 == 3.3.1 == 3.3.2 == 3.4 == 3.4.1 == 3.4.2 == 3.5 == 3.6 == 3.6.1 == 3.7 == 3.7.1 == 3.7.2 == 3.7.3 == 3.7.5 == 3.7.7 == 3.8 == 3.9

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.