Local service interruption via unchecked RIL write
Published Apr 8, 2024 · Updated Nov 1, 2024
Out-of-bounds write in the RIL service on affected UNISOC chipsets running Android 12 through Android 14 allows local users to interrupt service. The RIL service writes past a buffer boundary because it omits a required bounds check; UNISOC has not disclosed the function or input path. Reachability requires local access with System execution privileges; the documented consequence is service interruption, with no reported data disclosure or modification.
Summary
What happened
Out-of-bounds write in the RIL service on affected UNISOC chipsets running Android 12 through Android 14 allows local users to interrupt service. The RIL service writes past a buffer boundary because it omits a required bounds check; UNISOC has not disclosed the function or input path. Reachability requires local access with System execution privileges; the documented consequence is service interruption, with no reported data disclosure or modification.
The record
- CVE
- CVE-2023-52347
- Published
- Apr 8, 2024
- Updated
- Nov 1, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1642
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 8, 2024CVE publishedPublication date reported by the CVE source.
- Nov 1, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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