Freebsd Vulnerabilities

Timeline

The analysis of the timeline helps to identify the required approach and handling of single vulnerabilities and vulnerability collections. This overview makes it possible to see less important slices and more severe hotspots at a glance. Initiating immediate vulnerability response and prioritizing of issues is possible.

Last Year

The analysis of the timeline helps to identify the required approach and handling of single vulnerabilities and vulnerability collections. This overview makes it possible to see less important slices and more severe hotspots at a glance. Initiating immediate vulnerability response and prioritizing of issues is possible.

Version

11.060
11.153
11.245
11.342
10.139

Grouping all affected versions of a specific product helps to determine existing issues. This makes it possible to determine vendors and products which need attention when it comes to remediations.

Remediation

Official Fix332
Temporary Fix0
Workaround4
Unavailable5
Not Defined72

Vendors and researchers are eager to find countermeasures to mitigate security vulnerabilities. These can be distinguished between multiple forms and levels of remediation which influence risks differently.

Exploitability

High6
Functional3
Proof-of-Concept99
Unproven36
Not Defined269

Researcher and attacker which are looking for security vulnerabilities try to exploit them for academic purposes or personal gain. The level and quality of exploitability can be distinguished to determine simplicity and strength of attacks.

Access Vector

Not Defined0
Physical2
Local185
Adjacent48
Network178

The approach a vulnerability it becomes important to use the expected access vector. This is typically via the network, local, or physically even.

Authentication

Not Defined0
High5
Low102
None306

To exploit a vulnerability a certail level of authentication might be required. Vulnerabilities without such a requirement are much more popular.

User Interaction

Not Defined0
Required2
None411

Some attack scenarios require some user interaction by a victim. This is typical for phishing, social engineering and cross site scripting attacks.

C3BM Index

Our unique C3BM Index (CVSSv3 Base Meta Index) cumulates the CVSSv3 Meta Base Scores of all entries over time. Comparing this index to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

Last Year

Our unique C3BM Index (CVSSv3 Base Meta Index) cumulates the CVSSv3 Meta Base Scores of all entries over time. Comparing this index to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

CVSSv3 Base

≤10
≤20
≤36
≤445
≤527
≤6105
≤758
≤880
≤956
≤1036

The Common Vulnerability Scoring System (CVSS) is an industry standard to define the characteristics and impacts of security vulnerabilities. The base score represents the intrinsic aspects that are constant over time and across user environments. Our unique meta score merges all available scores from different sources to aggregate to the most reliable result.

CVSSv3 Temp

≤10
≤20
≤38
≤450
≤543
≤6109
≤766
≤875
≤950
≤1012

The Common Vulnerability Scoring System (CVSS) uses temp scores to reflect the characteristics of a vulnerability that may change over time but not across user environments. This includes reporting confidence, exploitability and remediation levels. We do also provide our unique meta score for temp scores, even though other sources rarely publish them.

VulDB

≤10
≤20
≤37
≤455
≤525
≤6123
≤739
≤885
≤941
≤1038

The moderation team is always defining the base vector and base score for an entry. These and all other available scores are used to generate the meta score.

NVD

≤10
≤20
≤30
≤43
≤50
≤620
≤711
≤851
≤96
≤1020

The National Vulnerability Database (NVD) is also defining CVSS vectors and scores. These are usually not complete and might differ from VulDB scores.

CNA

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤81
≤90
≤100

A CVE Numbering Authority (CNA) is responsible for assigning new CVE entries. They might also include a CVSS score. These are usually not complete and might differ from VulDB scores.

Vendor

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

Some vendors are willing to publish their own CVSS vectors and scores for vulnerabilities in their products. The coverage varies from vendor to vendor.

Research

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

There are sometimes also security researcher which provide their own CVSS vectors and scores for vulnerabilities they have found and published.

Exploit 0-day

<1k4
<2k14
<5k53
<10k125
<25k176
<50k39
<100k1
≥100k1

The moderation team is working with the threat intelligence team to determine prices for exploits. Our unique algorithm is used to identify the 0-day prices for an exploit, before it got distributed or became public. Calculated prices are aligned to prices disclosed by vulnerability broker and compared to prices we see on exploit markets.

Exploit Today

<1k366
<2k21
<5k17
<10k8
<25k1
<50k0
<100k0
≥100k0

The 0-day prices do not consider time-relevant factors. The today price does reflect price impacts like disclosure of vulnerability details, alternative exploits, availability of countermeasures. These dynamic aspects might decrease the exploit prices over time. Under certain circumstances this happens very fast.

Exploit Market Volume

Our unique calculation of exploit prices makes it possible to forecast the expected exploit market volume. The calculated prices for all possible 0-day expoits are cumulated for this task. Comparing the volume to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

Last Year

Our unique calculation of exploit prices makes it possible to forecast the expected exploit market volume. The calculated prices for all possible 0-day expoits are cumulated for this task. Comparing the volume to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

🔴 CTI Activities

Our unique Cyber Threat Intelligence aims to determine the ongoing research of actors to anticipiate their acitivities. Observing exploit markets on the Darknet, discussions of vulnerabilities on mailinglists, and exchanges on social media makes it possible to identify planned attacks. Monitored actors and activities are classified whether they are offensive or defensive. They are also weighted as some actors are well-known for certain products and technologies. And some of their disclosures might contain more or less details about technical aspects and personal context. The world map highlights active actors in real-time.

Affected Versions (135): 0.4.7, 0.4e, 1.0, 1.1, 1.1.5, 1.1.5.1, 1.5, 2.0, 2.0.5, 2.1, 2.1.5, 2.1.6, 2.1.6.1, 2.1.7, 2.1.7.1, 2.2, 2.2.1, 2.2.2, 2.2.3, 2.2.4, 2.2.5, 2.2.6, 2.2.7, 2.2.8, 3.0, 3.1, 3.2, 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.5, 3.2.6, 3.2.7, 3.2.8, 3.2.9, 3.2.11, 3.2.12, 3.3, 3.4, 3.5, 3.5.1, 3.113+5.3, 4, 4.0, 4.1, 4.1.1, 4.2, 4.3, 4.4, 4.5, 4.6, 4.6.1, 4.6.2, 4.7, 4.8, 4.9, 4.10, 4.11, 5, 5.0, 5.1, 5.2, 5.2.1, 5.3, 5.4, 5.5, 6, 6.0, 6.0 P5 Release, 6.0-STABLE, 6.1, 6.2, 6.2 Releng, 6.3, 6.3 Releng, 6.4, 7.0, 7.0 Beta4, 7.0 Releng, 7.0-release, 7.1, 7.2, 7.3, 7.4, 8.0, 8.1, 8.1-prerelease, 8.2, 8.3, 8.4, 9.0, 9.1, 9.2, 9.3, 10, 10.0, 10.1, 10.2, 10.3, 10.3-RELEASE-p6, 10.4, 10.4-RELEASE-p9, 11.0, 11.1, 11.1-RELEASE-p11, 11.2, 11.3, 11.3 p9, 11.4, 11.4-RC2, 11.4-RELEASE, 11.4-STABLE, 12.0, 12.0-RELEASE-p12, 12.1, 12.1 p5, 12.2, 12.2-RELEASE, 12.2-STAB, 12.2-STABLE, 12.3, 12.4, 12.4-RELEASE-p6, 13-RELEASE-p4, 13.0, 13.0-RC5, 13.0-RELE, 13.0-RELEASE, 13.0-STABLE, 13.1, 13.2, 13.2-RELEASE-p4, 14.0, CVE-2010-4670

Software Type: Operating System

PublishedBaseTempVulnerability0dayTodayExpRemCTICVE
03/21/20246.36.3OpenBSD/FreeBSD NFS memory corruption$0-$5k$0-$5kNot DefinedNot Defined0.09CVE-2024-29937
02/15/20243.33.2FreeBSD Virtual Memory System information disclosure$0-$5k$0-$5kNot DefinedOfficial Fix0.02CVE-2022-23091
02/15/20248.07.6FreeBSD aio_aqueue use after free$5k-$25k$0-$5kNot DefinedOfficial Fix0.04CVE-2022-23090
02/15/20243.53.4FreeBSD proc_getargv out-of-bounds$5k-$25k$0-$5kNot DefinedOfficial Fix0.04CVE-2022-23089
02/15/20245.55.3FreeBSD lib9p memory corruption$5k-$25k$0-$5kNot DefinedOfficial Fix0.02CVE-2022-23092
02/15/20244.64.4FreeBSD e1000 Device Model stack-based overflow$5k-$25k$0-$5kNot DefinedOfficial Fix0.03CVE-2022-23087
02/15/20248.17.7FreeBSD IEEE 802.11s Mesh ID heap-based overflow$5k-$25k$5k-$25kNot DefinedOfficial Fix0.00CVE-2022-23088
02/14/20242.42.3FreeBSD bhyveload information disclosure$0-$5k$0-$5kNot DefinedOfficial Fix0.02CVE-2024-25940
02/14/20244.34.1FreeBSD jail information disclosure$5k-$25k$0-$5kNot DefinedOfficial Fix0.03CVE-2024-25941
12/13/20235.95.8FreeBSD NFS Client memory corruption$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2023-6660
12/06/20235.65.5FreeBSD pf access control$5k-$25k$0-$5kNot DefinedOfficial Fix0.02CVE-2023-6534
11/08/20237.67.5FreeBSD libc __sflush out-of-bounds write$5k-$25k$0-$5kNot DefinedOfficial Fix0.00CVE-2023-5941
11/08/20236.56.4FreeBSD Setting cap_net privileges management$5k-$25k$0-$5kNot DefinedOfficial Fix0.05CVE-2023-5978
10/04/20235.65.4FreeBSD Speculative Execution initialization$5k-$25k$0-$5kNot DefinedOfficial Fix0.00CVE-2023-5370
10/04/20236.26.1FreeBSD Capsicum copy_file_range system dropped privileges$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2023-5369
10/04/20235.95.8FreeBSD msdosfs Filesystem ftruncate insecure default initialization of resource$0-$5k$0-$5kNot DefinedOfficial Fix0.04CVE-2023-5368
09/07/20235.35.1FreeBSD IPv6 Fragmented Packet additional special element$5k-$25k$0-$5kNot DefinedOfficial Fix0.04CVE-2023-4809
08/02/20237.57.5FreeBSD IPv6 Packet integer overflow$5k-$25k$5k-$25kNot DefinedNot Defined0.05CVE-2023-3107
08/02/20237.17.1FreeBSD fwctl Driver buffer overflow$5k-$25k$5k-$25kNot DefinedNot Defined0.00CVE-2023-3494
06/22/20237.27.1FreeBSD pam_krb5 unknown vulnerability$5k-$25k$0-$5kNot DefinedOfficial Fix0.04CVE-2023-3326
02/08/20234.54.5FreeBSD GELI missing encryption$5k-$25k$0-$5kNot DefinedOfficial Fix0.00CVE-2023-0751
12/01/20227.37.0FreeBSD Ping pr_pack stack-based overflow$5k-$25k$0-$5kNot DefinedOfficial Fix0.04CVE-2022-23093
10/18/20227.26.9FreeBSD Kernel toctou$5k-$25k$0-$5kNot DefinedOfficial Fix0.00CVE-2022-23084
10/18/20227.26.9FreeBSD Kernel access control$5k-$25k$0-$5kNot DefinedOfficial Fix0.00CVE-2022-23085
10/18/20227.26.9FreeBSD Kernel heap-based overflow$5k-$25k$0-$5kNot DefinedOfficial Fix0.03CVE-2022-23086

388 more entries are not shown

Want to stay up to date on a daily basis?

Enable the mail alert feature now!