Memory corruption via unchecked Trustlet buffer sizes
Published Apr 8, 2020 · Updated Aug 5, 2024
A buffer overflow in a Trustlet on Samsung mobile devices running Android 6.0 allows attackers to corrupt memory via unspecified vectors. The Trustlet fails to verify source and destination sizes before copying data into a buffer, allowing the copy to exceed its boundary. Public records do not identify the entry point or required privileges, and Samsung's bulletin instead lists Android 7.x, leaving exposure boundaries inconsistent.
Summary
What happened
A buffer overflow in a Trustlet on Samsung mobile devices running Android 6.0 allows attackers to corrupt memory via unspecified vectors. The Trustlet fails to verify source and destination sizes before copying data into a buffer, allowing the copy to exceed its boundary. Public records do not identify the entry point or required privileges, and Samsung's bulletin instead lists Android 7.x, leaving exposure boundaries inconsistent.
The record
- CVE
- CVE-2018-21066
- 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