dbcve.org
Windows Server 2012Operating system · Microsoft

CVE-2024-49128

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
Sensitive data storage in improperly locked memory in Windows Remote Desktop Services allows an unauthorized attacker to execute code over a network.

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 vulnerability in Windows Remote Desktop Services allows sensitive data to be stored in improperly locked memory, enabling an unauthorized remote attacker to execute arbitrary code over a network. The flaw stems from insufficient memory protection mechanisms that fail to properly secure sensitive data structures.

MitigationApply the Microsoft security update for CVE-2024-49128 when available. In the interim, restrict RDP access via network-level controls (VPN, firewall rules), disable RDP if not required, and enforce Network Level Authentication (NLA).

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. Identify Windows Server version and build number
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to display the installed Windows Server version and build number
    Affected if The displayed build number falls within an affected range: Server 2016 < 10.0.14393.7606, Server 2019 < 10.0.17763.6659, Server 2022 < 10.0.20348.2966, Server 2022 23h2 < 10.0.25398.1308, Server 2025 < 10.0.26100.2605, or Server 2012 (any version)
  2. Verify Remote Desktop Services is enabled
    Open Services (services.msc) and check if 'Remote Desktop Services' (TermService) is running, or run 'reg query HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server /v fDenyTSConnections' to check the RDP enablement registry value
    Affected if The registry value fDenyTSConnections is 0 (RDP enabled) or the TermService service is running
  3. Check RDP listener configuration
    Run 'netsh advfirewall firewall show rule name=all' or check Event Viewer for RDP listener events under Microsoft-Windows-TerminalServices-RDPClient/Operational
    Affected if RDP listeners are configured and active on the system

A system is affected if it runs a vulnerable Windows Server version (below the fixed build) AND has Remote Desktop Services enabled and listening.

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 Microsoft security update for CVE-2024-49128 when available. In the interim, restrict RDP access via network-level controls (VPN, firewall rules), disable RDP if not required, and enforce Network Level Authentication (NLA).

Recommended fix High confidence

Windows Server 2016: build 10.0.14393.7606+ | Windows Server 2019: build 10.0.17763.6659+ | Windows Server 2022: build 10.0.20348.2966+ | Windows Server 2022 23h2: build 10.0.25398.1308+ | Windows Server 2025: build 10.0.26100.2605+ | Windows Server 2012/2012 R2: migrate to supported version

  1. Identify the current Windows Server build version by running 'winver' or 'systeminfo' in Command Prompt
  2. For Windows Server 2016: Update to build 10.0.14393.7606 or later via Windows Update or manually download the security update from Microsoft Update Catalog
  3. For Windows Server 2019: Update to build 10.0.17763.6659 or later via Windows Update or manually download the security update from Microsoft Update Catalog
  4. For Windows Server 2022: Update to build 10.0.20348.2966 or later via Windows Update
  5. For Windows Server 2022 23h2: Update to build 10.0.25398.1308 or later via Windows Update
  6. For Windows Server 2025: Update to build 10.0.26100.2605 or later via Windows Update
  7. For Windows Server 2012/2012 R2: Microsoft no longer supports these versions; migrate to a supported Windows Server version (recommended: Windows Server 2022 or 2025)
  8. After updating, verify the build version matches or exceeds the fixed build for your version
Caveat Windows Server 2012/2012 R2 has no security updates available; continued use poses extreme risk; migration to newer version required

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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