Secure Boot bypass via enabled UEFI Shell
Published Feb 14, 2024 · Updated Oct 24, 2024
Secure Boot bypass in Canonical LXD allows guest OS users with root access to execute unsigned code through the VM firmware. LXD's OVMF build exposes the UEFI Shell as a built-in boot option under Secure Boot, and its mm command writes arbitrary physical memory. A guest root user can change the boot order, place an unattended startup.nsh on the EFI system partition, and gain system-level control after reboot.
Summary
What happened
Secure Boot bypass in Canonical LXD allows guest OS users with root access to execute unsigned code through the VM firmware. LXD's OVMF build exposes the UEFI Shell as a built-in boot option under Secure Boot, and its mm command writes arbitrary physical memory. A guest root user can change the boot order, place an unattended startup.nsh on the EFI system partition, and gain system-level control after reboot.
The record
- CVE
- CVE-2023-49721
- Published
- Feb 14, 2024
- Updated
- Oct 24, 2024
- Vendor
- Canonical
- Product
- LXD
- Classifications
- CWE-276, T1542.003
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Feb 14, 2024CVE publishedPublication date reported by the CVE source.
- Oct 24, 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
- Affected versionversion=0 <*
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.
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