dbcve.org
Windows Server 2008Operating system · Microsoft

CVE-2024-38231

HIGH · 7.5 CVSS v3.1 Published 2024-09-10
Fix available
A fix is available. Upgrade to 10.0.14393.7336 / 10.0.17763.6293 or later.
See remediation →
84/100
Remediation priority · High
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 Denial of Service 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
How this class of weakness works · CWE-285

The application confirms who you are but does not properly check whether you are permitted to perform a given action, so authenticated users reach functions or data meant for others. Attackers test roles and object references to find the gap. Remediation is an authorization check on every request, evaluated against the acting user's actual permissions.

General guidance for the improper authorization class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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:all versions= r2
Windows Server 2012Operating system
Affected:all versions= r2
Windows Server 2016Operating system
Affected:< 10.0.14393.7336
Windows Server 2019Operating system
Affected:< 10.0.17763.6293
Windows Server 2022Operating system
Affected:< 10.0.20348.2700
Windows Server 2022 23h2Operating system
Affected:< 10.0.25398.1128

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.7336 / 10.0.17763.6293 / 10.0.20348.2700 or later
Fixed in 10.0.14393.733610.0.17763.629310.0.20348.2700
Vendor patch msrc.microsoft.com →
Recommended fix High confidence

Windows Server 2016 to 10.0.14393.7336 | Windows Server 2019 to 10.0.17763.6293 | Windows Server 2022 to 10.0.20348.2700 | Windows Server 2022 23h2 to 10.0.25398.1128

  1. 1. Identify the Windows Server version and current build number by running 'winver' or 'systeminfo' in Command Prompt
  2. 2. Determine if the server is running the Remote Desktop Licensing Service (typically installed on RD Connection Brokers)
  3. 3. For Windows Server 2016: Upgrade to build 10.0.14393.7336 or later
  4. 4. For Windows Server 2019: Upgrade to build 10.0.17763.6293 or later
  5. 5. For Windows Server 2022: Upgrade to build 10.0.20348.2700 or later
  6. 6. For Windows Server 2022 23h2: Upgrade to build 10.0.25398.1128 or later
  7. 7. For Windows Server 2008/2012 R2: Microsoft may offer Extended Security Updates (ESU) if applicable, otherwise these versions are end-of-life and migration is recommended
  8. 8. Apply the security update via Windows Update, WSUS, or download from Microsoft Update Catalog using the KB number referenced in the MSRC advisory
Caveat Standard monthly cumulative updates carry low risk; always test in staging before production deployment. Windows Server 2008/2012 R2 are end-of-life and require migration rather than patching.

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 $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-38231 — 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-38231 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