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.

372,871

Total vulnerabilities in the database

Vulnerabilities for products matching "firefox"

Found 1 matching product.

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

mozilla / firefox

37607 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2008-0412	High	February 8, 2008 2/8/08	<= 2.0.0.11
CVE-2008-0413	High	February 8, 2008 2/8/08	<= 2.0.0.11
CVE-2008-0414	Low	February 8, 2008 2/8/08	<= 2.0.0.11
CVE-2008-0415	Low	February 8, 2008 2/8/08	<= 2.0.0.11
CVE-2008-0417	Low	February 8, 2008 2/8/08	<= 2.0.0.11
CVE-2008-0418	Low	February 8, 2008 2/8/08	<= 2.0.0.11
CVE-2008-0419	High	February 8, 2008 2/8/08	<= 2.0.0.11
CVE-2008-0367	Medium	January 19, 2008 1/19/08	== 3.0-beta2 <= 2.0.0.11
CVE-2007-6589	Low	December 28, 2007 12/28/07	<= 2.0.0.9
CVE-2007-5959	High	November 26, 2007 11/26/07	== 0.8 == 1.5.2 == 1.5.0.6 == 1.8 == 2.0.0.2 == 1.5.0.10 == 1.5.0.3 == 1.5.0.11 == 1.5.4 == 1.0.2 == 1.5 == 0.9.1 == 1.0.4 == 2.0.0.7 == 1.0.7 == 2.0.0.9 == 0.10.1 == 0.9 == 1.5.6 == 1.0 == 1.5.0.7 == 2.0 == 1.0.1 == 2.0-beta1 == 1.5.0.8 == 2.0.0.3 == 1.5.0.9 == 1.5.0.5 == 1.5.7 == 1.5.0.12 == 2.0.0.6 == 1.5.0.2 == 1.0.3 == 2.0.0.4 == 1.5.1 == 0.9.3 == 2.0-rc2 == 2.0.0.1 == 1.5.5 == 0.9.2 == 2.0.0.8 == 1.5.8 == 1.5.3 == 1.5.0.4 == 1.5.0.1 == 0.10 == 1.0.5 == 2.0.0.5 == 2.0-rc3 == 1.0.6 == 1.0.8
CVE-2007-5960	Low	November 26, 2007 11/26/07	== 0.8 == 1.5.2 == 1.5.0.6 == 1.8 == 2.0.0.2 == 1.5.0.10 == 1.5.0.3 == 1.5.0.11 == 1.5.4 == 1.0.2 == 1.5 == 0.9.1 == 1.0.4 == 2.0.0.7 == 1.0.7 == 2.0.0.9 == 0.10.1 == 0.9 == 1.5.6 == 1.0 == 1.5.0.7 == 2.0 == 1.0.1 == 2.0-beta1 == 1.5.0.8 == 2.0.0.3 == 1.5.0.9 == 1.5.0.5 == 1.5.7 == 1.5.0.12 == 2.0.0.6 == 1.5.0.2 == 1.0.3 == 2.0.0.4 == 1.5.1 == 0.9.3 == 2.0-rc2 == 2.0.0.1 == 1.5.5 == 0.9.2 == 2.0.0.8 == 1.5.8 == 1.5.3 == 1.5.0.4 == 1.5.0.1 == 0.10 == 1.0.5 == 2.0.0.5 == 2.0-rc3 == 1.0.6 == 1.0.8
CVE-2007-5947	Low	November 14, 2007 11/14/07	== 2.0.0.2 == 2.0.0.7 == 2.0.0.3 == 2.0.0.6 == 2.0.0.4 <= 2.0.0.9 == 2.0.0.1 == 2.0.0.8 == 2.0.0.5
CVE-2007-5896	High	November 8, 2007 11/8/07	== 2.0.0.9
CVE-2007-5691	Low	October 29, 2007 10/29/07	== 2.0.0.7
CVE-2007-5335	Low	October 24, 2007 10/24/07	<= 2.0.0.7
CVE-2007-5334	Low	October 21, 2007 10/21/07	<= 2.0.0.7
CVE-2007-5337	Low	October 21, 2007 10/21/07	<= 2.0.0.7
CVE-2007-5338	High	October 21, 2007 10/21/07	<= 2.0.0.7
CVE-2007-5339	Low	October 21, 2007 10/21/07	<= 2.0.0.7
CVE-2007-5340	Low	October 21, 2007 10/21/07	<= 2.0.0.7
CVE-2007-5459	Low	October 14, 2007 10/14/07	== 2.0
CVE-2007-5414	Low	October 12, 2007 10/12/07	<= 1.8
CVE-2007-5415	Low	October 12, 2007 10/12/07	== 2.0
CVE-2007-5045	High	September 24, 2007 9/24/07	<= 2.0.0.6
CVE-2007-4879	Medium	September 13, 2007 9/13/07	<= 2.0.0.12 == 0.1 == 0.8 == 1.5-beta2 == 1.5.2 == 1.5.0.6 == 1.8 == 2.0.0.2 == 1.5.0.10 == 1.5.0.3 == 1.5.0.11 == 1.4.1 == 1.5.4 == 1.0.2 == 1.5-beta1 == 1.5 == 0.9.1 == 1.0.4 == 2.0.0.7 == 1.0.7 == 2.0.0.9 == 0.10.1 == 0.9 == 1.5.6 == 0.7 == 0.2 == 0.3 == 1.0 == 1.5.0.7 == 2.0 == 1.0.1 == 0.6 == 0.7.1 == 1.5.0.8 == 2.0.0.3 == 1.5.0.9 == 1.5.0.5 == 1.5.7 == 1.5.0.12 == 2.0.0.6 == 2.0.0.11 == 1.5.0.2 == 1.0.3 == 2.0.0.4 == 0.5 == 0.6.1 == 1.5.1 == 0.9.3 == 2.0.0.1 == 1.5.5 == 0.9.2 == 1.0-preview_release == 2.0.0.8 == 0.9-rc == 1.5.8 == 1.5.3 == 0.4 == 1.5.0.4 == 1.5.0.1 == 0.10 == 1.0.5 == 2.0.0.5 == 2.0.0.10 == 1.0.6 == 1.0.8
CVE-2007-4841	High	September 12, 2007 9/12/07	<= 2.0.0.8
CVE-2007-4357	Medium	August 15, 2007 8/15/07	<= 2.0.0.6
CVE-2007-3844	Low	August 8, 2007 8/8/07	== 2.0.0.5
CVE-2007-3845	High	August 8, 2007 8/8/07	== 2.0.0.5
CVE-2007-4038	Low	July 27, 2007 7/27/07	<= 2.0.0.4
CVE-2007-4041	Medium	July 27, 2007 7/27/07	== 2.0.0.5 == 3.0-alpha
CVE-2007-4013	High	July 26, 2007 7/26/07	*
CVE-2007-3734	High	July 18, 2007 7/18/07	== 2.0.0.2 == 2.0 == 2.0.0.3 == 2.0.0.4 == 2.0.0.1
CVE-2007-3735	High	July 18, 2007 7/18/07	== 2.0.0.2 == 2.0 == 2.0.0.3 == 2.0.0.4 == 2.0.0.1
CVE-2007-3736	Low	July 18, 2007 7/18/07	== 2.0.0.2 == 2.0 == 2.0.0.3 == 2.0.0.4 == 2.0.0.1
CVE-2007-3737	High	July 18, 2007 7/18/07	== 2.0.0.2 == 2.0 == 2.0.0.3 == 2.0.0.4 == 2.0.0.1
CVE-2007-3738	High	July 18, 2007 7/18/07	== 2.0.0.2 == 2.0 == 2.0.0.3 == 2.0.0.4 == 2.0.0.1
CVE-2007-3827	Medium	July 17, 2007 7/17/07	*
CVE-2007-3656	Medium	July 10, 2007 7/10/07	== 1.5.2 == 1.5.0.6 == 1.8 == 1.5.0.10 == 1.5.0.3 == 1.5.0.11 == 1.5.4 == 1.0.2 == 1.5 == 1.0.4 == 1.0.7 == 1.5.6 == 1.0 == 1.5.0.7 == 1.0.1 == 1.5.0.8 == 1.5.0.9 == 1.5.0.5 == 1.5.7 == 1.5.0.12 == 1.5.0.2 == 1.0.3 == 1.5.1 == 1.5.5 == 1.5.8 == 1.5.3 == 1.5.0.4 == 1.5.0.1 == 1.0.5 == 1.0.6 == 1.0.8
CVE-2007-3657	Low	July 10, 2007 7/10/07	== 2.0.0.4
CVE-2007-3670	Low	July 10, 2007 7/10/07	*
CVE-2007-3511	Low	July 3, 2007 7/3/07	== 1.5.0.12 == 2.0.0.6 == 2.0.0.4 <= 2.0.0.7 == 2.0.0.5
CVE-2007-3285	Medium	June 20, 2007 6/20/07	<= 2.0.0.4 == 0.8 == 0.9 == 0.9.1 == 0.9.2 == 0.9.3 == 0.10 == 0.10.1 == 1.0 == 1.0.1 == 1.0.2 == 1.0.3 == 1.0.4 == 1.0.5 == 1.0.6 == 1.0.7 == 1.0.8 == 1.5 == 1.5.0.1 == 1.5.0.2 == 1.5.0.3 == 1.5.0.4 == 1.5.0.5 == 1.5.0.6 == 1.5.0.7 == 1.5.0.8 == 1.5.0.9 == 1.5.0.10 == 1.5.0.11 == 1.5.1 == 1.5.2 == 1.5.3 == 1.5.4 == 1.5.5 == 1.5.6 == 1.5.7 == 1.5.8 == 2.0-rc2 == 2.0-beta1 == 2.0 == 2.0-rc3 == 2.0.0.1 == 2.0.0.2 == 2.0.0.3
CVE-2007-3089	Low	June 6, 2007 6/6/07	== 0.8 == 1.5.2 == 1.5.0.6 == 2.0.0.2 == 1.5.0.10 == 1.5.0.3 == 1.5.0.11 == 1.5.4 == 1.0.2 == 1.5 == 0.9.1 == 1.0.4 == 1.0.7 == 0.10.1 == 0.9 <= 2.0.0.4 == 1.5.6 == 1.0 == 1.5.0.7 == 2.0 == 1.0.1 == 1.5.0.8 == 2.0.0.3 == 1.5.0.9 == 1.5.0.5 == 1.5.7 == 1.5.0.2 == 1.0.3 == 1.5.1 == 0.9.3 == 2.0.0.1 == 1.5.5 == 0.9.2 == 1.5.8 == 1.5.3 == 1.5.0.4 == 1.5.0.1 == 0.10 == 1.0.5 == 1.0.6 == 1.0.8
CVE-2007-3072	High	June 6, 2007 6/6/07	== 2.0.0.2 == 2.0 == 2.0.0.3 == 2.0.0.1
CVE-2007-3073	High	June 6, 2007 6/6/07	<= 2.0.0.4
CVE-2007-3074	Low	June 6, 2007 6/6/07	== 2.0.0.2 == 2.0 == 2.0.0.3 == 2.0.0.4 == 2.0.0.1
CVE-2007-1362	Low	June 1, 2007 6/1/07	== 1.5.2 == 1.5.0.6 == 2.0.0.2 == 1.5.0.10 == 1.5.0.3 == 1.5.0.11 == 1.5.4 == 1.5.6 == 1.5.0.7 == 2.0 == 1.5.0.8 == 2.0.0.3 == 1.5.0.9 == 1.5.0.5 == 1.5.7 == 1.5.0.2 == 1.5.1 == 2.0.0.1 == 1.5.5 == 1.5.8 == 1.5.3 == 1.5.0.4 == 1.5.0.1
CVE-2007-2867	High	June 1, 2007 6/1/07	== 1.5.2 == 1.5.0.6 == 2.0.0.2 == 1.5.0.10 == 1.5.0.3 == 1.5.0.11 == 1.5.4 == 1.5 == 1.5.6 == 1.5.0.7 == 2.0 == 1.5.0.8 == 2.0.0.3 == 1.5.0.9 == 1.5.0.5 == 1.5.7 == 1.5.0.2 == 1.5.1 == 2.0.0.1 == 1.5.5 == 1.5.8 == 1.5.3 == 1.5.0.4 == 1.5.0.1
CVE-2007-2868	High	June 1, 2007 6/1/07	== 1.5.0.6 == 2.0.0.2 == 1.5.0.10 == 1.5.0.3 == 1.5.0.11 == 1.5 == 1.5.0.7 == 2.0 == 1.5.0.8 == 2.0.0.3 == 1.5.0.9 == 1.5.0.5 == 1.5.0.2 == 2.0.0.1 == 1.5.0.4 == 1.5.0.1

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.