Local privilege escalation via memcall_add buffer overflow
Published Jun 13, 2024 · Updated Aug 2, 2024
Buffer overflow in memcall_add in Google Android before the 2024-06-05 patch level allows local users to elevate privileges. The function accepts insufficiently validated memory-call data and writes beyond its destination buffer in the Pixel Trusty/TEE component. Execution on an affected Pixel device is required; exploitation needs no user interaction or additional execution privileges and grants elevated local privilege.
Summary
What happened
Buffer overflow in memcall_add in Google Android before the 2024-06-05 patch level allows local users to elevate privileges. The function accepts insufficiently validated memory-call data and writes beyond its destination buffer in the Pixel Trusty/TEE component. Execution on an affected Pixel device is required; exploitation needs no user interaction or additional execution privileges and grants elevated local privilege.
The record
- CVE
- CVE-2024-32907
- Published
- Jun 13, 2024
- Updated
- Aug 2, 2024
- Vendor
- Product
- Android
- Classifications
- CWE-20, CWE-120, T1404
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jun 13, 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 <2024-06-05
- Affected versionversion=Android kernel
What conditions does exploitation require?
What is affected?
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