Local information disclosure via unchecked adapter bounds
Published Oct 25, 2024 · Updated Oct 25, 2024
An out-of-bounds read in Google Android's Exynos RIL component allows local users to disclose information from device memory. ProtocolEmbmsSaiListAdapter::Init() in protocolembmsadapter.cpp reads beyond an input boundary because it omits a required bounds check. Exploitation requires prior compromise of baseband firmware and no user interaction, limiting the consequence to local information disclosure.
Summary
What happened
An out-of-bounds read in Google Android's Exynos RIL component allows local users to disclose information from device memory. ProtocolEmbmsSaiListAdapter::Init() in protocolembmsadapter.cpp reads beyond an input boundary because it omits a required bounds check. Exploitation requires prior compromise of baseband firmware and no user interaction, limiting the consequence to local information disclosure.
The record
- CVE
- CVE-2024-47019
- Published
- Oct 25, 2024
- Updated
- Oct 25, 2024
- Vendor
- Product
- Android
- Classifications
- CWE-125, T1533
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 25, 2024CVE publishedPublication date reported by the CVE source.
- Oct 25, 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?
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