CVE-2024-49105
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 · uneditedRemote Desktop Client 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 · moderate confidenceA Remote Code Execution vulnerability in the Microsoft Remote Desktop Client that allows an attacker to execute arbitrary code on affected systems. The HIGH severity (CVSS 8.4) indicates significant potential impact.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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< 1.2.5716.0< 2.0.327.0< 10.0.10240.20857< 10.0.14393.7606< 10.0.17763.6659< 10.0.19044.5247< 10.0.19045.5247< 10.0.22621.4602CVSS 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
- High
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Remote Desktop Client version (mstsc.exe)Right-click mstsc.exe in %SystemRoot%\System32, select Properties, then view the Details tab for Product Version. Or run: Get-ItemProperty 'C:\Windows\System32\mstsc.exe' | Select-Object VersionInfoAffected if Product version is below 1.2.5716.0
-
Check Microsoft Windows App versionOpen PowerShell and run: Get-AppxPackage -Name Microsoft.RemoteDesktop | Select-Object Name, VersionAffected if Version is below 2.0.327.0
-
Check Windows 10 build versionOpen Settings > System > About, or run: winver, or run: [System.Environment]::OSVersion.Version.Build in PowerShellAffected if Build number is below 10240.20857 (1507), 14393.7606 (1607), 17763.6659 (1809), 19044.5247 (21h2), or 19045.5247 (22h2)
-
Check Windows 11 22h2 build versionOpen Settings > System > About, or run: winver, or run: [System.Environment]::OSVersion.Version.Build in PowerShellAffected if Build number is below 22621.4602
The environment is affected if the installed Remote Desktop Client is below 1.2.5716.0, Windows App is below 2.0.327.0, or the Windows OS build is below the threshold for the installed Windows version.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.2.5716.02.0.327.010.0.10240.20857
Apply available Microsoft security updates for the Remote Desktop Client. Until patched, limit RDP connections to trusted servers and disable RDP client features when not needed.
Apply December 2024 Windows Security Updates (or subsequent updates) containing the CVE-2024-49105 fix
- Open Windows Settings and navigate to Windows Update
- Click 'Check for updates' to download and install the latest security patches
- For enterprise deployments, manually download and install the corresponding KB patch from the Microsoft Update Catalog
- Restart the system if prompted
- Verify the installed version meets the fixed release: Remote Desktop Client >= 1.2.5716.0, Windows App >= 2.0.327.0, or Windows 10/11 version >= the build numbers specified (e.g., Windows 11 22h2 >= 10.0.22621.4602)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-49105 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-49105 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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