Secure-memory corruption via HDCP Trustlet overflow
Published Mar 24, 2020 · Updated Aug 5, 2024
Buffer overflow in the HDCP Trustlet on Samsung mobile devices running Android 8.x or 9.0 allows remote attackers to corrupt TEEGRIS memory. Public records identify the HDCP Trustlet as the locus but do not disclose the input path, affected routine, or unchecked operation that overruns the secure-memory buffer. Exposure is limited to Exynos-based devices, and the published evidence confirms secure-memory corruption but does not establish code execution or a specific service interruption.
Summary
What happened
Buffer overflow in the HDCP Trustlet on Samsung mobile devices running Android 8.x or 9.0 allows remote attackers to corrupt TEEGRIS memory. Public records identify the HDCP Trustlet as the locus but do not disclose the input path, affected routine, or unchecked operation that overruns the secure-memory buffer. Exposure is limited to Exynos-based devices, and the published evidence confirms secure-memory corruption but does not establish code execution or a specific service interruption.
The record
- CVE
- CVE-2019-20545
- Published
- Mar 24, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 24, 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