Skip to content
Fencer Intel
critical 9.6

CVE-2022-0173 json

Out-of-bounds Read in radareorg/radare2

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

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

Summary

radare2 is vulnerable to Out-of-bounds Read

Patch / fix

  • radareorg radareorg/radare2 Will be fixed in the upcoming r2-5.6.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.6.0-r0

alpine advisories ALPINE-CVE-2022-0173

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-0173 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-0173 updated cvss 5.5

radare2: is vulnerable to Out-of-bounds Read

  • 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.15% chance of exploitation in the next 30 days, higher than 67% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • huntr.dev https://huntr.dev/bounties/727d8600-88bc-4dde-8dea-ee3d192600e5 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.0 9.6 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/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.