Authenticated code execution via unverified debugger payloads
Published Mar 11, 2025 · Updated Feb 13, 2026
Improper signature verification in Microsoft WinDbg before 1.2502.25002.0 allows remote authenticated users to execute code over a network. During dump analysis, SOS secure mode incorrectly validates cryptographic signatures on downloaded dynamic payloads and can load tampered code. Exploitation requires an authenticated network attacker and high-complexity preparation, but no user interaction, and code runs in the debugger's security context.
Summary
What happened
Improper signature verification in Microsoft WinDbg before 1.2502.25002.0 allows remote authenticated users to execute code over a network. During dump analysis, SOS secure mode incorrectly validates cryptographic signatures on downloaded dynamic payloads and can load tampered code. Exploitation requires an authenticated network attacker and high-complexity preparation, but no user interaction, and code runs in the debugger's security context.
The record
- CVE
- CVE-2025-24043
- Published
- Mar 11, 2025
- Updated
- Feb 13, 2026
- Vendor
- Microsoft
- Product
- WinDbg
- Classifications
- CWE-347
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 11, 2025CVE publishedPublication date reported by the CVE source.
- Feb 13, 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=1.0.0 <1.2502.25002.0
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