Firmware code execution via LemSecureBootForceKey buffer overflow
Published Nov 8, 2023 · Updated Sep 12, 2024
Buffer overflow in Lenovo Desktop BIOS allows local users with elevated privileges to execute arbitrary code in system firmware. The LemSecureBootForceKey module contains the overflow, but Lenovo has not disclosed the affected copy operation or attacker-controlled input. Administrative local access is required; successful exploitation executes code in the firmware context and can compromise the system.
Summary
What happened
Buffer overflow in Lenovo Desktop BIOS allows local users with elevated privileges to execute arbitrary code in system firmware. The LemSecureBootForceKey module contains the overflow, but Lenovo has not disclosed the affected copy operation or attacker-controlled input. Administrative local access is required; successful exploitation executes code in the firmware context and can compromise the system.
The record
- CVE
- CVE-2023-43567
- Published
- Nov 8, 2023
- Updated
- Sep 12, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120, T1068
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Nov 8, 2023CVE publishedPublication date reported by the CVE source.
- Sep 12, 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.
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