Device shell command execution via package-name injection
Published Apr 22, 2024 · Updated Aug 2, 2024
Command injection in Skylot JADX before 1.5.0 allows local users to run shell commands on a connected Android device through a crafted APK. JADX-GUI's ADBDevice launch path concatenates the APK-controlled package name directly into an am start shell command without filtering shell metacharacters. Exploitation requires a user to open the APK and click Launch App; injected commands then execute with the device's shell privileges, enabling actions such as shutdown.
Summary
What happened
Command injection in Skylot JADX before 1.5.0 allows local users to run shell commands on a connected Android device through a crafted APK. JADX-GUI's ADBDevice launch path concatenates the APK-controlled package name directly into an am start shell command without filtering shell metacharacters. Exploitation requires a user to open the APK and click Launch App; injected commands then execute with the device's shell privileges, enabling actions such as shutdown.
The record
- CVE
- CVE-2024-32653
- Published
- Apr 22, 2024
- Updated
- Aug 2, 2024
- Vendor
- Skylot
- Product
- JADX
- Classifications
- CWE-20, T1204.002
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Apr 22, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.5.0
- Affected versionversion=< 1.5.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Crafted package-name shutdown proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo