Vulnerability Database

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 Exploit Date Affected Version
CVE-2004-0125
High August 6, 2004 8/6/04
== 4.3-releng
== 4.1.1-stable
== 4.6-releng
== 4.1.1-release
== 4.4-stable
== 4.6-stable
== 4.8-release_p6
== 4.6-release
== 4.3-stable
== 4.7-stable
== 4.3-release_p38
== 4.5-stable
== 4.6-release_p20
== 4.5-release
== 4.3-release
== 4.7-releng
== 4.2-stable
== 4.5
== 4.4-release_p42
== 4.7
== 4.1
== 4.4-releng
== 4.4
== 4.9-releng
== 4.7-release_p17
== 4.9-pre-release
== 4.8-pre-release
== 4.5-release_p32
== 4.8
== 4.2
== 4.0-releng
== 4.0
== 4.1.1
== 4.6
== 4.3
== 4.10
== 4.5-releng
== 4.8-releng
== 4.0-alpha
== 4.7-release
== 4.9
== 4.6.2
CVE-2004-0370
Low May 4, 2004 5/4/04
== 5.2
CVE-2004-0126
Low March 29, 2004 3/29/04
== 5.1-release
== 5.1
== 5.2
== 5.2.1-release
CVE-2004-0171
Medium March 15, 2004 3/15/04
== 4.7
== 5.1
== 5.2
== 4.8
== 5.0
== 4.9
== 4.6.2
CVE-2004-0002
High March 3, 2004 3/3/04
== 4.3-releng
== 4.1.1-stable
== 4.6-releng
== 3.1
== 4.1.1-release
== 3.0-releng
== 5.1-releng
== 4.4-stable
== 4.6-stable
== 4.8-release_p6
== 4.6-release
== 5.1-release_p5
== 4.3-stable
== 4.7-stable
== 5.0-release_p14
== 3.5-stable
== 4.3-release_p38
== 4.5-stable
== 4.6-release_p20
== 4.5-release
== 5.0-releng
== 4.3-release
== 4.7-releng
== 4.2-stable
== 4.5
== 3.5.1
== 4.4-release_p42
== 4.7
== 4.1
== 3.5.1-stable
== 4.4-releng
== 4.4
== 5.1
== 4.7-release_p17
== 4.9-pre-release
== 3.0
== 4.8-pre-release
== 5.2
== 3.2
== 4.5-release_p32
== 4.8
== 4.2
== 4.0-releng
== 3.3
== 4.0
== 4.1.1
== 4.6
== 4.3
== 3.4
== 3.5
== 5.0-alpha
== 4.5-releng
== 4.8-releng
== 5.0
== 3.5.1-release
== 4.0-alpha
== 4.7-release
== 4.9
== 4.6.2
CVE-2004-0099
Low March 3, 2004 3/3/04
== 5.1-release
== 5.2.1-release
CVE-2004-0114
Low March 3, 2004 3/3/04
<= 5.2
CVE-2003-1234
Low December 31, 2003 12/31/03
== 3.1
== 2.2.5
== 4.6-release
== 2.2.2
== 2.1.7
== 4.11
== 2.2.3
== 4.5-release
== 1.1.5.1
== 2.1.6.1
== 2.2-current
== 4.10-release
== 4.10-release_p8
== 4.3-release
== 4.4
== 4.9-releng
== 4.11-releng
== 2.1.0
== 2.2.4
== 3.2
== 4.10-releng
== 4.11-release_p3
== 4.5
== 2.2
== 2.2.8
== 4.2
== 4.7
== 2.1.6
== 2.2.1
== 2.2.6
== 3.4
== 3.5
== 4.11-stable
== 4.6
== 2.1.5
== 3.3
== 5.0
== 2.1.7.1
== 2.2.7
== 3.5.1-release
== 4.10
== 4.3
== 4.7-release
CVE-2003-0914
Low December 15, 2003 12/15/03
== 4.7
== 4.8
== 4.4
== 4.5
== 4.6
== 4.6.2
== 4.9
== 5.0
CVE-2003-0804
Medium November 17, 2003 11/17/03
== 4.5
== 4.0
== 4.1
== 4.1.1
== 4.6
== 4.7
== 4.8
== 4.3
== 4.9-pre-release
== 5.1
== 4.2
== 4.4
== 4.6.2
== 5.0
CVE-2003-0688
Medium October 20, 2003 10/20/03
== 4.7
== 4.8
== 4.6
== 5.0
CVE-2003-0694
High October 6, 2003 10/6/03
== 4.3-releng
== 4.6-releng
== 3.0-releng
== 4.3-release_p38
== 4.8-release_p6
== 4.6-release_p20
== 5.1-release_p5
== 5.1-releng
== 5.0-release_p14
== 5.0-releng
== 4.7-release_p17
== 4.7-releng
== 4.4-release_p42
== 4.4-releng
== 4.9-pre-release
== 4.5-release_p32
== 4.8-releng
== 4.0-releng
== 4.5-releng
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.5
== 2.2.2
== 2.2.3
== 2.2.4
== 2.2.6
== 2.2
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-2003-0078
Medium March 3, 2003 3/3/03
== 4.5
== 4.7
== 4.4
== 4.2
== 4.6
== 4.3
== 5.0
CVE-2003-0015
High February 7, 2003 2/7/03
== 4.5
== 4.7
== 4.4
== 4.6
== 5.0
CVE-2003-0001
Medium January 17, 2003 1/17/03
== 4.7
== 4.2
== 4.4
== 4.5
== 4.6
== 4.3
CVE-2002-1667
Low December 31, 2002 12/31/02
== 4.5-stable
== 4.5-release
CVE-2002-1669
Low December 31, 2002 12/31/02
== 4.4
== 4.2
== 4.3
CVE-2002-1674
Low December 31, 2002 12/31/02
== 4.5
== 4.1
== 4.4
== 4.2
== 4.1.1
== 4.3
CVE-2002-1915
Medium December 31, 2002 12/31/02
== 4.5
== 3.5.1
== 4.1
== 4.4
== 4.2
== 4.0
== 4.1.1
== 4.6
== 4.3
== 3.5
== 5.0
CVE-2002-2092
Low December 31, 2002 12/31/02
== 4.3-releng
== 4.1.1-stable
== 3.1
== 4.1.1-release
== 2.2.5
== 4.4-stable
== 4.3-stable
== 2.2.2
== 2.2.3
== 4.3-release
== 4.2-stable
== 3.5.1
== 4.1
== 2.2.8
== 4.4-releng
== 4.4
== 2.2
== 3.0
== 3.2
== 4.2
== 2.2.4
== 2.1.0
== 2.2.6
== 3.3
== 4.0
== 4.1.1
== 4.3
== 3.4
== 3.5
== 2.0
CVE-2002-1219
High November 29, 2002 11/29/02
== 4.5
== 4.7
== 4.4
== 4.6
CVE-2002-1220
Medium November 29, 2002 11/29/02
== 4.5
== 4.7
== 4.4
== 4.6
CVE-2002-1221
Medium November 29, 2002 11/29/02
== 4.5
== 4.7
== 4.4
== 4.6
CVE-2002-0666
Medium November 4, 2002 11/4/02
== 4.6-stable
== 4.6-release
== 4.6
CVE-2002-0973
Low September 24, 2002 9/24/02
== 4.1.1-stable
== 4.1.1-release
== 4.4-stable
== 4.6-release
== 4.3-stable
== 4.5-stable
== 4.5-release
== 4.3-release
== 4.2-stable
== 4.5
== 4.1
== 4.4
== 4.2
== 4.0
== 4.1.1
== 4.6
== 4.3
== 4.6.1-release_p10
CVE-2002-1125
Low September 24, 2002 9/24/02
== 4.5
== 4.4
== 4.2
== 4.6
== 4.3
CVE-2002-0391
Critical August 12, 2002 8/12/02
<= 4.6.1
CVE-2002-0414
High August 12, 2002 8/12/02
== 4.5
== 4.4
== 4.2
== 4.3
CVE-2002-0518
Medium August 12, 2002 8/12/02
== 4.5-stable
== 4.5-release
CVE-2002-0754
High August 12, 2002 8/12/02
== 4.1.1-stable
== 4.1.1-release
== 4.3-stable
== 4.3-release
== 4.2-stable
== 4.1
== 4.4
== 4.2
== 4.0
== 4.1.1
== 4.3
CVE-2002-0755
High August 12, 2002 8/12/02
== 4.5-release
== 4.4-release
CVE-2002-0794
Medium August 12, 2002 8/12/02
== 4.5-release
CVE-2002-0795
Low August 12, 2002 8/12/02
== 4.5-stable
== 4.5-release
CVE-2002-0820
High August 12, 2002 8/12/02
== 4.6
CVE-2002-0829
Low August 12, 2002 8/12/02
<= 4.6.1
CVE-2002-0830
Medium August 12, 2002 8/12/02
<= 4.6.1
CVE-2002-0831
Low August 12, 2002 8/12/02
== 4.6-stable
== 4.6-release
== 4.5-release
== 4.3-release
== 4.4-release
CVE-2002-0701
Low July 23, 2002 7/23/02
== 6.2-stable
CVE-2002-0572
High July 3, 2002 7/3/02
== 4.5-stable
== 4.5-release
== 4.4-releng
CVE-2002-0574
Medium July 3, 2002 7/3/02
<= 4.5
CVE-2002-0381
Medium June 25, 2002 6/25/02
<= 4.5
CVE-2002-0062
High March 8, 2002 3/8/02
== 3.1
== 3.5.1
== 4.1
== 3.2
== 3.3
== 4.0
== 4.1.1
== 3.4
== 3.5
== 5.0
CVE-2002-0004
High February 27, 2002 2/27/02
== 4.4
== 4.2
== 4.1.1
== 4.3
CVE-2001-1185
Medium December 10, 2001 12/10/01
== 4.4
CVE-2001-0796
Medium December 6, 2001 12/6/01
== 3.0
CVE-2001-0670
High October 3, 2001 10/3/01
<= 4.3
CVE-2001-1034
High September 23, 2001 9/23/01
== 4.4

Frequently Asked Questions

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.