Memory corruption via unchecked input-booster index
Published Apr 8, 2020 · Updated Aug 5, 2024
Array overflow in Samsung mobile device input-booster drivers on Android 7.x and 8.x allows attackers to corrupt memory. The driver uses an index variable without checking its size before an array access, allowing an out-of-range index to overflow the array. Samsung has not published the input path, required privileges, or consequences beyond the array overflow.
Summary
What happened
Array overflow in Samsung mobile device input-booster drivers on Android 7.x and 8.x allows attackers to corrupt memory. The driver uses an index variable without checking its size before an array access, allowing an out-of-range index to overflow the array. Samsung has not published the input path, required privileges, or consequences beyond the array overflow.
The record
- CVE
- CVE-2018-21064
- Published
- Apr 8, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 8, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 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