dbcve.org
Windows Server 2008Operating system · Microsoft

CVE-2024-38074

CRITICAL · 9.8 CVSS v3.1 Published 2024-07-09
Fix available
A fix is available. Upgrade to 10.0.14393.7159 / 10.0.17763.6054 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Windows Remote Desktop Licensing Service Remote Code Execution Vulnerability

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Windows Server 2008Operating system
Affected:= r2
Windows Server 2012Operating system
Affected:all versions= r2
Windows Server 2016Operating system
Affected:< 10.0.14393.7159
Windows Server 2019Operating system
Affected:< 10.0.17763.6054
Windows Server 2022Operating system
Affected:< 10.0.20348.2582
Windows Server 2022 23h2Operating system
Affected:< 10.0.25398.1009

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.0.14393.7159 / 10.0.17763.6054 / 10.0.20348.2582 or later
Fixed in 10.0.14393.715910.0.17763.605410.0.20348.2582
Vendor patch msrc.microsoft.com →
Recommended fix High confidence

Upgrade to Windows Server 2022 (build 10.0.20348.2582 or later) or Windows Server 2025 for the most current security support

  1. Verify current Windows Server build version by running 'winver' or 'systeminfo' in command prompt
  2. Identify the affected Windows Server version from the list: 2008 R2, 2012, 2012 R2, 2016, 2019, 2022, or 2022 23h2
  3. Apply the security update from Microsoft Update Catalog or Windows Update for the specific version: Windows Server 2016 requires build 10.0.14393.7159 or higher; Windows Server 2019 requires build 10.0.17763.6054 or higher; Windows Server 2022 requires build 10.0.20348.2582 or higher; Windows Server 2022 23h2 requires build 10.0.25398.1009 or higher
  4. For Windows Server 2008 R2 and 2012/2012 R2 which are end-of-life, apply Extended Security Updates (ESU) if available or upgrade to a supported version
  5. After patching, verify the Remote Desktop Licensing Service is running and monitor for any service disruption
  6. Restart the server if required by the update
Caveat Patching should not cause breaking changes; however, verify application compatibility for legacy Windows Server 2008 R2/2012 systems as those versions are end-of-life

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $2,300. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-38074 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-38074 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data