CVE-2024-32653
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 · uneditedjadx is a Dex to Java decompiler. Prior to version 1.5.0, the package name is not filtered before concatenation. This can be exploited to inject arbitrary code into the package name. The vulnerability allows an attacker to execute commands with shell privileges. Version 1.5.0 contains a patch for the vulnerability.
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 confidenceThe jadx Dex-to-Java decompiler fails to sanitize package names extracted from input APK/Dex files before using them in shell command execution contexts. An attacker can craft a malicious APK with a specially crafted package name containing shell metacharacters to achieve arbitrary command execution with the privileges of the user running jadx.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Locate jadx installationRun 'which jadx' or 'where jadx' to find the executable path. On Linux/macOS also check common locations like /usr/bin/jadx, /usr/local/bin/jadx, or ~/.local/bin/jadx.Affected if jadx is not found on the system, then not affected.
-
Determine jadx versionRun 'jadx --version' or 'jadx -v' to display the installed version number.Affected if Version is unknown or cannot be determined.
-
Compare version to fixed releaseCompare the installed version against 1.5.0. Versions prior to 1.5.0 (such as 1.4.x, 1.3.x, etc.) are affected.Affected if Installed version is lower than 1.5.0.
-
Assess processing of untrusted APK/Dex filesDetermine whether jadx is used to process APK or Dex files from untrusted or external sources. This is the attack surface for command injection.Affected if jadx version is below 1.5.0 AND the tool processes APK/Dex files from untrusted sources.
User is affected if jadx version is below 1.5.0 and they process APK/Dex files from untrusted sources, as malicious package names could trigger arbitrary command execution.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade to jadx version 1.5.0 or later which contains proper input sanitization for package names before shell command concatenation.
1.5.0
- Check current jadx version using `jadx --version` or equivalent command
- Download jadx version 1.5.0 or later from the official GitHub releases page (github.com/skylot/jadx)
- Replace the existing jadx installation with version 1.5.0
- Verify the upgrade was successful by running `jadx --version` to confirm the new version is installed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-32653 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-32653 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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