dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2024-49089

HIGH · 7.2 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 →
78/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 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

A Remote Code Execution vulnerability in Windows Routing and Remote Access Service (RRAS) allows an attacker to execute arbitrary code on affected Windows systems. The vulnerability affects a core Windows networking service and is rated HIGH severity with CVSS 7.2.

MitigationApply Microsoft security updates for CVE-2024-49089 immediately when available. If RRAS is not required, disable the service. Ensure network segmentation and least-privilege access controls are in place as defense-in-depth measures.

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

CVSS:3.1/AV:N/AC:L/PR:H/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. Check Windows version and build number
    Open Command Prompt or PowerShell and run: `winver` or `systeminfo | findstr /B /C:"OS Name" /C:"OS Version"`. Alternatively, run `winmgmt /salvagerepository` or check the registry at HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion
    Affected if The installed Windows version and build number fall within the affected ranges (Windows 10 1507 < 10.0.10240.20857, 1607 < 10.0.14393.7606, 1809 < 10.0.17763.6659, 21h2 < 10.0.19044.5247, 22h2 < 10.0.19045.5247, or Windows 11 22h2 < 10.0.22621.4602, 23h2 < 10.0.22631.4602, 24h2 < 10.0.26100.2605)
  2. Verify RRAS service status
    Open Services console (services.msc) or run `Get-Service RemoteAccess` in PowerShell. Check if the "Remote Access" service (formerly Routing and Remote Access) is installed and its current state (Running, Stopped, or Disabled)
    Affected if The RemoteAccess/RRAS service is present on the system (even if stopped, the vulnerable code is installed)
  3. Check RRAS service configuration
    Run `netsh routing ip show global` or check the registry at HKLM\SYSTEM\CurrentControlSet\Services\RemoteAccess\Parameters for RRAS configuration keys. In PowerShell, check: `Get-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Services\RemoteAccess'`
    Affected if RRAS is configured or enabled (any non-default configuration present, or the service is set to start automatically)
  4. Identify if RRAS is required
    Review installed server roles or features. On Windows Server, check Server Manager for "Routing and Remote Access" role. On workstations, verify if RRAS was manually installed or configured. Run `Get-WindowsOptionalFeature -Online | Where-Object {$_.FeatureName -like '*RemoteAccess*'}` in PowerShell
    Affected if RRAS features or roles are installed/enabled on the system

A system is affected if it runs a vulnerable Windows version listed in the affected ranges AND has RRAS installed, regardless of whether the service is currently running.

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 Microsoft security updates for CVE-2024-49089 immediately when available. If RRAS is not required, disable the service. Ensure network segmentation and least-privilege access controls are in place as defense-in-depth measures.

Recommended fix High confidence

Windows 10/11 November 2024 Security Update (or minimum fixed version per product branch as listed)

  1. Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine which affected version range your current Windows installation falls into from the CVE details
  3. Apply the November 2024 Windows Security Update (or subsequent cumulative update) that addresses CVE-2024-49089
  4. Alternatively, upgrade to a version at or above the fixed version for your Windows release: Windows 10 1507 to 10.0.10240.20857, Windows 10 1607 to 10.0.14393.7606, Windows 10 1809 to 10.0.17763.6659, Windows 10 21h2 to 10.0.19044.5247, Windows 10 22h2 to 10.0.19045.5247, Windows 11 22h2 to 10.0.22621.4602, Windows 11 23h2 to 10.0.22631.4602, or Windows 11 24h2 to 10.0.26100.2605
  5. Restart the system after applying the update
  6. Verify the update was installed by checking Windows Update history for the security patch containing CVE-2024-49089
Caveat Standard Windows update risks - ensure critical data is backed up before applying updates

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
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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