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.

326,214

Total vulnerabilities in the database

Vulnerabilities for products matching "freebsd"

Found 1 matching product.

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

freebsd / freebsd

90 vulnerabilities found (with exploits)

Title	Severity	Date	Affected Version
CVE-2009-0641	High	February 20, 2009 2/20/09	== 7.0-release == 7.1-rc1 == 7.0_beta4 == 7.0 == 7.0_releng == 7.1 == 7.0-beta_4 == 7.0-current
CVE-2008-4247	High	September 25, 2008 9/25/08	== 7.0
CVE-2008-2464	High	September 11, 2008 9/11/08	*
CVE-2008-1391	High	March 27, 2008 3/27/08	== 7.0-pre-release == 7.0_beta4 == 7.0 == 6.0_p5_release == 6.0 == 7.0_releng == 6.0-release == 6.0-stable
CVE-2008-1215	Low	March 9, 2008 3/9/08	== 6.3 == 7.0
CVE-2008-0777	Low	February 15, 2008 2/15/08	== 6.3 == 5.5 == 7.0 == 6.2
CVE-2007-3798	Critical	July 16, 2007 7/16/07	== 6.2 == 6.2-p1 == 6.2-p4 == 6.2-p5 == 6.2-p6 >= 6.0 < 6.1 == 6.1 == 6.1-p1 == 6.1-p2 == 6.1-p9 == 6.1-p10 == 6.1-p11 == 6.1-p12 == 6.1-p13 == 6.1-p16 == 6.1-p17 == 6.1-p18 == 6.1-p7 == 6.1-p4 == 6.1-p6 >= 5.0 < 5.5 == 5.5 == 5.5-p1 == 5.5-p11 == 5.5-p12 == 5.5-p13 == 5.5-p2 == 5.5-p3 == 5.5-p4 == 5.5-p5 == 5.5-p7 == 5.5-p8 == 5.5-p9 == 5.5-p14
CVE-2007-0229	High	January 13, 2007 1/13/07	== 6.1
CVE-2007-0166	Medium	January 11, 2007 1/11/07	== 5.3 <= 6.2
CVE-2006-5680	Medium	November 9, 2006 11/9/06	== 6-stable
CVE-2006-5550	Low	October 26, 2006 10/26/06	== 6.1-release == 6.1-release_p10 == 6.1-stable
CVE-2005-4351	Low	December 31, 2005 12/31/05	<= 6.0 == 7.0-current
CVE-2005-0356	Medium	May 31, 2005 5/31/05	== 1.1.5.1 == 2.0 == 2.0.5 == 2.1.0 == 2.1.5 == 2.1.6 == 2.1.6.1 == 2.1.7.1 == 2.2 == 2.2.2 == 2.2.3 == 2.2.4 == 2.2.5 == 2.2.6 == 2.2.8 == 3.0 == 3.0-releng == 3.1 == 3.2 == 3.3 == 3.4 == 3.5 == 3.5-stable == 3.5.1 == 3.5.1-release == 3.5.1-stable == 4.0 == 4.0-alpha == 4.0-releng == 4.1 == 4.1.1 == 4.1.1-release == 4.1.1-stable == 4.10 == 4.10-release == 4.10-release_p8 == 4.10-releng == 4.11-release_p3 == 4.11-releng == 4.11-stable == 4.2 == 4.2-stable == 4.3 == 4.3-release == 4.3-release_p38 == 4.3-releng == 4.3-stable == 4.4 == 4.4-release_p42 == 4.4-releng == 4.4-stable == 4.5 == 4.5-release == 4.5-release_p32 == 4.5-releng == 4.5-stable == 4.6 == 4.6-release == 4.6-release_p20 == 4.6-releng == 4.6-stable == 4.6.2 == 4.7 == 4.7-release == 4.7-release_p17 == 4.7-releng == 4.7-stable == 4.8 == 4.8-pre-release == 4.8-release_p6 == 4.8-releng == 4.9 == 4.9-pre-release == 4.9-releng == 5.0 == 5.0-alpha == 5.0-release_p14 == 5.0-releng == 5.1 == 5.1-alpha == 5.1-release == 5.1-release_p5 == 5.1-releng == 5.2 == 5.2.1-release == 5.2.1-releng == 5.3 == 5.3-release == 5.3-releng == 5.3-stable == 5.4-pre-release == 5.4-release
CVE-2004-0618	Low	December 6, 2004 12/6/04	== 5.1-releng == 5.1-release_p5 == 5.1-release == 5.1-alpha == 4.10-release == 5.1 == 5.2.1-release
CVE-2003-0466	Critical	August 27, 2003 8/27/03	>= 4.0 <= 5.0
CVE-2003-0144	High	March 31, 2003 3/31/03	== 2.2 == 2.2.2 == 2.2.3 == 2.2.4 == 2.2.5 == 2.2.6
CVE-2003-0028	High	March 25, 2003 3/25/03	== 4.1.1-stable == 4.1.1-release == 4.4-stable == 4.5 == 4.5-release == 4.7-stable == 4.2-stable == 4.5-stable == 4.3-release == 4.3-stable == 4.6-release == 4.6-stable == 4.2 == 5.0 == 4.1.1 == 4.4 == 4.7 == 4.3 == 4.6 == 4.0 == 4.1 == 4.7-release == 4.6.2
CVE-2002-0391	Critical	August 12, 2002 8/12/02	<= 4.6.1
CVE-2002-0795	Low	August 12, 2002 8/12/02	== 4.5-stable == 4.5-release
CVE-2002-0572	High	July 3, 2002 7/3/02	== 4.4-releng == 4.5-release == 4.5-stable
CVE-2002-0381	Medium	June 25, 2002 6/25/02	<= 4.5
CVE-2002-0004	High	February 27, 2002 2/27/02	== 4.1.1 == 4.2 == 4.3 == 4.4
CVE-2001-1185	Medium	December 10, 2001 12/10/01	== 4.4
CVE-2001-0710	Medium	September 20, 2001 9/20/01	<= 4.3
CVE-2001-1029	Low	September 20, 2001 9/20/01	<= 4.4
CVE-2001-0554	High	August 14, 2001 8/14/01	== 3.1 == 3.0-releng == 2.2.5 == 2.2.2 == 2.1.7 == 3.5-stable == 2.2.3 == 2.0.5 == 3.5.1 == 4.1 == 2.2.8 == 3.5.1-stable == 2.1.6.1 == 2.2 == 3.0 == 3.2 == 2.2-current == 4.2 == 2.2.4 == 2.1.0 == 2.2.6 == 2.1.6 == 2.1.7.1 == 4.0-releng == 3.3 == 4.0 == 4.1.1 == 4.3 == 3.4 == 2.0.1 == 3.5 == 2.1.5 == 3.5.1-release == 4.0-alpha == 2.2.1 == 2.2.7 == 2.1-stable == 2.0
CVE-2001-1180	High	July 10, 2001 7/10/01	== 4.1 == 4.2 == 4.0 == 4.3
CVE-2001-1244	Medium	July 7, 2001 7/7/01	== 4.3
CVE-2001-0247	High	June 18, 2001 6/18/01	== 3.1 == 2.2.5 == 2.2.2 == 2.2.3 == 3.5.1 == 4.1 == 2.2.8 == 2.2 == 3.0 == 3.2 == 4.2 == 2.2.4 == 2.2.6 == 3.3 == 4.0 == 4.1.1 == 3.4 == 3.5
CVE-2001-0230	Low	June 2, 2001 6/2/01	<= 0.4_1
CVE-2001-0183	High	March 26, 2001 3/26/01	== 3.1 == 3.5.1 == 4.1 == 3.0 == 4.2 == 3.3 == 4.0 == 4.1.1 == 3.4 == 3.5 == 4.0-alpha
CVE-2000-0963	High	December 19, 2000 12/19/00	== 3.4 == 3.5.1 == 4.0 == 4.1 == 4.1.1 == 4.1.1-stable
CVE-2000-0993	High	December 19, 2000 12/19/00	== 3.2 == 3.3 == 3.4 == 3.5 == 4.0
CVE-2000-0595	Low	July 5, 2000 7/5/00	== 3.1 == 3.0 == 3.2 == 3.3 == 4.0 == 3.4
CVE-2000-0532	High	June 7, 2000 6/7/00	== 4.0
CVE-1999-1517	High	November 1, 1999 11/1/99	== 3.3
CVE-1999-1564	Low	September 2, 1999 9/2/99	== 3.2
CVE-1999-1518	Medium	July 15, 1999 7/15/99	== 3.1 == 2.2.5 == 2.2.2 == 2.2.3 == 2.0.5 == 1.1.5.1 == 2.2.8 == 3.0 == 3.2 == 2.2.4 == 2.1.0 == 2.2.6 == 2.1.6 == 2.1.7.1 == 2.1.5 == 2.0
CVE-1999-1402	Low	May 17, 1997 5/17/97	== 3.1 == 2.2.5 == 2.2.2 == 2.2.3 == 2.2.8 == 3.0 == 2.2.4 == 2.2.6
CVE-1999-1572	Low	July 16, 1996 7/16/96	== 2.1.0

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.