Secure Boot bypass via enabled UEFI Shell
Published Feb 14, 2024 · Updated May 8, 2025
Security feature bypass in Canonical Ubuntu EDK II before 2023.05-2ubuntu0.1 allows local users to bypass UEFI Secure Boot. Ubuntu's OVMF and AAVMF firmware exposes its built-in UEFI Shell while Secure Boot is active; shell scripting and the mm command permit writes to physical memory. High-privilege OS-resident local users can change the boot order, trigger an unattended shell script after reboot, place an unsigned payload in memory, and redirect execution to it.
Summary
What happened
Security feature bypass in Canonical Ubuntu EDK II before 2023.05-2ubuntu0.1 allows local users to bypass UEFI Secure Boot. Ubuntu's OVMF and AAVMF firmware exposes its built-in UEFI Shell while Secure Boot is active; shell scripting and the mm command permit writes to physical memory. High-privilege OS-resident local users can change the boot order, trigger an unattended shell script after reboot, place an unsigned payload in memory, and redirect execution to it.
The record
- CVE
- CVE-2023-48733
- Published
- Feb 14, 2024
- Updated
- May 8, 2025
- Vendor
- Canonical
- Product
- Ubuntu EDK II
- Classifications
- CWE-1188, T1542.003
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Feb 14, 2024CVE publishedPublication date reported by the CVE source.
- May 8, 2025Record 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 <2023.05-2ubuntu0.1
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