Radare2 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

5.6.027
5.6.127
5.6.219
5.6.319
5.6.414

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 Fix59
Temporary Fix0
Workaround0
Unavailable0
Not Defined52

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
Functional0
Proof-of-Concept0
Unproven0
Not Defined111

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
Local48
Adjacent10
Network53

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
Low30
None81

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
Required51
None60

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
≤30
≤45
≤514
≤630
≤747
≤815
≤90
≤100

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
≤30
≤45
≤520
≤629
≤745
≤812
≤90
≤100

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
≤32
≤415
≤56
≤648
≤712
≤828
≤90
≤100

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
≤50
≤641
≤70
≤822
≤90
≤100

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
≤51
≤65
≤79
≤819
≤93
≤101

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

<1k26
<2k38
<5k47
<10k0
<25k0
<50k0
<100k0
≥100k0

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

<1k96
<2k14
<5k1
<10k0
<25k0
<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 (59): 1.2.1, 1.3, 1.5, 2, 2.0, 2.0.1, 2.1, 2.2, 2.3, 2.4, 2.5, 2.6, 2.7, 2.8, 3.0, 3.1, 3.1.1, 3.1.2, 3.1.3, 3.2, 3.3, 3.4, 3.5, 3.5.1, 3.6, 3.7, 3.8, 4.0, 4.1, 4.2, 4.3, 4.4, 4.5, 5.0, 5.1, 5.2, 5.3, 5.3.1, 5.4, 5.5, 5.5.1, 5.5.2, 5.5.3, 5.6, 5.6.1, 5.6.2, 5.6.3, 5.6.4, 5.6.5, 5.6.6, 5.6.7, 5.7, 5.7.2, 5.8, 5.8.1, 5.8.2, 5.8.3, 5.8.4, 5.8.5

Software Type: Programming Tool Software

PublishedBaseTempVulnerability0dayTodayExpRemCTICVE
08/20/20225.55.3radare2 Array Length core_java.c off-by-one$0-$5k$0-$5kNot DefinedOfficial Fix0.05CVE-2020-27793
08/20/20226.56.4radare2 adf Command cmd_anal.c anal_fcn_data memory corruption$0-$5k$0-$5kNot DefinedOfficial Fix0.04CVE-2020-27795
08/20/20225.55.3radare2 cmd_info.c cmd_info double free$0-$5k$0-$5kNot DefinedOfficial Fix0.04CVE-2020-27794
07/22/20223.53.5Radare2 Binary File bfile.c r_bin_file_xtr_load_buffer null pointer dereference$0-$5k$0-$5kNot DefinedNot Defined0.04CVE-2022-34520
07/22/20223.53.5Radare2 Binary File wasm.c consume_encoded_name_new heap-based overflow$0-$5k$0-$5kNot DefinedNot Defined0.04CVE-2022-34502
05/26/20226.66.5radare2 out-of-bounds$0-$5k$0-$5kNot DefinedOfficial Fix0.04CVE-2022-1899
05/25/20223.53.5radare2 Binary Symbol Parser bin_symbols.c null pointer dereference$0-$5k$0-$5kNot DefinedNot Defined0.02CVE-2021-44974
05/25/20225.55.5radare2 Mach-O Parser anal_objc.c buffer overflow$0-$5k$0-$5kNot DefinedNot Defined0.03CVE-2021-44975
05/22/20225.95.8radare2 uninitialized pointer$0-$5k$0-$5kNot DefinedOfficial Fix0.03CVE-2022-1809
05/13/20226.66.5radare2 heap-based overflow$0-$5k$0-$5kNot DefinedOfficial Fix0.08CVE-2022-1714
05/10/20226.96.8radare2 mach0.c heap-based overflow$0-$5k$0-$5kNot DefinedOfficial Fix0.03CVE-2022-1649
04/25/20226.26.1radare2 r_bin_java_bootstrap_methods_attr_new out-of-bounds$0-$5k$0-$5kNot DefinedOfficial Fix0.04CVE-2022-1452
04/25/20225.95.8radare2 r_bin_java_constant_value_attr_new out-of-bounds$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2022-1451
04/24/20226.46.3radare2 use after free$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2022-1444
04/22/20225.35.2radare2 heap-based overflow$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2022-1437
04/18/20225.15.0radare2 heap-based overflow$0-$5k$0-$5kNot DefinedOfficial Fix0.06CVE-2022-1383
04/18/20224.04.0radare2 null pointer dereference$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2022-1382
04/11/20225.95.8radare2 r_bin_ne_get_entrypoints out-of-bounds$0-$5k$0-$5kNot DefinedOfficial Fix0.02CVE-2022-1297
04/11/20225.75.6radare2 r_bin_ne_get_relocs out-of-bounds$0-$5k$0-$5kNot DefinedOfficial Fix0.04CVE-2022-1296
04/08/20226.46.3radare2 use after free$0-$5k$0-$5kNot DefinedOfficial Fix0.02CVE-2022-1284
04/08/20225.05.0radare2 r_bin_ne_get_entrypoints null pointer dereference$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2022-1283
04/06/20226.96.8radare2 mach0.c r_str_ncpy heap-based overflow$0-$5k$0-$5kNot DefinedOfficial Fix0.04CVE-2022-1240
04/06/20226.96.8radare2 ne.c heap-based overflow$0-$5k$0-$5kNot DefinedOfficial Fix0.08CVE-2022-1238
04/06/20227.47.3radare2 array index$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2022-1237
04/05/20226.46.3radare2 heap-based overflow$0-$5k$0-$5kNot DefinedOfficial Fix0.07CVE-2022-1244

86 more entries are not shown

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!