Secure boot bypass via bootm memory corruption
Published Jul 1, 2024 · Updated Aug 1, 2024
Memory corruption in Qualcomm Snapdragon wired-networking firmware allows physically proximate attackers to bypass secure-boot image authentication. During bootm processing, the boot loader corrupts memory while authenticating the kernel or root filesystem image, causing the authentication decision to be bypassed. Physical access and invocation of bootm are required, and successful exploitation permits an unauthenticated kernel or root filesystem image to boot.
Summary
What happened
Memory corruption in Qualcomm Snapdragon wired-networking firmware allows physically proximate attackers to bypass secure-boot image authentication. During bootm processing, the boot loader corrupts memory while authenticating the kernel or root filesystem image, causing the authentication decision to be bypassed. Physical access and invocation of bootm are required, and successful exploitation permits an unauthenticated kernel or root filesystem image to boot.
The record
- CVE
- CVE-2024-21482
- Published
- Jul 1, 2024
- Updated
- Aug 1, 2024
- Vendor
- Qualcomm
- Product
- QCN9074 Firmware
- Classifications
- CWE-119, T1542.003
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 1, 2024CVE publishedPublication date reported by the CVE source.
- Aug 1, 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 <=*
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