Secure Boot bypass via stack-based buffer overflow
Published Apr 9, 2024 · Updated May 3, 2025
Stack-based buffer overflow in Microsoft Windows Secure Boot allows attackers to bypass Secure Boot via an adjacent vector. Microsoft identifies Secure Boot as the affected component but has not disclosed the buffer's code locus, untrusted input, or incorrect copy operation. Exploitation requires high privileges, user interaction, adjacency, and a high-complexity condition; Microsoft has not published the narrower post-bypass consequence.
Summary
What happened
Stack-based buffer overflow in Microsoft Windows Secure Boot allows attackers to bypass Secure Boot via an adjacent vector. Microsoft identifies Secure Boot as the affected component but has not disclosed the buffer's code locus, untrusted input, or incorrect copy operation. Exploitation requires high privileges, user interaction, adjacency, and a high-complexity condition; Microsoft has not published the narrower post-bypass consequence.
The record
- CVE
- CVE-2024-28898
- Published
- Apr 9, 2024
- Updated
- May 3, 2025
- Vendor
- Microsoft
- Product
- Windows 10 Version 1507
- Classifications
- CWE-121
- Attack vector
- adjacent
- Privileges
- admin
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.
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