Physical encryption bypass via undisclosed mechanism
Published Oct 8, 2024 · Updated Aug 19, 2026
Security feature bypass in Microsoft Windows BitLocker allows physically proximate attackers to access encrypted data. Microsoft has not published the affected BitLocker component or the operation that mishandles attacker-controlled input. Physical access to the device is required, and successful exploitation defeats BitLocker protection for data on the affected system.
Summary
What happened
Security feature bypass in Microsoft Windows BitLocker allows physically proximate attackers to access encrypted data. Microsoft has not published the affected BitLocker component or the operation that mishandles attacker-controlled input. Physical access to the device is required, and successful exploitation defeats BitLocker protection for data on the affected system.
The record
- CVE
- CVE-2024-43513
- Published
- Oct 8, 2024
- Updated
- Aug 19, 2026
- Vendor
- Microsoft
- Product
- Windows 10 Version 1507
- Classifications
- CWE-693
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 8, 2024CVE publishedPublication date reported by the CVE source.
- Aug 19, 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.20796
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