Persistent firmware modification via incomplete Boot Guard coverage
Published Jul 16, 2021 · Updated Dec 16, 2025
Protection mechanism failure in Lenovo BIOS allows physically proximate attackers to write to SPI flash storage on affected systems. Boot Guard's Initial Boot Block coverage omits some UEFI firmware modules, so their contents are not verified against the protected hash before execution. Physical access, or an existing BIOS write-protection bypass, is required to install a persistent firmware implant.
Summary
What happened
Protection mechanism failure in Lenovo BIOS allows physically proximate attackers to write to SPI flash storage on affected systems. Boot Guard's Initial Boot Block coverage omits some UEFI firmware modules, so their contents are not verified against the protected hash before execution. Physical access, or an existing BIOS write-protection bypass, is required to install a persistent firmware implant.
The record
- CVE
- CVE-2021-3453
- Published
- Jul 16, 2021
- Updated
- Dec 16, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-693, T1542.001
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 16, 2021CVE publishedPublication date reported by the CVE source.
- Dec 16, 2025Record 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.
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.
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