Physical privilege escalation via embedded UEFI shell
Published Sep 13, 2024 · Updated Sep 16, 2024
Active debug code in affected Lenovo L390, L390 Yoga, and 10w BIOS allows physically proximate attackers to escalate privileges. Affected firmware leaves an embedded UEFI shell accessible in production, exposing active debug functionality that should not be reachable. Physical access to a vulnerable device is required, and the exposed shell provides local privilege escalation; Lenovo has not disclosed the shell entry path or available commands.
Summary
What happened
Active debug code in affected Lenovo L390, L390 Yoga, and 10w BIOS allows physically proximate attackers to escalate privileges. Affected firmware leaves an embedded UEFI shell accessible in production, exposing active debug functionality that should not be reachable. Physical access to a vulnerable device is required, and the exposed shell provides local privilege escalation; Lenovo has not disclosed the shell entry path or available commands.
The record
- CVE
- CVE-2024-7756
- Published
- Sep 13, 2024
- Updated
- Sep 16, 2024
- Vendor
- Lenovo
- Product
- Lenovo ThinkPad L390 Yoga Firmware
- Classifications
- CWE-489
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 13, 2024CVE 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=0 <1.47
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
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