dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2024-49102

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 →
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

This is a remote code execution vulnerability in Windows Routing and Remote Access Service (RRAS), a Windows server component that handles routing and VPN connections. The high CVSS score (8.8) indicates an attacker could potentially execute arbitrary code with elevated privileges on affected systems without authentication in some scenarios.

MitigationApply the Microsoft security patch for CVE-2024-49102. If immediate patching is not possible, consider disabling or restricting RRAS service if not required, and ensure network segmentation limits exposure to untrusted networks.

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
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. Verify RRAS role or feature is installed
    On Windows Server: Open Server Manager > Manage > Add Roles and Features > check if 'Remote Access' role or 'Routing' role service is installed. On Windows 10/11: Check 'Programs and Features' > 'Turn Windows features on or off' for 'Routing and Remote Access' (RRAS) or run: Get-WindowsOptionalFeature -Online | Where-Object {$_.FeatureName -like '*RemoteAccess*' -or $_.FeatureName -like '*Routing*'}
    Affected if RRAS role, feature, or service is installed/enabled on the system
  2. Confirm RRAS service status
    Open Services console (services.msc) and check if 'Routing and Remote Access' (RRAS) service exists and its current status (Running/Stopped). Alternatively, run: Get-Service -Name 'RemoteAccess' in PowerShell
    Affected if The RemoteAccess service exists and is in a Running or Started state
  3. Check installed Windows version against affected ranges
    Run 'winver' from command prompt, or in PowerShell run: [System.Environment]::OSVersion.Version or Get-ComputerInfo | Select WindowsVersion,OsVersion. Compare the version number to 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; Windows 11 22h2 < 10.0.22621.4602, 23h2 < 10.0.22631.4602, 24h2 < 10.0.26100.2605
    Affected if The installed Windows version is lower than the fixed version for that specific Windows release
  4. Determine RRAS network exposure
    Check if RRAS ports are listening. Run: netstat -an | findstr ':1723' (PPTP VPN) or check for ports associated with your VPN type (IKEv2=500,4500; SSTP=443; L2TP=1701). Also verify firewall rules allowing inbound connections to RRAS services from untrusted networks
    Affected if RRAS service ports are listening and accessible from untrusted/network-facing interfaces

The system is affected if RRAS is installed and running on a Windows version below the fixed build numbers for that 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.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 patch for CVE-2024-49102. If immediate patching is not possible, consider disabling or restricting RRAS service if not required, and ensure network segmentation limits exposure to untrusted networks.

Recommended fix High confidence

Upgrade to the December 2024 Windows security update matching your edition (build numbers: 10.0.10240.20857, 10.0.14393.7606, 10.0.17763.6659, 10.0.19044.5247, 10.0.19045.5247, 10.0.22621.4602, 10.0.22631.4602, or 10.0.26100.2605)

  1. Identify the current Windows version by running 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"'
  2. Check if Routing and Remote Access Service (RRAS) is enabled on the system using 'services.msc' or 'Get-Service RemoteAccess'
  3. Apply the appropriate Windows security update for your version: For Windows 10 1507 upgrade to build 10.0.10240.20857 or later | For Windows 10 1607 upgrade to build 10.0.14393.7606 or later | For Windows 10 1809 upgrade to build 10.0.17763.6659 or later | For Windows 10 21h2 upgrade to build 10.0.19044.5247 or later | For Windows 10 22h2 upgrade to build 10.0.19045.5247 or later | For Windows 11
  4. Verify the update was successful by checking the Windows version matches or exceeds the required build number
  5. Restart the system if prompted to complete the update installation
Caveat Standard Windows update risks apply - ensure backups and test in non-production environment first

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

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