Memory corruption via unchecked datablock_write input length
Published Apr 10, 2020 · Updated Aug 6, 2024
Buffer overflow in datablock_write on Samsung mobile devices with KK 4.4 and later through 2015-05-13 allows remote attackers to corrupt memory. The function writes received data without validating that its amount fits the destination buffer. Network delivery requires no authentication or user interaction; the public record does not identify a protocol or demonstrate code execution.
Summary
What happened
Buffer overflow in datablock_write on Samsung mobile devices with KK 4.4 and later through 2015-05-13 allows remote attackers to corrupt memory. The function writes received data without validating that its amount fits the destination buffer. Network delivery requires no authentication or user interaction; the public record does not identify a protocol or demonstrate code execution.
The record
- CVE
- CVE-2015-5524
- Published
- Apr 10, 2020
- Updated
- Aug 6, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 10, 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