Secure Boot bypass via heap buffer overflow
Published Jul 9, 2024 · Updated Feb 10, 2026
Secure Boot bypass in Microsoft Windows allows physically proximate attackers to defeat pre-start trust enforcement through physical access. Microsoft identifies a heap-based buffer overflow but has not published the affected Secure Boot component or the unsafe memory operation. Exploitation requires physical access, needs no account or user action, and permits untrusted boot code to bypass signature-based startup controls.
Summary
What happened
Secure Boot bypass in Microsoft Windows allows physically proximate attackers to defeat pre-start trust enforcement through physical access. Microsoft identifies a heap-based buffer overflow but has not published the affected Secure Boot component or the unsafe memory operation. Exploitation requires physical access, needs no account or user action, and permits untrusted boot code to bypass signature-based startup controls.
The record
- CVE
- CVE-2024-38065
- Published
- Jul 9, 2024
- Updated
- Feb 10, 2026
- Vendor
- Microsoft
- Product
- Windows 10 Version 1507
- Classifications
- CWE-122, CWE-787, T1542.003
- Attack vector
- physical
- 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.10240.0 <10.0.10240.20710
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