Local code execution via unchecked response bounds
Published Jul 6, 2023 · Updated Nov 20, 2024
Out-of-bounds write in libsec-ril on Samsung Mobile Devices before SMR Jul-2023 Release 1 allows local users to execute arbitrary code. BuildOemSecureSimLockResponse writes beyond a memory buffer because it lacks a proper boundary check when building a secure SIM-lock response. Exploitation requires high-privilege local access and can compromise confidentiality, integrity, and availability through attacker-controlled code.
Summary
What happened
Out-of-bounds write in libsec-ril on Samsung Mobile Devices before SMR Jul-2023 Release 1 allows local users to execute arbitrary code. BuildOemSecureSimLockResponse writes beyond a memory buffer because it lacks a proper boundary check when building a secure SIM-lock response. Exploitation requires high-privilege local access and can compromise confidentiality, integrity, and availability through attacker-controlled code.
The record
- CVE
- CVE-2023-30668
- Published
- Jul 6, 2023
- Updated
- Nov 20, 2024
- Vendor
- Samsung Electronics Co., Ltd.
- Product
- Samsung Mobile Devices
- Classifications
- CWE-787
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jul 6, 2023CVE publishedPublication date reported by the CVE source.
- Nov 20, 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?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
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