Content disclosure via incomplete HDCP key exchange
Published Jun 13, 2024 · Updated Aug 19, 2024
Permission bypass in Google Android's Trusty component allows physically proximate attackers to disable HDCP 2.2 encryption. The HDCP initialization path leaves content protection disabled when the connected peer does not complete the key exchange; Google has not published the affected function. Physical access to a display connection is required, and the bounded consequence is exposure of otherwise protected audiovisual content rather than service interruption.
Summary
What happened
Permission bypass in Google Android's Trusty component allows physically proximate attackers to disable HDCP 2.2 encryption. The HDCP initialization path leaves content protection disabled when the connected peer does not complete the key exchange; Google has not published the affected function. Physical access to a display connection is required, and the bounded consequence is exposure of otherwise protected audiovisual content rather than service interruption.
The record
- CVE
- CVE-2024-32918
- Published
- Jun 13, 2024
- Updated
- Aug 19, 2024
- Vendor
- Product
- Android
- Classifications
- CWE-269
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 13, 2024CVE publishedPublication date reported by the CVE source.
- Aug 19, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <*
- Affected versionversion=Android kernel
What conditions does exploitation require?
What is affected?
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