Skip to content
Fencer Vulns
high 7.3

CVE-2022-1061 json

Heap Buffer Overflow in parseDragons in radareorg/radare2

published 2022-03-24 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-24406

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

Summary

Heap Buffer Overflow in parseDragons in GitHub repository radareorg/radare2 prior to 5.6.8.

Patch / fix

  • radareorg radareorg/radare2 5.6.8
  • 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.8-r0

alpine advisories ALPINE-CVE-2022-1061

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

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-1061 updated cvss 7.3

radare2: heap-based buffer overflow in parseDragons() in libr/bin/p/bin_symbols.c

  • 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

0.93% chance of exploitation in the next 30 days, higher than 60% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • huntr.dev https://huntr.dev/bounties/a7546dae-01c5-4fb0-8a8e-c04ea4e9bac7 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.0 7.3 CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P

Affected products

  • radareorg radareorg/radare2

Classification

Weakness

References

Sources

Fencer Vulns 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.