Out-of-bounds read and write via missing bounds check
Published Nov 7, 2023 · Updated Sep 17, 2024
Improper input validation in libsaped on Samsung Mobile Devices before SMR Nov-2023 Release 1 allows local attackers to read and write out of bounds. The get_head_crc function processes input without the boundary check needed to keep memory accesses within the intended buffer. The flaw affects Android 11, 12, and 13; Samsung has not disclosed the input path or any consequence beyond the stated out-of-bounds access.
Summary
What happened
Improper input validation in libsaped on Samsung Mobile Devices before SMR Nov-2023 Release 1 allows local attackers to read and write out of bounds. The get_head_crc function processes input without the boundary check needed to keep memory accesses within the intended buffer. The flaw affects Android 11, 12, and 13; Samsung has not disclosed the input path or any consequence beyond the stated out-of-bounds access.
The record
- CVE
- CVE-2023-42537
- Published
- Nov 7, 2023
- Updated
- Sep 17, 2024
- Vendor
- Samsung Electronics Co., Ltd.
- Product
- Samsung Mobile Devices
- Classifications
- CWE-787, CWE-125
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 7, 2023CVE publishedPublication date reported by the CVE source.
- Sep 17, 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.
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