Elevated NVRAM variable writes via out-of-bounds read
Published Nov 8, 2023 · Updated Sep 4, 2024
Out-of-bounds read in Lenovo BIOS NvmramSmm allows local users with elevated privileges to write to NVRAM variables. Lenovo identifies the locus as the NvmramSmm SMM driver but has not disclosed which bounds check or memory operation mishandles input. Exploitation requires local high privileges and can alter persistent firmware variables, with no remote or unauthenticated path reported.
Summary
What happened
Out-of-bounds read in Lenovo BIOS NvmramSmm allows local users with elevated privileges to write to NVRAM variables. Lenovo identifies the locus as the NvmramSmm SMM driver but has not disclosed which bounds check or memory operation mishandles input. Exploitation requires local high privileges and can alter persistent firmware variables, with no remote or unauthenticated path reported.
The record
- CVE
- CVE-2023-45079
- Published
- Nov 8, 2023
- Updated
- Sep 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-125, T1542.001
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Nov 8, 2023CVE publishedPublication date reported by the CVE source.
- Sep 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?
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.
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