Firmware modification via trusted NVRAM control variable
Published Apr 22, 2022 · Updated Aug 3, 2024
Security feature bypass in Lenovo Notebook BIOS allows local users with elevated privileges to disable SPI flash write protections. The SecureBackDoorPeim and SecureBackDoor drivers treat the cE! NVRAM variable as an instruction to skip programming BIOS Control and Protected Range registers during boot. Administrator access with firmware-environment privileges and a restart are required; SPI flash then becomes writable outside SMM, enabling persistent firmware modification.
Summary
What happened
Security feature bypass in Lenovo Notebook BIOS allows local users with elevated privileges to disable SPI flash write protections. The SecureBackDoorPeim and SecureBackDoor drivers treat the cE! NVRAM variable as an instruction to skip programming BIOS Control and Protected Range registers during boot. Administrator access with firmware-environment privileges and a restart are required; SPI flash then becomes writable outside SMM, enabling persistent firmware modification.
The record
- CVE
- CVE-2021-3971
- Published
- Apr 22, 2022
- Updated
- Aug 3, 2024
- Vendor
- Lenovo
- Product
- Notebook BIOS
- Classifications
- CWE-489, T1542.001, T1562
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Apr 22, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=various
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.
Weakness, pattern, technique
Public exploit references
- SecureBackDoor cE! NVRAM-variable procedureproof of concept · demonstrated
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