Openbsd 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

3.020
3.420
3.115
2.414
3.314

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 Fix101
Temporary Fix0
Workaround2
Unavailable5
Not Defined45

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

High0
Functional2
Proof-of-Concept38
Unproven8
Not Defined105

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
Physical0
Local66
Adjacent21
Network66

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
High0
Low31
None122

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
None151

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
≤31
≤411
≤511
≤651
≤728
≤827
≤916
≤108

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
≤31
≤411
≤525
≤652
≤721
≤831
≤98
≤104

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
≤31
≤414
≤59
≤655
≤722
≤830
≤914
≤108

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
≤40
≤51
≤69
≤71
≤811
≤90
≤103

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

<1k2
<2k11
<5k37
<10k47
<25k39
<50k15
<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

<1k129
<2k6
<5k11
<10k6
<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 (54): 0xb2, 1.1.6, 1.2.4, 1.4.1, 2.0, 2.1, 2.2, 2.3, 2.4, 2.5, 2.6, 2.7, 2.8, 2.9, 3.0, 3.1, 3.2, 3.3, 3.4, 3.5, 3.6, 3.7, 3.8, 3.9, 4.0, 4.1, 4.2, 4.3, 4.4, 4.5, 4.6, 4.7, 4.8, 5.1, 5.2, 5.5, 5.6, 5.7, 5.8, 5.9, 6.0, 6.1, 6.2, 6.3, 6.4, 6.5, 6.6, 6.9, 7.0, 7.1, 7.2, 7.3, 7.3 Errata 013, 7.4

Software Type: Operating System

PublishedBaseTempVulnerability0dayTodayExpRemCTICVE
03/21/20246.36.3OpenBSD/FreeBSD NFS memory corruption$0-$5k$0-$5kNot DefinedNot Defined0.09CVE-2024-29937
03/01/20247.57.2OpenBSD Network Buffer buffer size$5k-$25k$0-$5kNot DefinedOfficial Fix0.06CVE-2023-52558
03/01/20245.35.1OpenBSD npppd buffer size$5k-$25k$0-$5kNot DefinedOfficial Fix0.00CVE-2023-52557
03/01/20245.95.7OpenBSD pf toctou$5k-$25k$0-$5kNot DefinedOfficial Fix0.00CVE-2023-52556
08/10/20235.55.4OpenBSD Console Terminal Emulation memory corruption$5k-$25k$0-$5kNot DefinedOfficial Fix0.06CVE-2023-40216
04/15/20236.36.0OpenBSD/LibreSSL Certificate Chain x509_verify.c improper authentication$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2021-46880
04/12/20235.65.4OpenBSD/LibreSSL x509_verify.c x509_verify_ctx_add_chain certificate validation$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2022-48437
04/05/20235.35.1OpenBSD/OpenSMTPD smtpd ascii_load_sockaddr Local Privilege Escalation$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2023-29323
03/04/20237.57.3OpenBSD TCP Packet tcp_input.c tcp_input denial of service$5k-$25k$0-$5kNot DefinedOfficial Fix0.00CVE-2023-27567
03/26/20224.64.4OpenBSD IPv6 Route heap-based overflow$5k-$25k$0-$5kNot DefinedOfficial Fix0.00CVE-2022-27882
03/26/20224.64.4OpenBSD slaacd engine.c buffer overflow$5k-$25k$0-$5kNot DefinedOfficial Fix0.00CVE-2022-27881
06/22/20214.34.3FreeBSD/OpenBSD ftpd popen.c null pointer dereference$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2010-4816
05/12/20215.45.4OpenBSD WEP/WPA/WPA2/WPA3 injection$5k-$25k$5k-$25kNot DefinedNot Defined0.00CVE-2020-26142
12/12/20197.87.6OpenBSD setuid Program ld.so _dl_setup_env privileges management$5k-$25k$0-$5kProof-of-ConceptNot Defined0.08CVE-2019-19726
12/11/20196.46.4Linux/FreeBSD/OpenBSD/MacOS/iOS/Android VPN channel accessible$5k-$25k$0-$5kNot DefinedNot Defined0.04CVE-2019-14899
12/10/20196.76.7OpenBSD Random Number Generator random.c prng seed$5k-$25k$5k-$25kNot DefinedNot Defined0.07CVE-2012-1577
12/05/20197.87.8OpenBSD S-Key/Yubikey improper authentication$5k-$25k$5k-$25kNot DefinedNot Defined0.04CVE-2019-19522
12/05/20198.58.5OpenBSD libc auth_subr.c improper authentication$5k-$25k$5k-$25kNot DefinedNot Defined0.04CVE-2019-19521
12/05/20196.56.5OpenBSD xlock loader.c privileges management$0-$5k$0-$5kNot DefinedNot Defined0.03CVE-2019-19520
12/05/20196.56.5OpenBSD su.c main input validation$0-$5k$0-$5kNot DefinedNot Defined0.04CVE-2019-19519
08/26/20196.46.4OpenBSD Kernel tcp_sack_option input validation$5k-$25k$5k-$25kNot DefinedOfficial Fix0.02CVE-2019-8460
08/01/20184.44.4OpenBSD IO Port Access Control gdt.c input validation$0-$5k$0-$5kNot DefinedNot Defined0.00CVE-2018-14775
06/19/20176.96.6OpenBSD qsort resource consumption$5k-$25k$0-$5kProof-of-ConceptNot Defined0.04CVE-2017-1000373
06/19/20178.58.1OpenBSD Stack Guard at access control$5k-$25k$0-$5kProof-of-ConceptNot Defined0.03CVE-2017-1000372
03/27/20176.46.1OpenBSD httpd resource management$5k-$25k$0-$5kProof-of-ConceptOfficial Fix0.00CVE-2017-5850

128 more entries are not shown

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!