Memory corruption via oversized OTP service copy
Published Apr 7, 2020 · Updated Aug 6, 2024
Heap-based buffer overflow in Samsung mobile devices through 2016-09-13 allows remote attackers to corrupt OTP service memory. The OTP service passes an excessive copy length to memcpy, causing data to be written beyond the destination heap buffer. Exploitation requires an affected device with an Exynos AP chipset; public records identify neither the reachable OTP request nor a demonstrated consequence beyond memory corruption.
Summary
What happened
Heap-based buffer overflow in Samsung mobile devices through 2016-09-13 allows remote attackers to corrupt OTP service memory. The OTP service passes an excessive copy length to memcpy, causing data to be written beyond the destination heap buffer. Exploitation requires an affected device with an Exynos AP chipset; public records identify neither the reachable OTP request nor a demonstrated consequence beyond memory corruption.
The record
- CVE
- CVE-2016-11025
- Published
- Apr 7, 2020
- Updated
- Aug 6, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 7, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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