Authenticated code execution via licensing-service race
Published Sep 10, 2024 · Updated Aug 10, 2026
Race condition in Remote Desktop Licensing Service on affected Windows Server releases allows remote authenticated users to execute code. Microsoft identifies improper synchronization of a shared resource but has not disclosed the affected routine, raced operations, or attacker-controlled input. Reachability requires the RD Licensing role and low-privileged network authentication; successful exploitation can compromise the service host.
Summary
What happened
Race condition in Remote Desktop Licensing Service on affected Windows Server releases allows remote authenticated users to execute code. Microsoft identifies improper synchronization of a shared resource but has not disclosed the affected routine, raced operations, or attacker-controlled input. Reachability requires the RD Licensing role and low-privileged network authentication; successful exploitation can compromise the service host.
The record
- CVE
- CVE-2024-43467
- Published
- Sep 10, 2024
- Updated
- Aug 10, 2026
- Vendor
- Microsoft
- Product
- Windows Server 2019
- Classifications
- CWE-362, T1210
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 10, 2024CVE publishedPublication date reported by the CVE source.
- Aug 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.17763.0 <10.0.17763.6293
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