Secure Boot bypass via heap buffer overflow
Published Apr 9, 2024 · Updated May 3, 2025
Heap-based buffer overflow in Microsoft Windows Secure Boot allows adjacent attackers to bypass boot integrity protections. Microsoft has not published the affected Secure Boot function, the input that reaches it, or the memory operation responsible for the overflow. Exploitation requires adjacent access and complex conditions, but no authentication or user interaction, and can defeat the trust boundary enforced during startup.
Summary
What happened
Heap-based buffer overflow in Microsoft Windows Secure Boot allows adjacent attackers to bypass boot integrity protections. Microsoft has not published the affected Secure Boot function, the input that reaches it, or the memory operation responsible for the overflow. Exploitation requires adjacent access and complex conditions, but no authentication or user interaction, and can defeat the trust boundary enforced during startup.
The record
- CVE
- CVE-2024-28896
- Published
- Apr 9, 2024
- Updated
- May 3, 2025
- Vendor
- Microsoft
- Product
- Windows 10 Version 1507
- Classifications
- CWE-122, T1542.003
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 9, 2024CVE publishedPublication date reported by the CVE source.
- May 3, 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=10.0.10240.0 <10.0.10240.20596
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