Pre-boot code execution via trusted EFI shell
Published Aug 26, 2022 · Updated Aug 3, 2024
Secure Boot bypass in CryptoPro Secure Disk bootloaders before 2022-06-01 allows local users to execute arbitrary pre-boot code. The signed bootloader exposes an EFI shell that launches unsigned code without enforcing the Secure Boot trust policy. Exploitation requires privileged access to replace the signed bootloader on the EFI System Partition and boot from external media; code then runs before operating-system defenses.
Summary
What happened
Secure Boot bypass in CryptoPro Secure Disk bootloaders before 2022-06-01 allows local users to execute arbitrary pre-boot code. The signed bootloader exposes an EFI shell that launches unsigned code without enforcing the Secure Boot trust policy. Exploitation requires privileged access to replace the signed bootloader on the EFI System Partition and boot from external media; code then runs before operating-system defenses.
The record
- CVE
- CVE-2022-34301
- Published
- Aug 26, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1542.003
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Aug 26, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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