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

Found 1 matching product.

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

mozilla / mozilla

107 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2009-3010	Low	August 31, 2009 8/31/09	<= 1.7.12
CVE-2009-3014	Low	August 31, 2009 8/31/09	<= 1.7 == 0.8 == 0.9.2 == 0.9.2.1 == 0.9.3 == 0.9.35 == 0.9.4 == 0.9.4.1 == 0.9.48 == 0.9.5 == 0.9.6 == 0.9.7 == 0.9.8 == 0.9.9 == 1.0 == 1.0-rc1 == 1.0-rc2 == 1.0-rc3 == 1.0.1 == 1.0.2 == 1.1 == 1.1-alpha == 1.1-beta == 1.2 == 1.2-alpha == 1.2-beta == 1.2.1 == 1.3 == 1.3.1 == 1.4 == 1.4-alpha == 1.4-beta == 1.4.1 == 1.4.2 == 1.4.4 == 1.5 == 1.5-alpha == 1.5-rc1 == 1.5-rc2 == 1.5.1 == 1.6 == 1.6-alpha == 1.6-beta
CVE-2007-4039	Critical	July 27, 2007 7/27/07	*
CVE-2007-3144	Medium	June 11, 2007 6/11/07	== 1.7.12
CVE-2007-1794	High	April 2, 2007 4/2/07	<= 1.7
CVE-2006-6498	Medium	December 20, 2006 12/20/06	== 1.7
CVE-2006-0292	High	February 2, 2006 2/2/06	== 1.5-rc2 == 1.4.1 == 1.5-alpha == 1.5-rc1 == 1.4 == 1.5
CVE-2006-0496	Low	February 1, 2006 2/1/06	== 1.7-alpha == 1.7-rc1 == 1.7 == 1.7.5 == 1.7.11 == 1.7.7 == 1.7-beta == 1.7.6 == 1.7.1 == 1.7.10 == 1.7.12 == 1.7.8 == 1.7.2 == 1.7-rc3 == 1.7-rc2 == 1.7.3
CVE-2005-4685	Medium	December 31, 2005 12/31/05	== 0.8 == 0.9.2 == 0.9.2.1 == 0.9.3 == 0.9.35 == 0.9.4 == 0.9.4.1 == 0.9.48 == 0.9.5 == 0.9.6 == 0.9.7 == 0.9.8 == 0.9.9 == 1.0 == 1.0-rc1 == 1.0-rc2 == 1.0.1 == 1.0.2 == 1.1 == 1.1-alpha == 1.1-beta == 1.2 == 1.2-alpha == 1.2-beta == 1.2.1 == 1.3 == 1.3.1 == 1.4 == 1.4-alpha == 1.4-beta == 1.4.1 == 1.4.2 == 1.4.4 == 1.5 == 1.5.1 == 1.6 == 1.7 == 1.7-alpha == 1.7-beta == 1.7-rc1 == 1.7-rc2 == 1.7-rc3 == 1.7.1 == 1.7.10 == 1.7.11 == 1.7.12 == 1.7.2 == 1.7.3 == 1.7.4 == 1.7.5 == 1.7.6 == 1.7.7 == 1.7.8 == 1.7.9 == 1.8-alpha1 == 1.8-alpha2 == 1.8-alpha3 == 1.8-alpha4 == m15 == m16
CVE-2005-4809	Medium	December 31, 2005 12/31/05	== 1.7.4 == 1.7.5 == 1.7.6 == 1.7.3
CVE-2005-4874	Low	December 31, 2005 12/31/05	== 1.7.8
CVE-2005-3896	High	November 29, 2005 11/29/05	*
CVE-2005-2968	High	September 20, 2005 9/20/05	== 1.7.10
CVE-2005-2260	High	July 13, 2005 7/13/05	== 1.3 == 1.4 == 1.4-alpha == 1.4.1 == 1.5 == 1.5-alpha == 1.5-rc1 == 1.5-rc2 == 1.5.1 == 1.6 == 1.6-alpha == 1.6-beta == 1.7 == 1.7-alpha == 1.7-beta == 1.7-rc1 == 1.7-rc2 == 1.7-rc3 == 1.7.1 == 1.7.2 == 1.7.3 == 1.7.5 == 1.7.6 == 1.7.7 == 1.7.8
CVE-2005-2261	High	July 13, 2005 7/13/05	== 1.3 == 1.4 == 1.4-alpha == 1.4.1 == 1.5 == 1.5-alpha == 1.5-rc1 == 1.5-rc2 == 1.5.1 == 1.6 == 1.6-alpha == 1.6-beta == 1.7 == 1.7-alpha == 1.7-beta == 1.7-rc1 == 1.7-rc2 == 1.7-rc3 == 1.7.1 == 1.7.2 == 1.7.3 == 1.7.5 == 1.7.6 == 1.7.7 == 1.7.8
CVE-2005-2263	Medium	July 13, 2005 7/13/05	== 1.3 == 1.4 == 1.4-alpha == 1.4.1 == 1.5 == 1.5-alpha == 1.5-rc1 == 1.5-rc2 == 1.5.1 == 1.6 == 1.6-alpha == 1.6-beta == 1.7 == 1.7-alpha == 1.7-beta == 1.7-rc1 == 1.7-rc2 == 1.7-rc3 == 1.7.1 == 1.7.2 == 1.7.3 == 1.7.5 == 1.7.6 == 1.7.7 == 1.7.8
CVE-2005-2265	Medium	July 13, 2005 7/13/05	== 1.3 == 1.4 == 1.4-alpha == 1.4.1 == 1.5 == 1.5-alpha == 1.5-rc1 == 1.5-rc2 == 1.5.1 == 1.6 == 1.6-alpha == 1.6-beta == 1.7 == 1.7-alpha == 1.7-beta == 1.7-rc1 == 1.7-rc2 == 1.7-rc3 == 1.7.1 == 1.7.2 == 1.7.3 == 1.7.5 == 1.7.6 == 1.7.7 == 1.7.8
CVE-2005-2266	Medium	July 13, 2005 7/13/05	== 1.3 == 1.4 == 1.4-alpha == 1.4.1 == 1.5 == 1.5-alpha == 1.5-rc1 == 1.5-rc2 == 1.5.1 == 1.6 == 1.6-alpha == 1.6-beta == 1.7 == 1.7-alpha == 1.7-beta == 1.7-rc1 == 1.7-rc2 == 1.7-rc3 == 1.7.1 == 1.7.2 == 1.7.3 == 1.7.5 == 1.7.6 == 1.7.7 == 1.7.8
CVE-2005-2268	Low	July 13, 2005 7/13/05	== 1.3 == 1.4 == 1.4-alpha == 1.4.1 == 1.5 == 1.5-alpha == 1.5-rc1 == 1.5-rc2 == 1.5.1 == 1.6 == 1.6-alpha == 1.6-beta == 1.7 == 1.7-alpha == 1.7-beta == 1.7-rc1 == 1.7-rc2 == 1.7-rc3 == 1.7.1 == 1.7.2 == 1.7.3 == 1.7.5 == 1.7.6 == 1.7.7 == 1.7.8
CVE-2005-2269	High	July 13, 2005 7/13/05	== 1.3 == 1.4 == 1.4-alpha == 1.4.1 == 1.5 == 1.5-alpha == 1.5-rc1 == 1.5-rc2 == 1.5.1 == 1.6 == 1.6-alpha == 1.6-beta == 1.7 == 1.7-alpha == 1.7-beta == 1.7-rc1 == 1.7-rc2 == 1.7-rc3 == 1.7.1 == 1.7.2 == 1.7.3 == 1.7.5 == 1.7.6 == 1.7.7 == 1.7.8
CVE-2005-2270	High	July 13, 2005 7/13/05	== 1.3 == 1.4 == 1.4-alpha == 1.4.1 == 1.5 == 1.5-alpha == 1.5-rc1 == 1.5-rc2 == 1.5.1 == 1.6 == 1.6-alpha == 1.6-beta == 1.7 == 1.7-alpha == 1.7-beta == 1.7-rc1 == 1.7-rc2 == 1.7-rc3 == 1.7.1 == 1.7.2 == 1.7.3 == 1.7.5 == 1.7.6 == 1.7.7 == 1.7.8
CVE-2005-2114	Medium	July 5, 2005 7/5/05	== 1.7.8
CVE-2005-1937	Low	June 14, 2005 6/14/05	== 1.7.7
CVE-2005-1531	High	May 12, 2005 5/12/05	<= 1.4 == 1.4.1 == 1.5 == 1.5-alpha == 1.5-rc1 == 1.5-rc2 == 1.5.1 == 1.6 == 1.6-alpha == 1.6-beta == 1.7 == 1.7-alpha == 1.7-beta == 1.7-rc1 == 1.7-rc2 == 1.7-rc3 == 1.7.1 == 1.7.2 == 1.7.3 == 1.7.5 == 1.7.6 == 1.7.7
CVE-2005-1532	High	May 12, 2005 5/12/05	== 1.3 == 1.4 == 1.4-alpha == 1.4.1 == 1.5 == 1.5-alpha == 1.5-rc1 == 1.5-rc2 == 1.5.1 == 1.6 == 1.6-alpha == 1.6-beta == 1.7 == 1.7-alpha == 1.7-beta == 1.7-rc1 == 1.7-rc2 == 1.7-rc3 == 1.7.1 == 1.7.2 == 1.7.3 == 1.7.5 == 1.7.6 == 1.7.7
CVE-2005-0141	Low	May 2, 2005 5/2/05	== 1.7 == 1.7.1 == 1.7.2 == 1.7-rc3 == 1.7.3
CVE-2005-0142	Low	May 2, 2005 5/2/05	== 1.7 == 1.7.1 == 1.7.2 == 1.7-rc3 == 1.7.3
CVE-2005-0144	Low	May 2, 2005 5/2/05	== 1.7 == 1.7.1 == 1.7.2 == 1.7-rc3 == 1.7.3
CVE-2005-0146	Medium	May 2, 2005 5/2/05	== 1.7 == 1.7.1 == 1.7.2 == 1.7-rc3 == 1.7.3
CVE-2005-0147	High	May 2, 2005 5/2/05	== 1.7 == 1.7.1 == 1.7.2 == 1.7-rc3 == 1.7.3
CVE-2005-0215	Medium	May 2, 2005 5/2/05	== 1.6
CVE-2005-0238	Medium	May 2, 2005 5/2/05	<= 1.6
CVE-2005-0255	Medium	May 2, 2005 5/2/05	== 1.7.3
CVE-2005-0399	Medium	May 2, 2005 5/2/05	== 1.3 == 1.4 == 1.4-alpha == 1.4.1 == 1.5 == 1.5-alpha == 1.5-rc1 == 1.5-rc2 == 1.5.1 == 1.6 == 1.6-alpha == 1.6-beta == 1.7 == 1.7-alpha == 1.7-beta == 1.7-rc1 == 1.7-rc2 == 1.7-rc3 == 1.7.1 == 1.7.2 == 1.7.3 == 1.7.5
CVE-2005-0401	Medium	May 2, 2005 5/2/05	== 1.3 == 1.4 == 1.4-alpha == 1.4.1 == 1.5 == 1.5-alpha == 1.5-rc1 == 1.5-rc2 == 1.5.1 == 1.6 == 1.6-alpha == 1.6-beta == 1.7 == 1.7-alpha == 1.7-beta == 1.7-rc1 == 1.7-rc2 == 1.7-rc3 == 1.7.1 == 1.7.2 == 1.7.3 == 1.7.5
CVE-2005-0578	Low	May 2, 2005 5/2/05	== 1.3 == 1.4 == 1.4-alpha == 1.4.1 == 1.5 == 1.5-alpha == 1.5-rc1 == 1.5-rc2 == 1.5.1 == 1.6 == 1.6-alpha == 1.6-beta == 1.7 == 1.7-alpha == 1.7-beta == 1.7-rc1 == 1.7-rc2 == 1.7-rc3 == 1.7.1 == 1.7.2 == 1.7.3 == 1.7.5
CVE-2005-0584	Low	May 2, 2005 5/2/05	== 1.3 == 1.4 == 1.4-alpha == 1.4.1 == 1.5 == 1.5-alpha == 1.5-rc1 == 1.5-rc2 == 1.5.1 == 1.6 == 1.6-alpha == 1.6-beta == 1.7 == 1.7-alpha == 1.7-beta == 1.7-rc1 == 1.7-rc2 == 1.7-rc3 == 1.7.1 == 1.7.2 == 1.7.3 == 1.7.5
CVE-2005-0586	Low	May 2, 2005 5/2/05	== 1.3 == 1.4 == 1.4-alpha == 1.4.1 == 1.5 == 1.5-alpha == 1.5-rc1 == 1.5-rc2 == 1.5.1 == 1.6 == 1.6-alpha == 1.6-beta == 1.7 == 1.7-alpha == 1.7-beta == 1.7-rc1 == 1.7-rc2 == 1.7-rc3 == 1.7.1 == 1.7.2 == 1.7.3 == 1.7.5
CVE-2005-0588	Medium	May 2, 2005 5/2/05	== 1.3 == 1.4 == 1.4-alpha == 1.4.1 == 1.5 == 1.5-alpha == 1.5-rc1 == 1.5-rc2 == 1.5.1 == 1.6 == 1.6-alpha == 1.6-beta == 1.7 == 1.7-alpha == 1.7-beta == 1.7-rc1 == 1.7-rc2 == 1.7-rc3 == 1.7.1 == 1.7.2 == 1.7.3 == 1.7.5
CVE-2005-0590	Medium	May 2, 2005 5/2/05	== 1.3 == 1.4 == 1.4-alpha == 1.4.1 == 1.5 == 1.5-alpha == 1.5-rc1 == 1.5-rc2 == 1.5.1 == 1.6 == 1.6-alpha == 1.6-beta == 1.7 == 1.7-alpha == 1.7-beta == 1.7-rc1 == 1.7-rc2 == 1.7-rc3 == 1.7.1 == 1.7.2 == 1.7.3 == 1.7.5
CVE-2005-0989	Medium	May 2, 2005 5/2/05	== 1.7.6
CVE-2005-1153	High	May 2, 2005 5/2/05	== 1.3 == 1.4 == 1.4-alpha == 1.4.1 == 1.5 == 1.5-alpha == 1.5-rc1 == 1.5-rc2 == 1.5.1 == 1.6 == 1.6-alpha == 1.6-beta == 1.7 == 1.7-alpha == 1.7-beta == 1.7-rc1 == 1.7-rc2 == 1.7-rc3 == 1.7.1 == 1.7.2 == 1.7.3 == 1.7.5 == 1.7.6
CVE-2005-1154	High	May 2, 2005 5/2/05	== 1.3 == 1.4 == 1.4-alpha == 1.4.1 == 1.5 == 1.5-alpha == 1.5-rc1 == 1.5-rc2 == 1.5.1 == 1.6 == 1.6-alpha == 1.6-beta == 1.7 == 1.7-alpha == 1.7-beta == 1.7-rc1 == 1.7-rc2 == 1.7-rc3 == 1.7.1 == 1.7.2 == 1.7.3 == 1.7.5 == 1.7.6
CVE-2005-1155	High	May 2, 2005 5/2/05	== 1.3 == 1.4 == 1.4-alpha == 1.4.1 == 1.5 == 1.5-alpha == 1.5-rc1 == 1.5-rc2 == 1.5.1 == 1.6 == 1.6-alpha == 1.6-beta == 1.7 == 1.7-alpha == 1.7-beta == 1.7-rc1 == 1.7-rc2 == 1.7-rc3 == 1.7.1 == 1.7.2 == 1.7.3 == 1.7.5 == 1.7.6
CVE-2005-1156	High	May 2, 2005 5/2/05	== 1.3 == 1.4 == 1.4-alpha == 1.4.1 == 1.5 == 1.5-alpha == 1.5-rc1 == 1.5-rc2 == 1.5.1 == 1.6 == 1.6-alpha == 1.6-beta == 1.7 == 1.7-alpha == 1.7-beta == 1.7-rc1 == 1.7-rc2 == 1.7-rc3 == 1.7.1 == 1.7.2 == 1.7.3 == 1.7.5 == 1.7.6
CVE-2005-1157	High	May 2, 2005 5/2/05	== 1.3 == 1.4 == 1.4-alpha == 1.4.1 == 1.5 == 1.5-alpha == 1.5-rc1 == 1.5-rc2 == 1.5.1 == 1.6 == 1.6-alpha == 1.6-beta == 1.7 == 1.7-alpha == 1.7-beta == 1.7-rc1 == 1.7-rc2 == 1.7-rc3 == 1.7.1 == 1.7.2 == 1.7.3 == 1.7.5 == 1.7.6
CVE-2005-1159	High	May 2, 2005 5/2/05	== 1.3 == 1.4 == 1.4-alpha == 1.4.1 == 1.5 == 1.5-alpha == 1.5-rc1 == 1.5-rc2 == 1.5.1 == 1.6 == 1.6-alpha == 1.6-beta == 1.7 == 1.7-alpha == 1.7-beta == 1.7-rc1 == 1.7-rc2 == 1.7-rc3 == 1.7.1 == 1.7.2 == 1.7.3 == 1.7.5 == 1.7.6
CVE-2005-1160	Medium	May 2, 2005 5/2/05	== 1.3 == 1.4 == 1.4-alpha == 1.4.1 == 1.5 == 1.5-alpha == 1.5-rc1 == 1.5-rc2 == 1.5.1 == 1.6 == 1.6-alpha == 1.6-beta == 1.7 == 1.7-alpha == 1.7-beta == 1.7-rc1 == 1.7-rc2 == 1.7-rc3 == 1.7.1 == 1.7.2 == 1.7.3 == 1.7.5 == 1.7.6
CVE-2005-0585	Low	March 25, 2005 3/25/05	== 1.3 == 1.4 == 1.4-alpha == 1.4.1 == 1.5 == 1.5-alpha == 1.5-rc1 == 1.5-rc2 == 1.5.1 == 1.6 == 1.6-alpha == 1.6-beta == 1.7 == 1.7-alpha == 1.7-beta == 1.7-rc1 == 1.7-rc2 == 1.7-rc3 == 1.7.1 == 1.7.2 == 1.7.3 == 1.7.5
CVE-2005-0592	High	March 25, 2005 3/25/05	== 1.3 == 1.4 == 1.4-alpha == 1.4.1 == 1.5 == 1.5-alpha == 1.5-rc1 == 1.5-rc2 == 1.5.1 == 1.6 == 1.6-alpha == 1.6-beta == 1.7 == 1.7-alpha == 1.7-beta == 1.7-rc1 == 1.7-rc2 == 1.7-rc3 == 1.7.1 == 1.7.2 == 1.7.3 == 1.7.5

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.