dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2024-30022

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. The CVSS 7.5 score indicates network-exploitable code execution without authentication. RRAS handles routing and VPN connections on Windows servers, making this a potentially severe infrastructure vulnerability.

MitigationApply Microsoft security updates for CVE-2024-30022 to affected Windows systems. If patching is not immediately feasible, consider disabling RRAS if not required, or implementing network segmentation 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. Confirm RRAS is installed or running
    Open Services console (services.msc) and look for 'Routing and Remote Access' service, or run 'Get-Service RemoteAccess' in PowerShell
    Affected if RRAS service exists and is in a started or stopped state on the system
  2. Identify Windows version
    Run 'winver' command or check System Properties, or run 'Get-ComputerInfo | Select WindowsProductName, WindowsVersion' in PowerShell
    Affected if The Windows version falls within the affected ranges: 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), or Windows 11 21h2 (<10.0.22000.2960), 22h2 (<10.0.22621.3593), 23h2 (<10.0.22631.3593)
  3. Check installed security updates
    Run 'Get-HotFix | Where-Object {$_.Description -eq 'Security Update'} | Sort-Object InstalledOn -Descending' in PowerShell, or view installed updates via Control Panel > Programs > View installed updates
    Affected if No security update for CVE-2024-30022 is listed among installed hotfixes

System is affected if RRAS is present and the Windows version or installed patches do not meet the fixed build numbers listed in the affected version ranges.

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-30022 to affected Windows systems. If patching is not immediately feasible, consider disabling RRAS if not required, or implementing network segmentation to limit exposure.

Recommended fix High confidence

Upgrade to the May 2024 Windows Security Update (or later) which addresses CVE-2024-30022 - specific build numbers vary by Windows version as listed in affected versions

  1. Install the latest Windows security update that addresses CVE-2024-30022. On affected systems, apply the May 2024 or later Windows Security Update via Windows Update, WSUS, or Microsoft Update Catalog.
  2. Alternatively, download and install the appropriate security update for your Windows version from the Microsoft Update Catalog (search for CVE-2024-30022).
  3. After installation, verify the system build matches or exceeds the fixed version: 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.
  4. If RRAS is not required, consider disabling the Routing and Remote Access service as a defense-in-depth measure until the update can be applied.
Caveat Standard Windows security update - minimal risk; ensure backup of critical data before applying updates as with any system update

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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