Arbitrary file write via unsanitized resource names
Published Jan 3, 2024 · Updated Jun 3, 2025
Path traversal in iBotPeaches Apktool 2.9.1 and earlier allows attackers to write arbitrary files by supplying a crafted APK. During decoding, ResFileDecoder builds output paths from unsanitized resource names, so traversal sequences escape the intended resource directory. A user must decode the malicious APK; writes are limited to that user's permissions, and targeting certain home files requires a known username or a working directory under the home folder.
Summary
What happened
Path traversal in iBotPeaches Apktool 2.9.1 and earlier allows attackers to write arbitrary files by supplying a crafted APK. During decoding, ResFileDecoder builds output paths from unsanitized resource names, so traversal sequences escape the intended resource directory. A user must decode the malicious APK; writes are limited to that user's permissions, and targeting certain home files requires a known username or a working directory under the home folder.
The record
- CVE
- CVE-2024-21633
- Published
- Jan 3, 2024
- Updated
- Jun 3, 2025
- Vendor
- iBotPeaches
- Product
- Apktool
- Classifications
- CWE-22, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 3, 2024CVE publishedPublication date reported by the CVE source.
- Jun 3, 2025Record 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=<= 2.9.1
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.
Weakness, pattern, technique
Public exploit references
- Apktool arbitrary-write 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