OSV-2022-383 Heap-use-after-free in r_asm_free
Not scored
Published
Check this codebase for OSV-2022-383 and fix it if it is affected.
What it is: OSV-2022-383 is an use after free vulnerability in radare2, published on 30 Apr 2022.
Exploitation: There is no known exploitation of OSV-2022-383 in the wild and no public exploit code.
Affected packages and fixed versions:
- radare2 (OSS-Fuzz): affected all versions; no fix listed
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/OSV-2022-383/ (Markdown: https://insights.sbomify.com/OSV-2022-383/index.md)
A heap-use-after-free vulnerability in the Radare2 library allows attackers to cause a crash or potentially execute arbitrary code via crafted input.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Not stated
- Victim action needed
- Not needed
- Fix
- None listed
What is OSV-2022-383?
OSV-2022-383 is an use after free vulnerability in radare2, published on 30 Apr 2022.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=47113
Crash type: Heap-use-after-free READ 4
Crash state:
r_asm_free
r_core_fini
r_core_free
Which versions are affected by OSV-2022-383?
1 open source package ship an affected version, including radare2.
| Package | Affected | Fixed in |
|---|---|---|
radare2 OSS-Fuzz | All versions | None |
How do I fix OSV-2022-383?
No fix has been published for OSV-2022-383 yet. Limit exposure of the affected software until one is available.
Upgrade to the fixed version. These bugs are found with fuzzing and sanitisers and avoided by memory-safe languages. More about Use after free.
Is OSV-2022-383 being exploited?
There is no known exploitation of OSV-2022-383 in the wild and no public exploit code.