Local memory fault via LoadEnvironment heap overflow
Published Sep 9, 2022 · Updated Aug 3, 2024
Heap-based buffer overflow in Samsung Mobile Devices Q(10), R(11), and S(12) allows local attackers to cause a memory access fault. The LoadEnvironment function in libSDKRecognitionText.spensdk.samsung.so mishandles untrusted data without adequate heap bounds checking, allowing an overwrite. Exploitation requires local code execution on an affected device and results in a memory fault; Samsung reports no confidentiality impact or remote attack path.
Summary
What happened
Heap-based buffer overflow in Samsung Mobile Devices Q(10), R(11), and S(12) allows local attackers to cause a memory access fault. The LoadEnvironment function in libSDKRecognitionText.spensdk.samsung.so mishandles untrusted data without adequate heap bounds checking, allowing an overwrite. Exploitation requires local code execution on an affected device and results in a memory fault; Samsung reports no confidentiality impact or remote attack path.
The record
- CVE
- CVE-2022-36860
- Published
- Sep 9, 2022
- Updated
- Aug 3, 2024
- Vendor
- Samsung Electronics Co., Ltd.
- Product
- Samsung Mobile Devices
- Classifications
- CWE-122, T1203
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 9, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=Q(10), R(11), S(12) <SMR Sep-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