Local SYSTEM escalation via kernel stack overflow
Published Nov 12, 2024 · Updated Jul 8, 2025
Stack-based buffer overflow in the Microsoft Windows Kernel allows local users with low privileges to gain SYSTEM privileges. Microsoft has not published the affected kernel routine, the attacker-controlled input, or the bounds-checking failure that corrupts the stack. A low-privileged account and local code execution are required; successful exploitation elevates that code to SYSTEM.
Summary
What happened
Stack-based buffer overflow in the Microsoft Windows Kernel allows local users with low privileges to gain SYSTEM privileges. Microsoft has not published the affected kernel routine, the attacker-controlled input, or the bounds-checking failure that corrupts the stack. A low-privileged account and local code execution are required; successful exploitation elevates that code to SYSTEM.
The record
- CVE
- CVE-2024-43630
- Published
- Nov 12, 2024
- Updated
- Jul 8, 2025
- Vendor
- Microsoft
- Product
- Windows Server 2025 (Server Core installation)
- Classifications
- CWE-121, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 12, 2024CVE publishedPublication date reported by the CVE source.
- Jul 8, 2025Record 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.26100.0 <10.0.26100.2314
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