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-2019-15879	High	May 13, 2020 5/13/20	== 11.3 == 11.3-p1 == 11.3-p3 == 11.3-p2 == 12.1-p1 == 12.1 == 11.3-p4 == 11.3-p5 == 11.3-p6 == 12.1-p2 == 11.3-p7 == 12.1-p3 == 12.1-p4 == 11.3-p8
CVE-2019-15880	Critical	May 13, 2020 5/13/20	== 12.1-p1 == 12.1 == 12.1-p2 == 12.1-p3 == 12.1-p4
CVE-2020-7452	Critical	April 29, 2020 4/29/20	== 11.3 == 11.3-p1 == 11.3-p3 == 11.3-p2 == 12.1-p1 == 12.1 == 11.3-p4 == 11.3-p5 == 11.3-p6 == 12.1-p2
CVE-2020-7453	Medium	April 29, 2020 4/29/20	== 11.3 == 11.3-p1 == 11.3-p3 == 11.3-p2 == 12.1-p1 == 12.1 == 11.3-p4 == 11.3-p5 == 11.3-p6 == 12.1-p2
CVE-2019-15874	Critical	April 29, 2020 4/29/20	== 11.3 == 11.3-p1 == 11.3-p3 == 11.3-p2 == 12.1-p1 == 12.1 == 11.3-p4 == 11.3-p5 == 11.3-p6 == 12.1-p2 == 11.3-p7 == 12.1-p3
CVE-2019-5614	Critical	April 29, 2020 4/29/20	== 11.3 == 11.3-p1 == 11.3-p3 == 11.3-p2 == 12.1-p1 == 12.1 == 11.3-p4 == 11.3-p5 == 11.3-p6 == 12.1-p2 == 11.3-p7 == 12.1-p3
CVE-2019-15876	Medium	April 28, 2020 4/28/20	== 11.3 == 11.3-p1 == 11.3-p3 == 11.3-p2 == 12.1-p1 == 12.1 == 11.3-p4 == 11.3-p5 == 11.3-p6 == 12.1-p2
CVE-2019-15877	Medium	April 28, 2020 4/28/20	== 12.1-p1 == 12.1 == 12.1-p2
CVE-2020-7451	Medium	April 28, 2020 4/28/20	== 11.3 == 11.3-p1 == 11.3-p3 == 11.3-p2 == 12.1-p1 == 12.1 == 11.3-p4 == 11.3-p5 == 11.3-p6 == 12.1-p2
CVE-2020-1967	High	April 21, 2020 4/21/20	== 12.1
CVE-2020-10565	High	March 14, 2020 3/14/20	< 525916_2020-02-12
CVE-2020-10566	High	March 14, 2020 3/14/20	< 525916_2020-02-12
CVE-2012-5363	High	February 20, 2020 2/20/20	< 9.2
CVE-2012-5365	High	February 20, 2020 2/20/20	< 9.2
CVE-2015-2923	Medium	February 20, 2020 2/20/20	< 10.1
CVE-2014-3879	Critical	February 18, 2020 2/18/20	<= 9.2
CVE-2019-5613	Critical	February 18, 2020 2/18/20	== 12.0-p1 == 12.0 == 12.0-p3 == 12.0-p2 == 12.0-p4 == 12.0-p6 == 12.0-p8 == 12.0-p7 == 12.0-p9 == 12.0-p10 == 12.0-p11 == 12.0-p12
CVE-2020-7450	Critical	February 18, 2020 2/18/20	== 12.0-p1 == 12.0 == 12.0-p3 == 12.0-p2 == 12.0-p4 == 12.0-p6 == 11.3 == 11.3-p1 == 11.3-p3 == 11.3-p2 == 12.0-p8 == 12.1-p1 == 12.1 == 11.3-p4 == 11.3-p5 == 12.0-p7 == 12.0-p9 == 12.0-p10 == 12.0-p11 == 12.0-p12
CVE-2019-15875	Low	February 18, 2020 2/18/20	== 12.0-p1 == 12.0 == 12.0-p3 == 12.0-p2 == 12.0-p4 == 12.0-p6 == 11.3 == 11.3-p1 == 11.3-p3 == 11.3-p2 == 12.0-p8 == 12.1-p1 == 12.1 == 11.3-p4 == 11.3-p5 == 12.0-p7 == 12.0-p9 == 12.0-p10 == 12.0-p11 == 12.0-p12
CVE-2011-3336	High	February 12, 2020 2/12/20	== 8.2
CVE-2012-4576	High	December 2, 2019 12/2/19	== 8.3 == 9.0 == 9.1 == 7.4
CVE-2011-2480	High	November 27, 2019 11/27/19	< 8.2
CVE-2019-5612	High	August 30, 2019 8/30/19	== 11.2-p3 == 11.2-p4 == 11.2-p5 == 12.0-p1 == 11.2-p7 == 12.0 == 11.2 == 11.2-p2 == 11.2-p6 == 11.2-p9 == 12.0-p3 == 11.2-p10 == 12.0-p4 == 12.0-p5 == 11.3 == 11.2-p12 == 11.3-p1 == 11.3-p3 == 11.3-p2 == 11.2-p13 == 11.2-p8 == 11.2-p11 == 12.0-p8
CVE-2019-5608	Critical	August 30, 2019 8/30/19	== 11.2-p3 == 11.2-p4 == 11.2-p5 == 12.0-p1 == 11.2-p7 == 12.0 == 11.2 == 11.2-p2 == 11.2-p6 == 11.2-p9 == 12.0-p3 == 11.2-p10 == 12.0-p4 == 12.0-p5 == 11.3 == 11.2-p12 == 11.3-p1 == 11.3-p3 == 11.3-p2 == 11.2-p13 == 11.2-p8 == 11.2-p11 == 12.0-p8
CVE-2019-5609	High	August 30, 2019 8/30/19	== 11.2-p3 == 11.2-p4 == 11.2-p5 == 12.0-p1 == 11.2-p7 == 12.0 == 11.2 == 11.2-p2 == 11.2-p6 == 11.2-p9 == 12.0-p3 == 11.2-p10 == 12.0-p4 == 12.0-p5 == 11.3 == 11.2-p12 == 11.3-p1 == 11.3-p3 == 11.3-p2 == 11.2-p13 == 11.2-p8 == 11.2-p11 == 12.0-p8
CVE-2019-5610	High	August 30, 2019 8/30/19	== 11.2-p3 == 11.2-p4 == 11.2-p5 == 12.0-p1 == 11.2-p7 == 12.0 == 11.2 == 11.2-p2 == 11.2-p6 == 11.2-p9 == 12.0-p3 == 11.2-p10 == 12.0-p4 == 12.0-p5 == 11.3 == 11.2-p12 == 11.3-p1 == 11.3-p3 == 11.3-p2 == 11.2-p13 == 11.2-p8 == 11.2-p11 == 12.0-p8
CVE-2019-5611	High	August 30, 2019 8/30/19	== 11.2-p3 == 11.2-p4 == 11.2-p5 == 12.0-p1 == 11.2-p7 == 12.0 == 11.2 == 11.2-p2 == 11.2-p6 == 11.2-p9 == 12.0-p3 == 11.2-p10 == 12.0-p4 == 12.0-p5 == 11.3 == 11.2-p12 == 11.3-p1 == 11.3-p3 == 11.3-p2 == 11.2-p13 == 11.2-p8 == 11.2-p11 == 12.0-p8
CVE-2019-5603	High	July 26, 2019 7/26/19	== 11.2-p3 == 11.2-p4 == 11.2-p5 == 12.0-p1 == 11.2-p7 == 12.0 == 11.2 == 11.2-p2 == 11.2-p6 == 11.2-p9 == 12.0-p3 == 11.2-rc3 == 11.2-p10 == 12.0-p2 == 12.0-p4 == 12.0-p5 == 12.0-p6 == 11.0 == 11.3 == 11.2-p8 == 11.2-p11 == 12.0-p7
CVE-2019-5604	Critical	July 26, 2019 7/26/19	== 11.2-p3 == 11.2-p4 == 11.2-p5 == 12.0-p1 == 11.2-p7 == 12.0 == 11.2 == 11.2-p2 == 11.2-p6 == 11.2-p9 == 12.0-p3 == 11.2-rc3 == 11.2-p10 == 12.0-p2 == 12.0-p4 == 12.0-p5 == 12.0-p6 == 11.0 == 11.3 == 11.2-p8 == 11.2-p11 == 12.0-p7
CVE-2019-5605	Medium	July 26, 2019 7/26/19	== 11.2-p3 == 11.2-p4 == 11.2-p5 == 11.2-p7 == 11.2 == 11.2-p2 == 11.2-p6 == 11.2-p9 == 11.2-rc3 == 11.2-p10 == 11.0 == 11.3 == 11.2-p8 == 11.2-p11
CVE-2019-5606	High	July 26, 2019 7/26/19	== 12.0 == 11.2 == 11.0 == 11.3
CVE-2019-5607	High	July 26, 2019 7/26/19	== 12.0 == 11.2 == 11.0 == 11.3
CVE-2019-5600	High	July 3, 2019 7/3/19	== 11.2-p3 == 11.2-p4 == 11.2-p5 == 12.0-p1 == 11.2-p7 == 12.0 == 11.2 == 11.2-p2 == 11.2-p6 == 11.2-p9 == 12.0-p3 == 11.2-rc3 == 11.2-p10 == 11.3-rc3 == 12.0-p2 == 12.0-p4 == 12.0-p5 == 12.0-p6
CVE-2019-5601	Low	July 3, 2019 7/3/19	== 11.2-p3 == 11.2-p4 == 11.2-p5 == 12.0-p1 == 11.2-p7 == 12.0 == 11.2 == 11.2-p2 == 11.2-p6 == 11.2-p9 == 12.0-p3 == 11.2-rc3 == 11.2-p10 == 12.0-p2 == 12.0-p4 == 12.0-p5 == 12.0-p6
CVE-2019-5602	High	July 3, 2019 7/3/19	== 11.2-p3 == 11.2-p4 == 11.2-p5 == 12.0-p1 == 11.2-p7 == 12.0 == 11.2 == 11.2-p2 == 11.2-p6 == 11.2-p9 == 12.0-p3 == 11.2-rc3 == 11.2-p10 == 11.3-rc3 == 12.0-p2 == 12.0-p4 == 12.0-p5 == 12.0-p6
CVE-2019-5599	High	July 2, 2019 7/2/19	== 12.0-p1 == 12.0 == 12.0-p3 == 12.0-p2 == 12.0-p4 == 12.0-p5
CVE-2019-12900	Critical	June 19, 2019 6/19/19	== 11.2-p3 == 11.2-p4 == 11.2-p5 == 12.0-p1 == 11.2-p7 == 12.0 == 11.2 == 11.2-p2 == 11.2-p6 == 11.2-p9 == 12.0-p3 == 11.2-rc3 == 11.2-p10 == 12.0-p2 == 12.0-p4 == 12.0-p5 == 12.0-p6 == 11.3 == 11.2-p12 == 11.3-p1 == 11.2-p8 == 11.2-p11 == 12.0-p8 == 12.0-p7
CVE-2019-5598	Medium	May 15, 2019 5/15/19	== 11.2-p3 == 11.2-p4 == 11.2-p5 == 12.0-p1 == 11.2-p7 == 12.0 == 11.2 == 11.2-p2 == 11.2-p6 == 11.2-p9 == 12.0-p3 == 11.2-rc3
CVE-2019-5597	Medium	May 15, 2019 5/15/19	== 11.2-p3 == 11.2-p4 == 11.2-p5 == 12.0-p1 == 11.2-p7 == 12.0 == 11.2 == 11.2-p2 == 11.2-p6 == 11.2-p9 == 12.0-p3
CVE-2019-9498	High	April 17, 2019 4/17/19	== 11.2-p3 == 11.2-p4 == 11.2-p5 == 12.0-p1 == 11.2-p7 == 12.0 == 11.2 == 11.2-p2 == 11.2-p6 == 11.2-p9 == 12.0-p3 == 12.0-p2 == 11.2-p13 == 11.2-p8 >= 11.0 <= 11.1
CVE-2019-9499	High	April 17, 2019 4/17/19	== 11.2-p3 == 11.2-p4 == 11.2-p5 == 12.0-p1 == 11.2-p7 == 12.0 == 11.2 == 11.2-p2 == 11.2-p6 == 11.2-p9 == 12.0-p3 == 12.0-p2 == 11.2-p13 == 11.2-p8 >= 11.0 <= 11.1
CVE-2019-9494	Medium	April 17, 2019 4/17/19	== 11.2-p3 == 11.2-p4 == 11.2-p5 == 12.0-p1 == 11.2-p7 == 12.0 == 11.2 == 11.2-p2 == 11.2-p6 == 11.2-p9 == 12.0-p3 == 11.2-rc3 == 12.0-p2 == 11.2-p8
CVE-2019-9495	Low	April 17, 2019 4/17/19	== 11.2-p3 == 11.2-p4 == 11.2-p5 == 12.0-p1 == 11.2-p7 == 12.0 == 11.2 == 11.2-p2 == 11.2-p6 == 11.2-p9 == 12.0-p3 == 11.2-rc3 == 12.0-p2 == 11.2-p8
CVE-2019-5595	Low	February 12, 2019 2/12/19	== 12.0 == 11.2
CVE-2019-5596	High	February 12, 2019 2/12/19	== 12.0 == 11.2
CVE-2019-6111	Medium	January 31, 2019 1/31/19	== 12.0-p1 == 12.0 == 12.0-p3 == 12.0-p2 < 12.0
CVE-2018-17161	High	January 3, 2019 1/3/19	== 11.2-p3 == 11.2-p4 == 11.2-p5 == 12.0 == 11.2 == 11.2-p2 == 11.2-p6
CVE-2018-17160	High	December 4, 2018 12/4/18	< 11.2 == 11.2-p5
CVE-2018-17157	High	December 4, 2018 12/4/18	< 11.2 == 11.2-p4
CVE-2018-17158	High	December 4, 2018 12/4/18	< 11.2 == 11.2-p5

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.