Local code execution via missing boundary check
Published Nov 9, 2022 · Updated May 1, 2025
Heap overflow in libsmat.so in Samsung Mobile Devices on Android 10 through 12 allows local users to execute arbitrary code. The sflacf_fal_bytes_peek function performs a byte peek without enforcing the heap-buffer boundary required for memory safety. Exploitation requires local access to an affected device and can compromise data or interrupt the device without reported user interaction.
Summary
What happened
Heap overflow in libsmat.so in Samsung Mobile Devices on Android 10 through 12 allows local users to execute arbitrary code. The sflacf_fal_bytes_peek function performs a byte peek without enforcing the heap-buffer boundary required for memory safety. Exploitation requires local access to an affected device and can compromise data or interrupt the device without reported user interaction.
The record
- CVE
- CVE-2022-39882
- Published
- Nov 9, 2022
- Updated
- May 1, 2025
- Vendor
- Samsung Electronics Co., Ltd.
- Product
- Samsung Mobile Devices
- Classifications
- CWE-787, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 9, 2022CVE publishedPublication date reported by the CVE source.
- May 1, 2025Record 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=Q(10), R(11), S(12) <SMR Nov-2022 Release 1
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