dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2024-30029

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

A remote code execution vulnerability exists in Windows Routing and Remote Access Service (RRAS). An unauthenticated attacker could send specially crafted network packets to a vulnerable RRAS server to execute arbitrary code with elevated privileges.

MitigationApply the Microsoft security update for CVE-2024-30029. If immediate patching is not possible, consider disabling RRAS if not required, or restricting network access to RRAS servers via firewalls or network segmentation.

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 is installed or enabled
    Open Server Manager > Add Roles and Features, or check Services console (services.msc) for 'Routing and Remote Access' service. On client Windows, check: Control Panel > Network and Internet > Network and Sharing Center > Change adapter settings > right-click network connection > Properties > check for 'Routing and Remote Access' component.
    Affected if RRAS component is present on the system (vulnerability only applies if RRAS is installed/enabled)
  2. Check Windows version against affected ranges
    Run 'winver' from Run dialog, or execute 'systeminfo' in Command Prompt, or run 'Get-ComputerInfo | Select-Object WindowsVersion,OsVersion' in PowerShell.
    Affected if Windows version is less than any of these thresholds: 10.0.10240.20651 (1507), 10.0.14393.6981 (1607), 10.0.17763.5820 (1809), 10.0.19044.4412 (21h2), 10.0.19045.4412 (22h2), 10.0.22000.2960 (Win11 21h2), 10.0.22621.3593 (Win11 22h2), 10.0.22631.3593 (Win11 23h2)
  3. Confirm RRAS service status
    Open Services console (services.msc), locate 'Routing and Remote Access' service, and check its Status column. Alternatively, run 'Get-Service RemoteAccess' in PowerShell.
    Affected if RRAS service is running (the vulnerability is exploitable only when the service is active)
  4. Determine if security update is applied
    Run 'Get-HotFix -Description 'Security Update'' | Where-Object {$_.InstalledOn -gt (Get-Date).AddDays(-60)} in PowerShell, or check Windows Update history for recent RRAS-related security patches.
    Affected if No security update for CVE-2024-30029 is installed (version remains below patched build numbers)

System is affected if RRAS is installed/enabled AND the Windows build number is below the fixed version for that Windows release line, and the security update is not installed.

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 the Microsoft security update for CVE-2024-30029. If immediate patching is not possible, consider disabling RRAS if not required, or restricting network access to RRAS servers via firewalls or network segmentation.

Recommended fix High confidence

Windows 10 1507: 10.0.10240.20651 | Windows 10 1607: 10.0.14393.6981 | Windows 10 1809: 10.0.17763.5820 | Windows 10 21h2: 10.0.19044.4412 | Windows 10 22h2: 10.0.19045.4412 | Windows 11 21h2: 10.0.22000.2960 | Windows 11 22h2: 10.0.22621.3593 | Windows 11 23h2: 10.0.22631.3593

  1. Check current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Open Settings > Update & Security > Windows Update
  3. Click 'Check for updates' to download and install the security update
  4. Alternatively, manually download the specific security update from the Microsoft Catalog (KB) for your Windows version
  5. Restart the computer after the update is installed
  6. Verify the update was successful by checking Windows Update history for the corresponding security patch
Caveat Standard Windows cumulative update; no expected breaking changes

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