Secure Boot bypass via production-signed test kernels
Published Jun 21, 2022 · Updated Aug 3, 2024
Secure Boot bypass in Red Hat Enterprise Linux 8.6 allows local users with high privileges to boot untrusted code on IBM Power systems. Pre-production kernel packages were signed with Red Hat production Secure Boot keys even though they lack the lockdown patches required for trusted builds. Exploitation requires Secure Boot on PowerPC, installation of a non-production kernel, and selection of that kernel as the default GRUB2 boot entry.
Summary
What happened
Secure Boot bypass in Red Hat Enterprise Linux 8.6 allows local users with high privileges to boot untrusted code on IBM Power systems. Pre-production kernel packages were signed with Red Hat production Secure Boot keys even though they lack the lockdown patches required for trusted builds. Exploitation requires Secure Boot on PowerPC, installation of a non-production kernel, and selection of that kernel as the default GRUB2 boot entry.
The record
- CVE
- CVE-2022-1665
- Published
- Jun 21, 2022
- Updated
- Aug 3, 2024
- Vendor
- Red Hat
- Product
- Red Hat Enterprise Linux
- Classifications
- CWE-1291, T1542.003
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jun 21, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=8.6
What conditions does exploitation require?
What is affected?
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