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-2005-0587	Medium	March 25, 2005 3/25/05	< 1.7.6
CVE-2005-0143	Low	March 23, 2005 3/23/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-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.8-alpha2
CVE-2005-0593	Low	March 4, 2005 3/4/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-0149	Medium	February 15, 2005 2/15/05	== 1.7-alpha == 1.7-rc1 == 1.7 == 1.7-beta == 1.7.1 == 1.7.2 == 1.7-rc3 == 1.7-rc2 == 1.7.3
CVE-2005-0233	High	February 8, 2005 2/8/05	< 1.7.6
CVE-2004-0902	High	January 27, 2005 1/27/05	== 1.7 == 1.7.1 == 1.7.2
CVE-2004-0903	High	January 27, 2005 1/27/05	== 1.7 == 1.7.1 == 1.7.2
CVE-2004-0904	High	December 31, 2004 12/31/04	== 1.7 == 1.7.1 == 1.7.2 == 1.7-rc3
CVE-2004-0906	Low	December 31, 2004 12/31/04	== 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.2
CVE-2004-0907	Low	December 31, 2004 12/31/04	== 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.2
CVE-2004-0908	Low	December 31, 2004 12/31/04	== 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.2
CVE-2004-0909	Medium	December 31, 2004 12/31/04	== 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.2
CVE-2004-1156	Low	December 31, 2004 12/31/04	== 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.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.2 == 1.7.3
CVE-2004-1449	Low	December 31, 2004 12/31/04	== 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
CVE-2004-1450	Medium	December 31, 2004 12/31/04	== 1.7-beta
CVE-2004-1451	Low	December 31, 2004 12/31/04	== 1.4.2 == 0.9.5 == 0.9.35 == 0.9.3 == 1.0.1 == 0.9.48 == 1.2.1 == 1.0-rc1 == 1.2-alpha == 0.9.7 == 1.1-beta == 1.0-rc2 == 0.9.2.1 == 1.4.1 == 1.4-beta == 1.2 == 0.9.2 == 1.4.4 == 1.3 == 1.2-beta == 1.0 == 0.9.8 == 1.4 == 1.5 == 0.9.4 == 1.4-alpha == 0.9.6 == 1.5.1 == 1.1 == 1.1-alpha == 0.9.4.1 == 0.8 == 1.0.2 == 1.3.1 == 0.9.9
CVE-2004-1753	Low	December 31, 2004 12/31/04	== 1.7.2
CVE-2004-1316	Medium	December 29, 2004 12/29/04	== 1.7-alpha == 1.7-rc1 == 1.5-rc2 == 1.7 == 1.6-beta == 1.4.1 == 1.5-alpha == 1.5-rc1 == 1.3 == 1.7-beta == 1.4 == 1.5 * == 1.7.1 == 1.4-alpha == 1.5.1 == 1.7.2 == 1.7-rc3 == 1.7-rc2 == 1.7.3 == 1.6-alpha == 1.6
CVE-2004-1380	Medium	October 20, 2004 10/20/04	* == 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
CVE-2004-1381	Medium	October 20, 2004 10/20/04	* == 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
CVE-2004-1613	Medium	October 18, 2004 10/18/04	== 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.6 == 1.7 == 1.7-rc3 == 1.7.1 == 1.7.2 == 1.7.3 == 1.8-alpha2
CVE-2004-1614	Medium	October 18, 2004 10/18/04	== 1.4.2 == 1.0.1 == 1.2.1 == 1.0-rc1 == 1.2-alpha == 1.7 == 1.1-beta == 1.0-rc2 == 1.4.1 == 1.4-beta == 1.2 == 1.3 == 1.2-beta == 1.0 == 1.4 == 1.5 == 1.7.1 == 1.4-alpha == 1.1 == 1.1-alpha == 1.7.2 == 1.0.2 == 1.8-alpha2 == 1.7-rc3 == 1.7.3 == 1.3.1 == 1.6
CVE-2004-0871	Medium	September 16, 2004 9/16/04	== 0.9.2
CVE-2004-0905	Low	September 14, 2004 9/14/04	== 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.5 == 1.6 == 1.7 == 1.7-rc3 == 1.7.1 == 1.7.2
CVE-2004-0722	High	August 18, 2004 8/18/04	== 1.6
CVE-2004-0757	High	August 18, 2004 8/18/04	<= 1.7
CVE-2004-0758	Medium	August 18, 2004 8/18/04	*
CVE-2004-0759	Medium	August 18, 2004 8/18/04	*
CVE-2004-0760	Medium	August 18, 2004 8/18/04	*
CVE-2004-0761	Medium	August 18, 2004 8/18/04	<= 1.7
CVE-2004-0762	Medium	August 18, 2004 8/18/04	<= 1.7
CVE-2004-0764	High	August 18, 2004 8/18/04	<= 1.7
CVE-2004-0765	High	August 18, 2004 8/18/04	<= 1.7
CVE-2004-0779	High	August 18, 2004 8/18/04	== 1.6
CVE-2004-0648	High	August 6, 2004 8/6/04	<= 1.7.1
CVE-2004-0718	High	July 27, 2004 7/27/04	== 1.6
CVE-2004-0478	Low	July 7, 2004 7/7/04	*
CVE-2003-0594	High	April 15, 2004 4/15/04	== 1.4.2 == 1.0.1 == 1.2.1 == 1.0-rc1 == 1.2-alpha == 1.1-beta == 1.0-rc2 == 1.4.1 == 1.2 == 1.1-alpha == 1.4 == 1.1 == 1.3 == 1.3.1 == 1.0 == 1.0.2 == 1.2-beta
CVE-2004-0191	Medium	March 15, 2004 3/15/04	== 0.9.5 == 0.9.35 == 0.9.3 == 1.0.1 == 0.9.48 == 1.2.1 == 1.0-rc1 == 1.2-alpha == 0.9.7 == 1.1-beta == 1.0-rc2 == 0.9.2.1 == 1.4.1 == 1.4-beta == 1.2 == 0.9.2 == 1.3 == 1.2-beta == 1.0 == 0.9.8 == 1.4 == 1.5 == 0.9.4 == 1.4-alpha == 0.9.6 == 1.1 == 1.1-alpha == 0.9.4.1 == 0.8 == 1.0.2 == 1.3.1 == 0.9.9
CVE-2003-1265	Low	December 31, 2003 12/31/03	== 5.0
CVE-2003-0791	Critical	October 7, 2003 10/7/03	<= 1.4
CVE-2003-0298	High	June 16, 2003 6/16/03	== 1.3 == 1.4-alpha
CVE-2003-0300	Medium	June 16, 2003 6/16/03	== 1.3 == 1.4-alpha
CVE-2002-2013	Medium	December 31, 2002 12/31/02	== 0.9.5 == 0.9.3 == 0.9.2.1 == 0.9.2 == 0.9.4 == 0.9.6 == 0.9.4.1
CVE-2002-2061	High	December 31, 2002 12/31/02	<= 1.0
CVE-2002-2314	Medium	December 31, 2002 12/31/02	== 1.0
CVE-2002-2338	Medium	December 31, 2002 12/31/02	== 0.9.5 == 0.9.3 == 1.0-rc1 == 0.9.7 == 1.0-rc2 == 0.9.2.1 == 0.9.2 == 1.0 == 0.9.8 == 0.9.4 == 0.9.6 == 0.9.4.1 == 0.9.9
CVE-2002-2359	Low	December 31, 2002 12/31/02	== 1.0-rc1 == 1.0-rc2 == 1.0 == 1.1-alpha
CVE-2002-1308	High	November 29, 2002 11/29/02	== 1.0.1 == 0.9.7 == 1.0 == 0.9.8 == 0.9.6 == 1.1 == 0.9.9
CVE-2002-1091	High	October 4, 2002 10/4/02	== 0.9.5 == 0.9.7 == 1.0 == 0.9.8 == 0.9.6 == 0.9.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.