Local privilege escalation via premature ApkAssets destruction
Published Dec 4, 2023 · Updated Aug 28, 2024
Double-free memory corruption in the Android 14 Framework allows local users to escalate privileges without user interaction. AssetManager2 retains raw or weak ApkAssets pointers after explicit close() calls destroy objects that remain in use, and racing native calls can dereference freed memory. Local app execution is required; successful exploitation can run code with elevated privileges and compromise device data or services.
Summary
What happened
Double-free memory corruption in the Android 14 Framework allows local users to escalate privileges without user interaction. AssetManager2 retains raw or weak ApkAssets pointers after explicit close() calls destroy objects that remain in use, and racing native calls can dereference freed memory. Local app execution is required; successful exploitation can run code with elevated privileges and compromise device data or services.
The record
- CVE
- CVE-2023-40103
- Published
- Dec 4, 2023
- Updated
- Aug 28, 2024
- Vendor
- Product
- Android
- Classifications
- CWE-415, T1404
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 4, 2023CVE publishedPublication date reported by the CVE source.
- Aug 28, 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=14
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
No public exploit references are available in this record.
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