Code execution via heap buffer overflow
Published Sep 9, 2021 · Updated Aug 3, 2024
Heap-based buffer overflow in Samsung Mobile Devices before SMR Sep-2021 Release 1 allows attackers to execute code in mediaextractor. The libsapeextractor library accepts input without sufficient bounds validation and writes beyond a heap allocation. Unauthenticated network access is the published gate, and successful exploitation executes code within mediaextractor; Samsung has not disclosed the exact trigger format.
Summary
What happened
Heap-based buffer overflow in Samsung Mobile Devices before SMR Sep-2021 Release 1 allows attackers to execute code in mediaextractor. The libsapeextractor library accepts input without sufficient bounds validation and writes beyond a heap allocation. Unauthenticated network access is the published gate, and successful exploitation executes code within mediaextractor; Samsung has not disclosed the exact trigger format.
The record
- CVE
- CVE-2021-25449
- Published
- Sep 9, 2021
- Updated
- Aug 3, 2024
- Vendor
- Samsung Electronics Co., Ltd.
- Product
- Samsung Mobile Devices
- Classifications
- CWE-119, CWE-122, T1658
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 9, 2021CVE 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=O(8.1), P(9.0), Q(10.0), R(11.0) <SMR Sep-2021 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.
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