Remote Desktop ClientApplication · Microsoft

CVE-2024-38131

HIGH · 8.8 CVSS v3.1 Published 2024-08-13
Fix available
A fix is available. Upgrade to 1.2.5560.0 / 10.0.10240.20751 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Clipboard Virtual Channel Extension 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
Remote Desktop ClientApplication
Affected:< 1.2.5560.0
Windows 10 1507Operating system
Affected:< 10.0.10240.20751
Windows 10 1607Operating system
Affected:< 10.0.14393.7259
Windows 10 1809Operating system
Affected:< 10.0.17763.6189
Windows 10 21h2Operating system
Affected:< 10.0.19044.4780
Windows 10 22h2Operating system
Affected:< 10.0.19045.4780
Windows 11 21h2Operating system
Affected:< 10.0.22000.3147
Windows 11 22h2Operating system
Affected:< 10.0.22621.4037

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 1.2.5560.0 / 10.0.10240.20751 / 10.0.14393.7259 or later
Fixed in 1.2.5560.010.0.10240.2075110.0.14393.7259
Vendor patch msrc.microsoft.com →
Recommended fix High confidence

Windows 10 1507: 10.0.10240.20751 or later | Windows 10 1607: 10.0.14393.7259 or later | Windows 10 1809: 10.0.17763.6189 or later | Windows 10 21h2: 10.0.19044.4780 or later | Windows 10 22h2: 10.0.19045.4780 or later | Windows 11 21h2: 10.0.22000.3147 or later | Windows 11 22h2: 10.0.22621.4037 or

  1. Identify the affected Windows version by running 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"'
  2. Identify the Remote Desktop Client version by running 'mstsc.exe /version' or checking About in the RDP client
  3. For Windows systems: Install the applicable Windows security update via Windows Update, WSUS, or Microsoft Update Catalog
  4. For Remote Desktop Client: Update to version 1.2.5560.0 or later (included in Windows updates)
  5. Verify the update was successful by re-checking the version numbers
Caveat Standard Windows update process with typical update risks (ensure backups and test in non-production first)

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-38131 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-38131 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