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.

346,508

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

5745 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2016-1887	High	May 25, 2016 5/25/16	== 10.3 == 10.2 == 10.1
CVE-2016-1886	High	May 25, 2016 5/25/16	== 10.3 == 10.2 == 9.3 == 10.1
CVE-2016-1885	Low	April 12, 2016 4/12/16	== 10.2 == 9.3 == 10.1
CVE-2016-1882	High	January 29, 2016 1/29/16	== 10.2 == 9.3 == 10.1
CVE-2016-1879	High	January 29, 2016 1/29/16	== 10.2 == 9.3 == 10.1
CVE-2014-8611	Medium	September 18, 2015 9/18/15	== 10.1
CVE-2015-1415	Low	April 10, 2015 4/10/15	== 10.0 <= 10.1 == 10.1-rc4 == 10.1-rc2 == 10.1-rc3 == 10.0-rc1 == 10.1-rc1 == 10.0-rc2
CVE-2015-1414	High	February 27, 2015 2/27/15	== 10.0 == 9.0 == 9.1 == 9.2 == 9.3 == 8.4 == 10.1
CVE-2014-8613	High	February 2, 2015 2/2/15	== 9.3 == 8.4 == 10.1
CVE-2014-8612	Low	February 2, 2015 2/2/15	== 10.0 == 9.3 == 8.4 == 10.1
CVE-2014-0998	High	February 2, 2015 2/2/15	== 10.1
CVE-2014-8117	Medium	December 17, 2014 12/17/14	*
CVE-2014-8116	Medium	December 17, 2014 12/17/14	*
CVE-2014-7250	Medium	December 12, 2014 12/12/14	== 5.4
CVE-2014-8475	Low	November 18, 2014 11/18/14	== 10.0 == 9.1 == 9.2
CVE-2014-8476	Low	November 13, 2014 11/13/14	== 10.0 == 9.0-beta1 == 10.1-rc4 == 10.1-rc2 == 10.1-rc3 == 9.0 == 9.1 == 9.2 == 9.3 == 10.1-rc1 == 8.4 == 9.0-beta2 == 10.1
CVE-2014-3711	Medium	October 27, 2014 10/27/14	== 10.0 == 9.3-rc1 == 10.1-rc2 == 10.0-rc1 == 9.1 == 9.2 == 9.3 == 9.2-rc1 == 9.3-rc2 == 10.1-rc1 == 9.2-prerelease == 9.2-rc2 == 10.1 == 10.0-rc2 == 9.1-p4 == 9.1-p5
CVE-2014-3954	High	October 27, 2014 10/27/14	== 10.0 == 9.3-rc1 == 10.1-rc2 == 10.0-rc1 == 9.1 == 9.2 == 9.3 == 9.2-rc1 == 9.3-rc2 == 10.1-rc1 == 9.2-prerelease == 9.2-rc2 == 10.1 == 10.0-rc2 == 9.1-p4 == 9.1-p5
CVE-2014-3955	Medium	October 27, 2014 10/27/14	== 10.0 == 9.0-beta1 == 9.3-rc1 == 10.1-rc2 == 9.0-beta3 == 10.0-rc1 == 9.0 == 9.1 == 9.2 == 9.3 == 9.2-rc1 == 9.3-rc2 == 10.1-rc1 == 8.4 == 9.0-beta2 == 9.2-prerelease == 9.2-rc2 == 10.1 == 10.0-rc2 == 9.1-p4 == 9.1-p5
CVE-2014-3951	Medium	August 21, 2014 8/21/14	== 10.0
CVE-2014-5384	Medium	August 21, 2014 8/21/14	== 10.0
CVE-2014-3952	Low	July 15, 2014 7/15/14	== 10.0 == 9.1 == 9.2 == 8.4
CVE-2014-3953	Low	July 15, 2014 7/15/14	== 10.0 == 9.1 == 9.2 == 8.4
CVE-2014-3873	Low	June 10, 2014 6/10/14	== 9.1 == 9.2 == 8.4 == 9.3-beta1
CVE-2014-3880	Low	June 10, 2014 6/10/14	== 10.0 == 9.1 == 9.2 == 8.4
CVE-2014-3956	Low	June 4, 2014 6/4/14	<= 9.2
CVE-2014-3000	High	May 2, 2014 5/2/14	== 10.0 == 9.1 == 9.2 == 8.4 == 8.3
CVE-2014-3001	Medium	May 2, 2014 5/2/14	== 10.0
CVE-2014-1453	Low	April 16, 2014 4/16/14	== 10.0 == 9.0-beta1 == 9.0-beta3 == 9.0 == 9.1 == 9.2 == 9.2-rc1 == 8.4 == 9.0-beta2 == 9.2-prerelease == 9.2-rc2 == 8.3 == 9.1-p4 == 9.1-p5
CVE-2014-1452	Medium	January 21, 2014 1/21/14	== 10.0 == 9.0 == 9.1 == 9.2 == 9.2-rc1 == 8.4 == 9.2-prerelease == 9.2-rc2 == 8.3 == 9.1-p4 == 9.1-p5
CVE-2013-6832	Low	November 21, 2013 11/21/13	== 5.2.1 == 7.4 == 6.1 == 3.1 == 6.4 == 6.3 == 2.2.5 == 5.5 == 8.2 == 5.4 == 5.3 == 2.2.2 == 2.1.7 == 4.11 == 2.2.3 == 2.0.5 == 8.0 == 1.1.5.1 == 9.0 == 9.1 == 4.5 == 3.5.1 == 4.7 == 7.0 == 9.2 == 4.1 == 2.2.8 == 6.0 == 4.4 == 1.0 == 5.1 == 2.1.6.1 == 7.3 == 2.2 == 3.0 == 5.2 <= 10.0 == 3.2 == 1.1 == 8.1 == 2.1 == 4.8 == 4.2 == 6.2 == 1.5 == 2.2.4 == 2.1.0 == 2.2.6 == 1.1.5 == 0.4_1 == 2.1.6 == 2.1.7.1 == 7.1 == 7.2 == 3.3 == 4.0 == 4.1.1 == 8.4 == 4.6 == 4.3 == 4.10 == 3.4 == 2.0.1 == 3.5 == 1.2 == 5.0 == 2.1.5 == 2.2.1 == 4.9 == 4.6.2 == 2.2.7 == 8.3 == 2.0
CVE-2013-6833	Low	November 21, 2013 11/21/13	== 5.2.1 == 7.4 == 6.1 == 3.1 == 6.4 == 6.3 == 2.2.5 == 5.5 == 8.2 == 5.4 == 5.3 == 2.2.2 == 2.1.7 == 4.11 == 2.2.3 == 2.0.5 == 8.0 == 1.1.5.1 == 9.0 == 9.1 == 4.5 == 3.5.1 == 4.7 == 7.0 == 9.2 == 4.1 == 2.2.8 == 6.0 == 4.4 == 1.0 == 5.1 == 2.1.6.1 == 7.3 == 2.2 == 3.0 == 5.2 <= 10.0 == 3.2 == 1.1 == 8.1 == 2.1 == 4.8 == 4.2 == 6.2 == 1.5 == 2.2.4 == 2.1.0 == 2.2.6 == 1.1.5 == 0.4_1 == 2.1.6 == 2.1.7.1 == 7.1 == 7.2 == 3.3 == 4.0 == 4.1.1 == 8.4 == 4.6 == 4.3 == 4.10 == 3.4 == 2.0.1 == 3.5 == 1.2 == 5.0 == 2.1.5 == 2.2.1 == 4.9 == 4.6.2 == 2.2.7 == 8.3 == 2.0
CVE-2013-6834	Low	November 21, 2013 11/21/13	== 5.2.1 == 7.4 == 6.1 == 3.1 == 6.4 == 6.3 == 2.2.5 == 5.5 == 8.2 == 5.4 == 5.3 == 2.2.2 == 2.1.7 == 4.11 == 2.2.3 == 2.0.5 == 8.0 == 1.1.5.1 == 9.0 == 9.1 == 4.5 == 3.5.1 == 4.7 == 7.0 == 9.2 == 4.1 == 2.2.8 == 6.0 == 4.4 == 1.0 == 5.1 == 2.1.6.1 == 7.3 == 2.2 == 3.0 == 5.2 <= 10.0 == 3.2 == 1.1 == 8.1 == 2.1 == 4.8 == 4.2 == 6.2 == 1.5 == 2.2.4 == 2.1.0 == 2.2.6 == 1.1.5 == 0.4_1 == 2.1.6 == 2.1.7.1 == 7.1 == 7.2 == 3.3 == 4.0 == 4.1.1 == 8.4 == 4.6 == 4.3 == 4.10 == 3.4 == 2.0.1 == 3.5 == 1.2 == 5.0 == 2.1.5 == 2.2.1 == 4.9 == 4.6.2 == 2.2.7 == 8.3 == 2.0
CVE-2013-0211	Medium	September 30, 2013 9/30/13	== 9.3
CVE-2013-5666	Low	September 23, 2013 9/23/13	== 9.2-rc1 == 9.2-rc2
CVE-2013-5710	Low	September 23, 2013 9/23/13	== 8.0 == 9.0 == 9.1 == 9.2 == 8.4 == 8.3
CVE-2013-5691	Medium	September 23, 2013 9/23/13	== 9.0 == 9.1 == 9.2 == 8.3
CVE-2013-5209	High	August 29, 2013 8/29/13	== 9.0 == 9.1 == 9.2-prerelease == 8.3 == 9.1-p4 == 9.1-p5
CVE-2013-3077	High	August 28, 2013 8/28/13	== 9.0 == 9.1 == 9.2-prerelease == 8.3 == 9.1-p4 == 9.1-p5
CVE-2013-4851	Medium	July 29, 2013 7/29/13	== 9.0 == 9.1 == 8.3 == 9.1-p4 == 9.1-p5
CVE-2013-4854	High	July 29, 2013 7/29/13	== 8.2 == 8.0 == 9.0 == 9.1 == 9.2-rc1 == 8.1 == 8.4 == 9.2-prerelease == 9.2-rc2 == 8.3 == 9.1-p4 == 9.1-p5
CVE-2013-2171	Medium	July 2, 2013 7/2/13	== 9.0 == 9.1 == 9.1-p4
CVE-2013-3266	High	May 2, 2013 5/2/13	== 8.2 == 8.0 == 9.0 == 9.1 == 8.1 == 8.3
CVE-2012-3549	High	October 9, 2012 10/9/12	== 8.2
CVE-2006-7252	Medium	July 25, 2012 7/25/12	== 6.4
CVE-2007-6754	Medium	July 25, 2012 7/25/12	== 6.4
CVE-2012-2143	Low	July 5, 2012 7/5/12	== 5.2.1 == 7.4 == 6.1 == 3.1 == 6.4 == 6.3 == 2.2.5 == 5.5 == 8.2 == 5.4 == 5.3 == 2.2.2 == 2.1.7 == 4.11 == 2.0.5 == 8.0 == 1.1.5.1 == 4.5 == 4.7 == 7.0 <= 9.0 == 4.1 == 2.2.8 == 6.0 == 4.4 == 1.0 == 5.1 == 7.3 == 2.2 == 3.0 == 5.2 == 3.2 == 1.1 == 8.1 == 2.1 == 4.8 == 4.2 == 6.2 == 2.2.6 == 1.1.5 == 2.1.6 == 7.1 == 7.2 == 3.3 == 4.0 == 4.1.1 == 4.6 == 4.3 == 4.10 == 3.4 == 3.5 == 5.0 == 2.1.5 == 2.2.1 == 4.9 == 4.6.2 == 2.2.7 == 8.3 == 2.0
CVE-2012-0217	High	June 12, 2012 6/12/12	<= 9.0
CVE-2011-2393	High	February 2, 2012 2/2/12	*
CVE-2011-4862	High	December 25, 2011 12/25/11	>= 7.3 <= 9.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.