Preboot payload tampering via wildcard certificate acceptance
Published Jun 24, 2021 · Updated Sep 16, 2024
Improper certificate validation in Dell UEFI BIOS HTTPS Stack Gen 10 and Gen 11 allows remote attackers to tamper with preboot payloads. BIOSConnect accepts any valid wildcard certificate chained to a built-in CA instead of binding the certificate to Dell's download host. No product credentials are required, but exploitation requires network compromise, a trusted certificate, and physical initiation of BIOSConnect or HTTPS Boot, enabling payload tampering or an unspecified service interruption.
Summary
What happened
Improper certificate validation in Dell UEFI BIOS HTTPS Stack Gen 10 and Gen 11 allows remote attackers to tamper with preboot payloads. BIOSConnect accepts any valid wildcard certificate chained to a built-in CA instead of binding the certificate to Dell's download host. No product credentials are required, but exploitation requires network compromise, a trusted certificate, and physical initiation of BIOSConnect or HTTPS Boot, enabling payload tampering or an unspecified service interruption.
The record
- CVE
- CVE-2021-21571
- Published
- Jun 24, 2021
- Updated
- Sep 16, 2024
- Vendor
- Dell
- Product
- Dell UEFI BIOS HTTPS Stack
- Classifications
- CWE-295, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 24, 2021CVE publishedPublication date reported by the CVE source.
- Sep 16, 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=Gen 11, Gen 10
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.
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