Local service crash via missing bounds check
Published Apr 8, 2024 · Updated Nov 5, 2024
Out-of-bounds write in affected UNISOC chipsets' ril service on Android 12 through 14 allows local users with System privileges to crash it. The ril service writes beyond a buffer because it omits a required bounds check; UNISOC has not disclosed the affected function or input field. Reachability requires local System execution privileges, and the documented consequence is limited to denial of service.
Summary
What happened
Out-of-bounds write in affected UNISOC chipsets' ril service on Android 12 through 14 allows local users with System privileges to crash it. The ril service writes beyond a buffer because it omits a required bounds check; UNISOC has not disclosed the affected function or input field. Reachability requires local System execution privileges, and the documented consequence is limited to denial of service.
The record
- CVE
- CVE-2023-52351
- Published
- Apr 8, 2024
- Updated
- Nov 5, 2024
- Vendor
- UNISOC
- Product
- UNISOC T610
- Classifications
- CWE-787, T1499.004
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Apr 8, 2024CVE publishedPublication date reported by the CVE source.
- Nov 5, 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=android12_android13_android14
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