Remote information disclosure via unchecked buffer read
Published Oct 18, 2023 · Updated Sep 13, 2024
Out-of-bounds read in Google Android's Exynos RIL component allows remote attackers to disclose information without user interaction. Init in protocolnetadapter.cpp omits a buffer-boundary check before reading untrusted protocol input, allowing the read to extend beyond its intended bounds. Reachability requires a supported Pixel device with the Exynos RIL; no execution privileges or user interaction are required, and the published consequence is information disclosure.
Summary
What happened
Out-of-bounds read in Google Android's Exynos RIL component allows remote attackers to disclose information without user interaction. Init in protocolnetadapter.cpp omits a buffer-boundary check before reading untrusted protocol input, allowing the read to extend beyond its intended bounds. Reachability requires a supported Pixel device with the Exynos RIL; no execution privileges or user interaction are required, and the published consequence is information disclosure.
The record
- CVE
- CVE-2023-35663
- Published
- Oct 18, 2023
- Updated
- Sep 13, 2024
- Vendor
- Product
- Android
- Classifications
- CWE-125
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 18, 2023CVE publishedPublication date reported by the CVE source.
- Sep 13, 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