Secure Boot bypass via undisclosed heap overflow
Published Jul 9, 2024 · Updated Feb 10, 2026
Heap-based buffer overflow in Microsoft Windows Secure Boot allows attackers to bypass boot integrity checks after user interaction. Microsoft has not disclosed the affected Secure Boot component, the malformed input, or the operation that writes beyond a heap buffer. Exploitation requires an adjacent attack path and user interaction; successful exploitation defeats trusted boot enforcement and exposes the system to untrusted boot code.
Summary
What happened
Heap-based buffer overflow in Microsoft Windows Secure Boot allows attackers to bypass boot integrity checks after user interaction. Microsoft has not disclosed the affected Secure Boot component, the malformed input, or the operation that writes beyond a heap buffer. Exploitation requires an adjacent attack path and user interaction; successful exploitation defeats trusted boot enforcement and exposes the system to untrusted boot code.
The record
- CVE
- CVE-2024-37977
- Published
- Jul 9, 2024
- Updated
- Feb 10, 2026
- Vendor
- Microsoft
- Product
- Windows 11 version 21H2
- Classifications
- CWE-122, T1542.003
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 9, 2024CVE publishedPublication date reported by the CVE source.
- Feb 10, 2026Record 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.0 <10.0.22000.3079
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