Local security bypass via improper signature verification
Published Jul 9, 2024 · Updated Feb 10, 2026
Improper signature verification in Microsoft Windows Enroll Engine allows local users to bypass a security feature on affected Windows builds. Microsoft identifies the locus as the Enroll Engine and maps it to CWE-347, but does not disclose which signed data is accepted or how verification fails. Exploitation requires local low-privilege access and high-complexity conditions; success can compromise confidentiality, integrity, and availability.
Summary
What happened
Improper signature verification in Microsoft Windows Enroll Engine allows local users to bypass a security feature on affected Windows builds. Microsoft identifies the locus as the Enroll Engine and maps it to CWE-347, but does not disclose which signed data is accepted or how verification fails. Exploitation requires local low-privilege access and high-complexity conditions; success can compromise confidentiality, integrity, and availability.
The record
- CVE
- CVE-2024-38069
- Published
- Jul 9, 2024
- Updated
- Feb 10, 2026
- Vendor
- Microsoft
- Product
- Windows 10 Version 1507
- Classifications
- CWE-347, T1553
- Attack vector
- local
- Privileges
- authenticated
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