Local code execution via unrestricted Java deserialization
Published Nov 20, 2024 · Updated Jan 6, 2025
Deserialization of untrusted data in Google Car App Library 1.4.0 through 1.7.0-beta02 allows local users to execute arbitrary code. CarAppService reconstructs attacker-supplied serialized objects as arbitrary Java classes instead of restricting them to types marked with the CarProtocol annotation. A malicious application must be installed alongside a victim application that exposes CarAppService, and code execution requires a suitable Java deserialization gadget.
Summary
What happened
Deserialization of untrusted data in Google Car App Library 1.4.0 through 1.7.0-beta02 allows local users to execute arbitrary code. CarAppService reconstructs attacker-supplied serialized objects as arbitrary Java classes instead of restricting them to types marked with the CarProtocol annotation. A malicious application must be installed alongside a victim application that exposes CarAppService, and code execution requires a suitable Java deserialization gadget.
The record
- CVE
- CVE-2024-10382
- Published
- Nov 20, 2024
- Updated
- Jan 6, 2025
- Vendor
- Product
- Android
- Classifications
- CWE-502, T1658
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Nov 20, 2024CVE publishedPublication date reported by the CVE source.
- Jan 6, 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=1.4.0 <1.7.0-beta02
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
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