CVE-2024-49119
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 · uneditedWindows Remote Desktop Services 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 Windows Remote Desktop Services with CVSS 8.1 (HIGH). The vulnerability allows remote attackers to execute arbitrary code on affected Windows systems through the Remote Desktop Services protocol, likely via specially crafted requests.
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< 10.0.14393.7606< 10.0.17763.6659< 10.0.20348.2966< 10.0.25398.1308< 10.0.26100.2605CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/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.
-
Identify Windows Server version and build numberOpen Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to obtain the full version and build numberAffected if The build number is lower than 7606 for Server 2016, 6659 for Server 2019, 2966 for Server 2022, 1308 for Server 2022 23h2, or 2605 for Server 2025
-
Verify Remote Desktop Services is enabledOpen Command Prompt and run 'reg query "HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server" /v fDenyTSConnections' - a value of 0 means RDP is enabledAffected if The fDenyTSConnections value is 0 (RDP enabled) AND the Windows version is below the affected thresholds in step 1
-
Confirm Terminal Services service statusOpen Services console (services.msc) or run 'sc query TermService' to check if the Terminal Services service is runningAffected if The service state shows as RUNNING and the Windows version is below the affected thresholds in step 1
A system is affected if it runs a Windows Server version with a build number below the thresholds AND has Remote Desktop Services enabled or running.
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 · scoped10.0.14393.760610.0.17763.665910.0.20348.2966
Apply Microsoft security updates for CVE-2024-49119 to affected Windows systems running Remote Desktop Services. Prioritize internet-facing RDP servers.
Windows Server 2016: 10.0.14393.7606 | Windows Server 2019: 10.0.17763.6659 | Windows Server 2022: 10.0.20348.2966 | Windows Server 2022 23h2: 10.0.25398.1308 | Windows Server 2025: 10.0.26100.2605
- 1. Identify the current Windows Server version by running 'winver' or 'systeminfo' in Command Prompt
- 2. Download the appropriate security update from Microsoft Update Catalog (search for CVE-2024-49119) or use Windows Update
- 3. Apply the security update to the affected Windows Server
- 4. Restart the server as prompted by the update installation
- 5. Verify the update was installed successfully by checking the installed updates or running 'winver' to confirm the version matches or exceeds the fixed version
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-49119 — 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-49119 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