dbcve.org
Radare2Application · Radare

CVE-2024-11858

HIGH · 7.8 CVSS v3.1 Published 2024-12-15
Fix available
A fix is available. Upgrade to after 5.9.8 or later.
See remediation →
81/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A flaw was found in Radare2, which contains a command injection vulnerability caused by insufficient input validation when handling Pebble Application files. Maliciously crafted inputs can inject shell commands during command parsing, leading to unintended behavior during file processing​

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Radare2 contains a command injection vulnerability due to insufficient input validation when parsing Pebble Application files. Attackers can inject shell commands through maliciously crafted Pebble files that get processed during file analysis, potentially executing arbitrary commands on the system.

MitigationUpdate Radare2 to the patched version that implements proper input sanitization for Pebble file parsing. Until patched, avoid processing untrusted Pebble Application files with Radare2.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Radare2Application
Affected:<= 5.9.8

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if Radare2 is installed
    Run `which r2` or `r2 -v` to locate the radare2 binary
    Affected if Radare2 is not found on the system
  2. Determine the installed Radare2 version
    Run `r2 -v` and note the version number in the output
    Affected if The version is 5.9.8 or lower (any version <= 5.9.8)
  3. Identify if Pebble file parsing has been used
    Check for recent analysis of Pebble application files (.pbw) by reviewing command history, recent files opened, or searching for `r2` process history involving Pebble files
    Affected if Pebble application files have been processed with this version of Radare2
  4. Inspect the Pebble parsing code path
    If you have access to the radare2 source or binary, verify that the Pebble file parsing functionality is present and can be invoked via commands like `i` (info) on a Pebble file
    Affected if The Pebble parsing module is available and has been used to analyze untrusted files

You are affected if Radare2 version 5.9.8 or lower is installed AND Pebble Application files have been analyzed with it, as the command injection vulnerability exists in the Pebble file parsing code path.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 5.9.8
Interim mitigation

Update Radare2 to the patched version that implements proper input sanitization for Pebble file parsing. Until patched, avoid processing untrusted Pebble Application files with Radare2.

Recommended fix Moderate confidence

Radare2 version > 5.9.8 (check GitHub releases for the first version after 5.9.8 that includes the security fix)

  1. 1. Visit the official Radare2 GitHub releases page at https://github.com/radareorg/radare2/releases to identify the version that addresses this command injection vulnerability.
  2. 2. Download the latest stable release of Radare2 (version higher than 5.9.8).
  3. 3. Back up your current Radare2 installation and configuration files.
  4. 4. Install the upgraded version of Radare2 following the official installation instructions from https://github.com/radareorg/radare2/blob/master/README.md
  5. 5. Verify the installation by running 'r2 -v' to confirm the version number is greater than 5.9.8.
  6. 6. Test that Radare2 functions correctly with your typical workflows before resuming production use.
Caveat Minor: Some command-line flags or scripting behaviors may have changed in newer versions; review release notes if using advanced features

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Radare2 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-11858 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-11858 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data