# CVE-2022-0849: Use After Free in r_reg_get_name_idx in radareorg/radare2

> A use-after-free vulnerability in radare2 allows attackers to execute arbitrary code or cause a denial of service via crafted input.

- **Severity:** High 7.3 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 5 Mar 2022
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-9r7p-3jj4-29v6, UBUNTU-CVE-2022-0849

## What is CVE-2022-0849?

CVE-2022-0849 is a high-severity use after free vulnerability in Radare Radare2, published on 5 Mar 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Use After Free in r_reg_get_name_idx in GitHub repository radareorg/radare2 prior to 5.6.6.

Weakness: CWE-416 (Use After Free)

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

It affects 1 product.


Products: Radare Radare2.

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

Upgrade to a fixed version.

## Is CVE-2022-0849 being exploited?

There is no known exploitation of CVE-2022-0849 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-0849 and fix it if it is affected.

What it is: CVE-2022-0849 is a high-severity use after free vulnerability in Radare Radare2, published on 5 Mar 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-0849 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-0849/ (Markdown: https://insights.sbomify.com/CVE-2022-0849/index.md)
```

## Sources

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

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