Secure Boot bypass via default cryptographic key
Published Aug 28, 2024 · Updated Aug 28, 2024
Use of a default cryptographic key in Dell Client Platform BIOS allows local administrators to bypass Secure Boot and execute code. Dell identifies only a default cryptographic key in proprietary BIOS code and has not disclosed the key's role or the operation that trusts it. Exploitation requires high privileges and local access; successful exploitation bypasses Secure Boot and enables arbitrary code execution.
Summary
What happened
Use of a default cryptographic key in Dell Client Platform BIOS allows local administrators to bypass Secure Boot and execute code. Dell identifies only a default cryptographic key in proprietary BIOS code and has not disclosed the key's role or the operation that trusts it. Exploitation requires high privileges and local access; successful exploitation bypasses Secure Boot and enables arbitrary code execution.
The record
- CVE
- CVE-2024-39584
- Published
- Aug 28, 2024
- Updated
- Aug 28, 2024
- Vendor
- Dell
- Product
- Dell Client Platform BIOS
- Classifications
- CWE-1392, T1542.003
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Aug 28, 2024CVE publishedPublication date reported by the CVE source.
- Aug 28, 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=N/A <1.15.0
- Affected versionversion=N/A <1.21.0
- Affected versionversion=N/A <1.24.0
- Affected versionversion=N/A <1.29.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
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