Local memory disclosure via unchecked buffer boundary
Published Dec 8, 2023 · Updated Aug 2, 2024
Out-of-bounds read in Exynos RIL on Google Android with the Android kernel allows local users to disclose memory. ProtocolNetSimFileInfoAdapter() in protocolnetadapter.cpp reads beyond an intended buffer because it fails to validate a boundary before accessing protocol data. Exploitation requires prior compromise of the device's baseband firmware; no user interaction is required, and the documented consequence is limited to local information disclosure.
Summary
What happened
Out-of-bounds read in Exynos RIL on Google Android with the Android kernel allows local users to disclose memory. ProtocolNetSimFileInfoAdapter() in protocolnetadapter.cpp reads beyond an intended buffer because it fails to validate a boundary before accessing protocol data. Exploitation requires prior compromise of the device's baseband firmware; no user interaction is required, and the documented consequence is limited to local information disclosure.
The record
- CVE
- CVE-2023-48408
- Published
- Dec 8, 2023
- Updated
- Aug 2, 2024
- Vendor
- Product
- Android
- Classifications
- CWE-125
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Dec 8, 2023CVE 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=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