# CVE-2019-16718: In radare2 before 3.9.0, a command injection vulnerability exists in bin_symbols() in libr/core/cbin.c.


- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 23 Sep 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-644g-qxf2-f99x

## What is CVE-2019-16718?

CVE-2019-16718 is a high-severity vulnerability in Radare Radare2, published on 23 Sep 2019. 

### Official description

In radare2 before 3.9.0, a command injection vulnerability exists in bin_symbols() in libr/core/cbin.c. By using a crafted executable file, it's possible to execute arbitrary shell commands with the permissions of the victim. This vulnerability is due to an insufficient fix for CVE-2019-14745 and improper handling of symbol names embedded in executables.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2019-16718?

It affects 1 product.


Products: Radare Radare2.

## How do I fix CVE-2019-16718?

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

## Is CVE-2019-16718 being exploited?

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

What it is: CVE-2019-16718 is a high-severity vulnerability in Radare Radare2, published on 23 Sep 2019. 
Exploitation: There is no known exploitation of CVE-2019-16718 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-2019-16718/ (Markdown: https://insights.sbomify.com/CVE-2019-16718/index.md)
```

## Sources

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

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