dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2024-49075

HIGH · 7.5 CVSS v3.1 Published 2024-12-12
Fix available
A fix is available. Upgrade to 10.0.17763.6659 / 10.0.19044.5247 or later.
See remediation →
84/100
Remediation priority · High
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 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

This is a Denial of Service vulnerability in Windows Remote Desktop Services. An unauthenticated remote attacker can likely send specially crafted requests to crash the Remote Desktop Services, causing service disruption and preventing legitimate users from establishing RDP sessions.

MitigationApply Microsoft security updates for CVE-2024-49075 when released. As an interim measure, restrict network access to RDP port (3389) via firewall rules or disable Remote Desktop Services if not business-critical.

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 10 1809Operating system
Affected:< 10.0.17763.6659
Windows 10 21h2Operating system
Affected:< 10.0.19044.5247
Windows 10 22h2Operating system
Affected:< 10.0.19045.5247
Windows 11 22h2Operating system
Affected:< 10.0.22621.4602
Windows 11 23h2Operating system
Affected:< 10.0.22631.4602
Windows 11 24h2Operating system
Affected:< 10.0.26100.2605
Windows Server 2019Operating system
Affected:< 10.0.17763.6659
Windows Server 2022Operating system
Affected:< 10.0.20348.2966

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Verify Remote Desktop Services is enabled
    Run 'Get-ItemProperty -Path 'HKLM:\System\CurrentControlSet\Control\Terminal Server' -Name 'fDenyTSConnections' | Select-Object -ExpandProperty fDenyTSConnections' in PowerShell. A value of 0 means RDP is enabled.
    Affected if The value returned is 0, indicating RDP is enabled and the system could be affected.
  2. Check Windows 10 1809 / Server 2019 build number
    Run 'winver' or 'systeminfo | findstr /C:"Build"' and note the build number (for example, 10.0.17763.x).
    Affected if The build number is less than 10.0.17763.6659.
  3. Check Windows 10 21h2 build number
    Run 'winver' or 'systeminfo | findstr /C:"Build"' and note the build number (10.0.19044.x).
    Affected if The build number is less than 10.0.19044.5247.
  4. Check Windows 10 22h2 build number
    Run 'winver' or 'systeminfo | findstr /C:"Build"' and note the build number (10.0.19045.x).
    Affected if The build number is less than 10.0.19045.5247.
  5. Check Windows 11 22h2 build number
    Run 'winver' or 'systeminfo | findstr /C:"Build"' and note the build number (10.0.22621.x).
    Affected if The build number is less than 10.0.22621.4602.
  6. Check Windows 11 23h2 / 24h2 or Server 2022 build number
    Run 'winver' or 'systeminfo | findstr /C:"Build"' and note the build number (23h2 is 10.0.22631.x, 24h2 is 10.0.26100.x, Server 2022 is 10.0.20348.x).
    Affected if For 23h2: build < 10.0.22631.4602. For 24h2: build < 10.0.26100.2605. For Server 2022: build < 10.0.20348.2966.

The system is affected if Remote Desktop Services is enabled AND the installed Windows build number falls below the corresponding threshold listed in the affected versions for the detected Windows release.

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.17763.6659 / 10.0.19044.5247 / 10.0.19045.5247 or later
Fixed in 10.0.17763.665910.0.19044.524710.0.19045.5247
Interim mitigation

Apply Microsoft security updates for CVE-2024-49075 when released. As an interim measure, restrict network access to RDP port (3389) via firewall rules or disable Remote Desktop Services if not business-critical.

Recommended fix High confidence

Apply the appropriate Windows security update from Microsoft Update (KB number varies by month - check MSRC for CVE-2024-49075)

  1. Identify the current Windows version by running `winver` or `systeminfo` in Command Prompt
  2. Compare the installed version against the fixed versions: Windows 10 1809 requires 10.0.17763.6659+, Windows 10 21H2 requires 10.0.19044.5247+, Windows 10 22H2 requires 10.0.19045.5247+, Windows 11 22H2 requires 10.0.22621.4602+, Windows 11 23H2 requires 10.0.22631.4602+, Windows 11 24H2 requires 10.0.26100.2605+, Windows Server 2019 requires 10.0.17763.6659+, Windows Server 2022 requires 10.0.203
  3. Open Settings > Windows Update and check for updates, or run `ms-settings:windowsupdate`
  4. Install the available security update (typically labeled as a cumulative update for the respective month/year)
  5. Restart the system when prompted
  6. Verify the version has been updated by running `winver` again
Caveat Standard Windows update with no special configuration changes required; test Remote Desktop functionality after reboot

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

Fix this in Windows 10 1809 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,180
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,488.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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