Local stack-memory disclosure via uninitialized plugin data
Published Jun 13, 2024 · Updated Nov 7, 2024
Information disclosure in Google Android's ACPM component allows local users to read four bytes of stack memory without user interaction. The plugin_ipc_handler function in slc_plugin.c uses uninitialized data, exposing residual stack contents during plugin IPC handling. Exploitation requires local low-privileged access and affects confidentiality only, with no reported write or service-interruption impact.
Summary
What happened
Information disclosure in Google Android's ACPM component allows local users to read four bytes of stack memory without user interaction. The plugin_ipc_handler function in slc_plugin.c uses uninitialized data, exposing residual stack contents during plugin IPC handling. Exploitation requires local low-privileged access and affects confidentiality only, with no reported write or service-interruption impact.
The record
- CVE
- CVE-2024-32930
- Published
- Jun 13, 2024
- Updated
- Nov 7, 2024
- Vendor
- Product
- Android
- Classifications
- CWE-665
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 13, 2024CVE publishedPublication date reported by the CVE source.
- Nov 7, 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=Android kernel
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