dbcve.org
Windows Server 2012Operating system · Microsoft

CVE-2024-49129

HIGH · 7.5 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 →
81/100
Remediation priority · High
Remotely reachable 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 Gateway (RD Gateway) 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 · moderate confidence

A denial of service vulnerability in Windows Remote Desktop Gateway (RD Gateway) allows an unauthenticated attacker to crash the RD Gateway service, disrupting remote desktop connections.

MitigationApply the relevant Microsoft security update for CVE-2024-49129 to Windows systems running RD Gateway; verify service availability post-patch.

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 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:L/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. Confirm RD Gateway role is installed
    Open Server Manager, go to Manage > Add Roles and Features, or run 'Get-WindowsFeature -Name RD-Gateway' in PowerShell. Alternatively, check for the service 'UmRdpService' or 'Remote Desktop Gateway' in services.msc
    Affected if RD Gateway role is installed and the service exists on the system
  2. Verify Windows Server version and build number
    Run 'winver' from command prompt, or execute 'systeminfo | findstr /C:"OS Name" /C:"OS Version"' in cmd.exe, or use PowerShell: '[System.Environment]::OSVersion.Version' or 'Get-ComputerInfo | Select-Object WindowsProductName, WindowsVersion, OsHardwareAbstractionLayerBuildNumber'
    Affected if The Windows Server version falls within the affected ranges (2012/2012 R2, 2016 < 10.0.14393.7606, 2019 < 10.0.17763.6659, 2022 < 10.0.20348.2966, 2025 < 10.0.26100.2605)
  3. Check if RD Gateway service is running
    Open services.msc and look for 'Remote Desktop Gateway' service, or run 'Get-Service -Name UmRdpService' in PowerShell
    Affected if The RD Gateway service is running and accepting connections, exposing the vulnerability to network attackers
  4. Confirm the exact OS build number
    Run 'winver' and note the full build number displayed (for example: 10.0.17763.1), or use 'Get-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion' | Select-Object CurrentBuild, CurrentBuildNumber, DisplayVersion, UBR' in PowerShell to get precise build information
    Affected if The build number is lower than the fixed versions: 7606 for Server 2016, 6659 for Server 2019, 2966 for Server 2022, 2605 for Server 2025 (all versions of Server 2012/2012 R2 are affected)

A system is affected if it runs a vulnerable Windows Server version within the specified ranges AND has the RD Gateway role installed with the service enabled.

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 the relevant Microsoft security update for CVE-2024-49129 to Windows systems running RD Gateway; verify service availability post-patch.

Recommended fix High confidence

Windows Server 2012/2012 R2: Upgrade to Windows Server 2019, 2022, or 2025; Other versions: Apply the specified cumulative update to reach the fixed build number

  1. Identify the current Windows Server version by running 'winver' or 'systeminfo' in Command Prompt
  2. For Windows Server 2016: Apply update KB5055529 or later to reach build 10.0.14393.7606
  3. For Windows Server 2019: Apply update KB5055533 or later to reach build 10.0.17763.6659
  4. For Windows Server 2022: Apply update KB5002414 or later to reach build 10.0.20348.2966
  5. For Windows Server 2025: Apply the February 2025 cumulative update or later to reach build 10.0.26100.2605
  6. For Windows Server 2012/2012 R2: No patches available; plan migration to a supported Windows Server version as these versions reached end of support in October 2023
  7. After applying updates, restart the affected servers to complete the patch installation
  8. Verify the build version matches the fixed release using 'winver' or 'systeminfo'
Caveat Windows Server 2012/2012 R2 have no security patches available and require full OS migration; standard cumulative update applies to other versions with no expected breaking changes

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

Fix this in Windows Server 2012 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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