Local privilege escalation via Secure Kernel heap overflow
Published Oct 8, 2024 · Updated Aug 19, 2026
Heap-based buffer overflow in Microsoft Windows Secure Kernel Mode allows local users to elevate privileges through an undisclosed input path. Microsoft has not disclosed the affected function or the operation that mishandles untrusted input; independent patch-diff research found ambiguous patch assignments. Exploitation requires low-privilege local access and no user interaction; success elevates the user across the Secure Kernel security boundary.
Summary
What happened
Heap-based buffer overflow in Microsoft Windows Secure Kernel Mode allows local users to elevate privileges through an undisclosed input path. Microsoft has not disclosed the affected function or the operation that mishandles untrusted input; independent patch-diff research found ambiguous patch assignments. Exploitation requires low-privilege local access and no user interaction; success elevates the user across the Secure Kernel security boundary.
The record
- CVE
- CVE-2024-43528
- Published
- Oct 8, 2024
- Updated
- Aug 19, 2026
- Vendor
- Microsoft
- Product
- Windows Server 2019
- Classifications
- CWE-122, T1068
- Attack vector
- local
- Privileges
- authenticated
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.17763.0 <10.0.17763.6532
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