dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2024-49080

HIGH · 8.8 CVSS v3.1 Published 2024-12-12
Fix available
A fix is available. Upgrade to 10.0.10240.20857 / 10.0.14393.7606 or later.
See remediation →
94/100
Remediation priority · Urgent
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 IP Routing Management Snapin 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 the Windows IP Routing Management Snapin. The vulnerability allows an attacker to execute arbitrary code on affected Windows systems through the snapin component, likely by triggering unsafe deserialization or memory corruption during snapin operations.

MitigationApply the Microsoft security update for CVE-2024-49080 once released. Prioritize patching systems with the Routing and Remote Access Service (RRAS) or IP Routing Management components enabled.

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 1507Operating system
Affected:< 10.0.10240.20857
Windows 10 1607Operating system
Affected:< 10.0.14393.7606
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

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

CVSS:3.1/AV:N/AC:L/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. Identify Windows version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to get the exact Windows build number
    Affected if The build number is lower than any of these thresholds: 10240.20857 (Win10 1507), 14393.7606 (Win10 1607), 17763.6659 (Win10 1809), 19044.5247 (Win10 21h2), 19045.5247 (Win10 22h2), 22621.4602 (Win11 22h2), 22631.4602 (Win11 23h2), 26100.2605 (Win11 24h2)
  2. Verify IP Routing Management Snapin presence
    Open the Microsoft Management Console (mmc.exe), add the IP Routing Management Snapin via File > Add/Remove Snap-in, or check for the snapin DLL in the Windows system directories
    Affected if The IP Routing Management Snapin is installed and accessible on the system
  3. Check Routing and Remote Access Service status
    Run 'services.msc' and locate the 'Routing and Remote Access' service, or run 'sc query RemoteAccess' from command prompt
    Affected if RRAS service is installed and running on the system, as this component exposes the vulnerable snapin interface

You are affected if your Windows build number falls below the thresholds listed AND the IP Routing Management Snapin or RRAS is present on your system.

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.10240.20857 / 10.0.14393.7606 / 10.0.17763.6659 or later
Fixed in 10.0.10240.2085710.0.14393.760610.0.17763.6659
Interim mitigation

Apply the Microsoft security update for CVE-2024-49080 once released. Prioritize patching systems with the Routing and Remote Access Service (RRAS) or IP Routing Management components enabled.

Recommended fix Moderate confidence

Windows 10 1507: 10.0.10240.20857 | Windows 10 1607: 10.0.14393.7606 | Windows 10 1809: 10.0.17763.6659 | Windows 10 21h2: 10.0.19044.5247 | Windows 10 22h2: 10.0.19045.5247 | Windows 11 22h2: 10.0.22621.4602 | Windows 11 23h2: 10.0.22631.4602 | Windows 11 24h2: 10.0.26100.2605

  1. Identify the current Windows version by running 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"'
  2. Open Windows Update by navigating to Settings > Update & Security > Windows Update
  3. Click 'Check for updates' and install all available security updates
  4. If the specific update for CVE-2024-49080 is not automatically offered, manually search for and install the corresponding Windows security update (KB5046706 or later for Windows 11 24h2, with equivalent updates for other versions)
  5. After installation, restart the system to complete the patch deployment
  6. Verify the installed version matches or exceeds the fixed version for your Windows release using 'winver'
Caveat Standard Windows security update deployment; may require system restart

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

Fix this in Windows 10 1507 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-49080 — 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-49080 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