Skip to content
Fencer Intel
high 7.7

CVE-2022-1899 json

Out-of-bounds Read in radareorg/radare2

published 4y ago modified 4mo ago also EUVD-2022-25171

cvss
7.7
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.5%
EPSS 1.5% chance of exploitation in 30 days, percentile 74%
public exploits
0
none known

Summary

Out-of-bounds Read in GitHub repository radareorg/radare2 prior to 5.7.0.

Patch / fix

  • radareorg radareorg/radare2 5.7.0
  • radare2 openSUSE Tumbleweed 5.7.0-1.1

opensuse advisories openSUSE-SU-2024:12173-1

  • radare2 Alpine 3.24, Alpine 3.23, Alpine 3.22 +4 more 5.7.0-r0

alpine advisories ALPINE-CVE-2022-1899

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2022-1899 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-1899 updated cvss 5.9

radare2: out of bounds read in string_scan_range

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.48% chance of exploitation in the next 30 days, higher than 74% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • huntr.dev https://huntr.dev/bounties/8a3dc5cb-08b3-4807-82b2-77f08c137a04 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.0 7.7 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:H
NVD 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
NVD 2.0 6.4 AV:N/AC:L/Au:N/C:P/I:N/A:P

Affected products

  • radareorg radareorg/radare2

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.