# CVE-2022-28069: Memory corruption in n/a

> A heap buffer overflow in radare2 allows attackers to execute arbitrary code or cause a denial of service via crafted binaries.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Aug 2023
- **Updated:** 3 Oct 2024
- **Also known as:** GHSA-jhh7-xjx4-wfw5, UBUNTU-CVE-2022-28069

## What is CVE-2022-28069?

CVE-2022-28069 is a high-severity memory corruption vulnerability in Radare Radare2, published on 22 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A heap buffer overflow in vax_opfunction in radare2 5.4.2 and 5.4.0.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2022-28069?

It affects 1 product.


Products: Radare Radare2.

## How do I fix CVE-2022-28069?

No fix has been published for CVE-2022-28069 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-28069 being exploited?

There is no known exploitation of CVE-2022-28069 in the wild and no public exploit code.

## Other vulnerabilities in Radare Radare2

- [CVE-2025-1864](https://insights.sbomify.com/CVE-2025-1864/): Buffer Overflow and Potential Code Execution in Radare2 (critical 10.0)
- [CVE-2025-1744](https://insights.sbomify.com/CVE-2025-1744/): Out-of-bounds Write in radare2 (critical 10.0)
- [CVE-2021-32494](https://insights.sbomify.com/CVE-2021-32494/): Denial of service in radare2 (critical 10.0)
- [CVE-2021-32495](https://insights.sbomify.com/CVE-2021-32495/): Use after free in radare2 (critical 10.0)
- [CVE-2024-29646](https://insights.sbomify.com/CVE-2024-29646/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-28069 and fix it if it is affected.

What it is: CVE-2022-28069 is a high-severity memory corruption vulnerability in Radare Radare2, published on 22 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-28069 in the wild and no public exploit code.

Affected product: Radare Radare2. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-28069/ (Markdown: https://insights.sbomify.com/CVE-2022-28069/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-28069
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-28069
- OSV: https://osv.dev/vulnerability/CVE-2022-28069

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-28069/
Summaries are generated and may contain mistakes; the official description above is the record.