dbcve.org
Windows Server 2008Operating system · Microsoft

CVE-2024-49085

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

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

MitigationApply the Microsoft security update for CVE-2024-49085 immediately, prioritizing Windows Server systems with RRAS enabled, and verify that remote access policies are properly restricted.

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. Check Windows Server version and build number
    Run 'winver' or 'systeminfo' from command prompt to obtain the exact Windows build version (for example, 10.0.17763.x). Compare your build number against the affected ranges: 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. Server 2008/2012/2012 R2 are all affected regardless of build.
    Affected if Your Windows Server version falls within any of the vulnerable version ranges listed, or you are running Server 2008/2012/2012 R2.
  2. Verify if RRAS service is installed
    Open Services console (services.msc) or run 'Get-Service RemoteAccess' in PowerShell. Look for the service named 'Remote Access (RRAS)' or 'Routing and Remote Access'.
    Affected if The RRAS service is present on the system.
  3. Confirm if RRAS is enabled or running
    In Services console, check the service status. In PowerShell, run 'Get-Service RemoteAccess | Select-Object Name,Status,StartType' to see if Status is Running or StartType is not Disabled.
    Affected if The RRAS service is started, running, or configured to start automatically (StartType is not Disabled).

You are affected if your Windows Server version is within the vulnerable build ranges AND the RRAS feature is installed and enabled 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.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-49085 immediately, prioritizing Windows Server systems with RRAS enabled, and verify that remote access policies are properly restricted.

Recommended fix High confidence

Windows Server 2016 to build 10.0.14393.7606+ | Windows Server 2019 to build 10.0.17763.6659+ | Windows Server 2022 to build 10.0.20348.2966+ | Windows Server 2022 23h2 to build 10.0.25398.1308+ | Windows Server 2025 to build 10.0.26100.2605+

  1. 1. Apply the November 2024 (or later) Windows security update through Windows Update, Microsoft Update, or your internal update management system
  2. 2. For Windows Server 2016: Update to build 10.0.14393.7606 or later
  3. 3. For Windows Server 2019: Update to build 10.0.17763.6659 or later
  4. 4. For Windows Server 2022: Update to build 10.0.20348.2966 or later
  5. 5. For Windows Server 2022 23h2: Update to build 10.0.25398.1308 or later
  6. 6. For Windows Server 2025: Update to build 10.0.26100.2605 or later
  7. 7. After updating, verify the RRAS service is running correctly and test remote access functionality
  8. 8. Note: Windows Server 2008 and Windows Server 2012 (all versions) are end-of-life and receive no security updates; migrate to a supported Windows Server version
Caveat Windows Server 2008 and 2012 have no patch available; requires operating system migration to a supported version

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 / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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