dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2024-30014

HIGH · 7.5 CVSS v3.1 Published 2024-05-14
Fix available
A fix is available. Upgrade to 10.0.10240.20651 / 10.0.14393.6981 or later.
See remediation →
82/100
Remediation priority · High
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. RRAS is a Windows server role that enables routing and remote access capabilities. An unauthenticated attacker could send specially crafted network packets to exploit this vulnerability and execute arbitrary code on the affected system.

MitigationApply Microsoft security updates for CVE-2024-30014 immediately. Until patched, restrict network access to RRAS services and consider disabling RRAS if not required, or implement network segmentation and firewall rules to limit exposure.

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.20651
Windows 10 1607Operating system
Affected:< 10.0.14393.6981
Windows 10 1809Operating system
Affected:< 10.0.17763.5820
Windows 10 21h2Operating system
Affected:< 10.0.19044.4412
Windows 10 22h2Operating system
Affected:< 10.0.19045.4412
Windows 11 21h2Operating system
Affected:< 10.0.22000.2960
Windows 11 22h2Operating system
Affected:< 10.0.22621.3593
Windows 11 23h2Operating system
Affected:< 10.0.22631.3593

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

CVSS:3.1/AV:N/AC:H/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 is installed
    On Windows Server, open Server Manager > Manage > Add Roles and Features, look for 'Remote Access' role. On Windows 10/11, check Programs and Features > Turn Windows features on or off > look for 'Routing and Remote Access' (RRAS).
    Affected if RRAS role or feature is installed on the system
  2. Confirm RRAS service status
    Open Services console (services.msc) and check the 'Routing and Remote Access' service. Run 'sc query RemoteAccess' in Command Prompt.
    Affected if The RemoteAccess service is running or set to start automatically
  3. Check Windows version against affected ranges
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to obtain the exact build number. Compare against the vulnerable version thresholds: Windows 10 1507 < 10.0.10240.20651, 1607 < 10.0.14393.6981, 1809 < 10.0.17763.5820, 21h2 < 10.0.19044.4412, 22h2 < 10.0.19045.4412; Windows 11 21h2 < 10.0.22000.2960, 22h2 < 10.0.22621.3593, 23h2 < 10.0.22631.3593.
    Affected if The installed Windows build number falls below the fixed version for that specific release
  4. Verify network exposure of RRAS
    Check RRAS configuration in Routing and Remote Access snap-in (rrasmgmt.msc) or via 'netsh routing ip show interface'. Determine if RRAS is bound to external-facing network adapters.
    Affected if RRAS is configured and bound to network interfaces accessible from untrusted networks

The system is affected if RRAS is installed and running on a vulnerable Windows version (build below the fixed threshold) and the system is network-accessible.

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.20651 / 10.0.14393.6981 / 10.0.17763.5820 or later
Fixed in 10.0.10240.2065110.0.14393.698110.0.17763.5820
Interim mitigation

Apply Microsoft security updates for CVE-2024-30014 immediately. Until patched, restrict network access to RRAS services and consider disabling RRAS if not required, or implement network segmentation and firewall rules to limit exposure.

Recommended fix High confidence

Windows security updates released in May 2024 (KB5037771 or equivalent monthly rollup) - specific builds: 10.0.10240.20651, 10.0.14393.6981, 10.0.17763.5820, 10.0.19044.4412, 10.0.19045.4412, 10.0.22000.2960, 10.0.22621.3593, 10.0.22631.3593

  1. Identify all Windows systems running affected versions using system inventory or vulnerability scanning tools
  2. Review the list of affected Windows versions against your environment to determine which systems need updating
  3. Download and apply the appropriate Windows security update from Microsoft Update Catalog or your organization's update infrastructure
  4. For Windows 10 systems: update to version 10.0.10240.20651 (1507), 10.0.14393.6981 (1607), 10.0.17763.5820 (1809), 10.0.19044.4412 (21h2), or 10.0.19045.4412 (22h2)
  5. For Windows 11 systems: update to version 10.0.22000.2960 (21h2), 10.0.22621.3593 (22h2), or 10.0.22631.3593 (23h2)
  6. After applying updates, restart affected systems to complete the patch installation
  7. Verify successful patching by checking system version information (winver) and confirming RRAS service functionality
Caveat Standard Windows update risks apply - test updates in staging environment before broad deployment; some legacy RRAS configurations may require review after patching

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-30014 — 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-30014 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