dbcve.org
Windows Server 2008Operating system · Microsoft

CVE-2024-49125

HIGH · 8.8 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 →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 Routing and Remote Access Service (RRAS) 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

Windows Routing and Remote Access Service (RRAS) contains a remote code execution vulnerability that allows an attacker to execute arbitrary code on affected systems. RRAS is a Windows server role that handles routing and VPN functionality, making this a critical vulnerability in enterprise environments.

MitigationApply the appropriate Microsoft security update for this vulnerability. If immediate patching is not possible, consider disabling or restricting RRAS services and implementing network-level filters to limit attack surface.

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 2008Operating system
Affected:all versions= r2
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
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 Windows Server version and build number
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to identify the exact Windows Server version and build number.
    Affected if The build number is below 14393.7606 (Server 2016), 17763.6659 (Server 2019), 20348.2966 (Server 2022), 25398.1308 (Server 2022 23h2), or 26100.2605 (Server 2025). Server 2008/2012 all versions are affected.
  2. Check if RRAS role is installed
    Run 'Get-WindowsFeature -Name RemoteAccess' in PowerShell with admin rights. Alternatively, check Server Manager under 'Remote Access' role.
    Affected if The RemoteAccess feature is installed (Install State shows 'Installed').
  3. Verify RRAS service status
    Run 'Get-Service RemoteAccess' or check the 'Routing and Remote Access' service in services.msc.
    Affected if The service exists and is in a Started or Running state.
  4. Check RRAS configuration for exposed network listeners
    Inspect RRAS configuration via 'netsh routing ip show config' or through the Routing and Remote Access snap-in (rrasmgmt.msc). Look for listening interfaces, VPN, or dial-in enabled settings.
    Affected if RRAS has active interfaces configured for VPN, dial-in, or routing protocols exposed to network.

A system is affected if it runs a vulnerable Windows Server version AND has RRAS installed with the RemoteAccess service enabled and configured.

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 appropriate Microsoft security update for this vulnerability. If immediate patching is not possible, consider disabling or restricting RRAS services and implementing network-level filters to limit attack surface.

Recommended fix High confidence

Apply Microsoft security update KB5044284 (or subsequent related update) which contains the fix for CVE-2024-49125 - the fixed builds are: Windows Server 2016 build 14393.7606, Server 2019 build 17763.6659, Server 2022 build 20348.2966, Server 2022 23H2 build 25398.1308, Server 2025 build 26100.2605

  1. Apply the latest Windows security update for CVE-2024-49125 via Windows Update or your patch management system
  2. Verify the RRAS service is running the patched version by checking Windows Update history or reviewing the installed hotfixes
  3. For Windows Server 2008/2012 (end-of-life): disable the RRAS service if not needed, or isolate the server on a restricted network segment
  4. After patching, verify RRAS functionality remains operational
  5. Review and confirm the security update is listed in Add/Remove Programs as a successfully installed update
Caveat Patches for RRAS may require a service restart; test in staging first if RRAS is business-critical

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

Fix this in Windows Server 2008 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-49125 — 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-49125 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