dbcve.org
Windows Server 2012Operating system · Microsoft

CVE-2024-49120

HIGH · 8.1 CVSS v3.1 Published 2024-12-12
Fix available
A fix is available. Upgrade to 10.0.14393.7606 / 10.0.17763.6659 or later.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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

A remote code execution vulnerability exists in Windows Remote Desktop Services. The vulnerability allows an attacker to execute arbitrary code on the target system through the Remote Desktop Protocol (RDP) service, potentially gaining full system control without authentication in some scenarios.

MitigationApply Microsoft security updates for CVE-2024-49120 immediately to all affected Windows systems. If immediate patching is not possible, consider blocking RDP at the network perimeter or disabling Remote Desktop Services if not required.

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
Windows Server 2012Operating system
Affected:all versions= r2
Windows Server 2016Operating system
Affected:< 10.0.14393.7606
Windows Server 2019Operating system
Affected:< 10.0.17763.6659
Windows Server 2022Operating system
Affected:< 10.0.20348.2966
Windows Server 2022 23h2Operating system
Affected:< 10.0.25398.1308
Windows Server 2025Operating system
Affected:< 10.0.26100.2605

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

Work through these to decide whether this CVE applies to you.

  1. Check Windows version and build number
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to obtain the exact Windows build
    Affected if The build number is lower than the version-specific thresholds (10.0.14393.7606 for Server 2016, 10.0.17763.6659 for Server 2019, 10.0.20348.2966 for Server 2022, 10.0.25398.1308 for Server 2022 23h2, 10.0.26100.2605 for Server 2025, or any version of Server 2012/R2)
  2. Verify Remote Desktop Services status
    Run 'Get-Service termservice' in PowerShell or check the Terminal Services service in services.msc
    Affected if The Remote Desktop Services (termservice) is running or set to start automatically
  3. Confirm RDP listener is active
    Run 'netstat -an | findstr ":3389"' to check if port 3389 is listening, or use PowerShell 'Get-NetTCPConnection -LocalPort 3389'
    Affected if Port 3389 is listening on any interface (0.0.0.0 or external IP)
  4. Check RDP network exposure
    Review firewall rules with 'netsh advfirewall firewall show rule name=all' or Windows Defender Firewall UI to see if RDP (port 3389) is allowed through any firewall profile
    Affected if Inbound RDP traffic is permitted by firewall rules, especially on Domain or Public profiles

A system is affected if it runs a vulnerable Windows Server version AND has Remote Desktop Services enabled and accessible via network, with the build number below the patched thresholds.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.7606 / 10.0.17763.6659 / 10.0.20348.2966 or later
Fixed in 10.0.14393.760610.0.17763.665910.0.20348.2966
Interim mitigation

Apply Microsoft security updates for CVE-2024-49120 immediately to all affected Windows systems. If immediate patching is not possible, consider blocking RDP at the network perimeter or disabling Remote Desktop Services if not required.

Recommended fix High confidence

Windows Server 2012 is end-of-life with no patch; migrate to a supported version (2016 or later). For others, apply corresponding KB update to reach minimum fixed build.

  1. Check current Windows Server version by running 'winver' or 'systeminfo' in Command Prompt
  2. Identify the applicable security update from Microsoft Security Update Guide (search for CVE-2024-49120)
  3. For Windows Server 2016: Apply KB5055529 or later security update to reach build 10.0.14393.7606
  4. For Windows Server 2019: Apply KB5055528 or later security update to reach build 10.0.17763.6659
  5. For Windows Server 2022: Apply KB5055548 or later security update to reach build 10.0.20348.2966
  6. For Windows Server 2022 23h2: Apply KB5055547 or later security update to reach build 10.0.25398.1308
  7. For Windows Server 2025: Apply KB5055549 or later security update to reach build 10.0.26100.2605
  8. Restart the server after applying the security update
Caveat Windows Server 2012/2012 R2 has no patch available; must migrate to newer OS version. Ensure application compatibility testing before patching supported versions.

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

Fix this in Windows Server 2012 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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