Physical privilege escalation via USB debug DMA
Published Jun 15, 2020 · Updated Aug 4, 2024
Improper access control in Intel Trusted Execution Engine before 3.1.75 and 4.0.25 allows physically proximate attackers to escalate privileges. On BXT-P and GLK platforms, firmware leaves USB DbC usable after manufacturing closes debug access, permitting RS1 DMA into CSME SRAM during reset or power-state resume. The path requires a physical USB connection and a CSME reset or resume, and successful exploitation grants control over trusted-engine execution without interrupting availability.
Summary
What happened
Improper access control in Intel Trusted Execution Engine before 3.1.75 and 4.0.25 allows physically proximate attackers to escalate privileges. On BXT-P and GLK platforms, firmware leaves USB DbC usable after manufacturing closes debug access, permitting RS1 DMA into CSME SRAM during reset or power-state resume. The path requires a physical USB connection and a CSME reset or resume, and successful exploitation grants control over trusted-engine execution without interrupting availability.
The record
- CVE
- CVE-2020-0566
- Published
- Jun 15, 2020
- Updated
- Aug 4, 2024
- Vendor
- Intel
- Product
- Intel Trusted Execution Engine
- Classifications
- T1068
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 15, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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=See provided reference
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