dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-29830

MEDIUM · 6.5 CVSS v3.1 Published 2025-05-13
Fix available
A fix is available. Upgrade to 10.0.10240.21014 / 10.0.14393.8066 or later.
See remediation →
72/100
Remediation priority · Elevated
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
Use of uninitialized resource in Windows Routing and Remote Access Service (RRAS) allows an unauthorized attacker to disclose information over a network.

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 · high confidence

CVE-2025-29830 is an information disclosure vulnerability in Windows Routing and Remote Access Service (RRAS) caused by use of an uninitialized resource. An unauthorized remote attacker can exploit this to disclose sensitive information from the affected system. The vulnerability affects Windows servers running RRAS and is rated medium severity (CVSS 6.5).

MitigationApply the Microsoft security update for CVE-2025-29830 to all affected Windows servers running RRAS. Prioritize internet-facing RRAS servers given the network-based attack vector.

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.21014
Windows 10 1607Operating system
Affected:< 10.0.14393.8066
Windows 10 1809Operating system
Affected:< 10.0.17763.7314
Windows 10 21h2Operating system
Affected:< 10.0.19044.5854
Windows 10 22h2Operating system
Affected:< 10.0.19045.5854
Windows 11 22h2Operating system
Affected:< 10.0.22621.5335
Windows 11 23h2Operating system
Affected:< 10.0.22631.5335
Windows 11 24h2Operating system
Affected:< 10.0.26100.4061

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

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
    Open Server Manager > Add Roles and Features, or run 'Get-WindowsFeature -Name Routing' in PowerShell on Server OS. On desktop Windows, check Services console for 'Routing and Remote Access' service entry.
    Affected if The RRAS role/service is present on the system
  2. Confirm RRAS service status
    Run 'Get-Service RemoteAccess' in PowerShell or check the RemoteAccess/Routing and Remote Access service in Services.msc. Look for StartType that is not Disabled.
    Affected if The RRAS service is installed and not explicitly disabled (vulnerability requires the service to be present)
  3. Check Windows version
    Run 'winver' from Run dialog, or run '[System.Environment]::OSVersion.Version' or 'Get-ComputerInfo | Select-Object WindowsVersion' in PowerShell.
    Affected if The installed Windows version falls within the affected ranges: Windows 10 1507 < 10.0.10240.21014, 1607 < 10.0.14393.8066, 1809 < 10.0.17763.7314, 21h2 < 10.0.19044.5854, 22h2 < 10.0.19045.5854; Windows 11 22h2 < 10.0.22621.5335, 23h2 < 10.0.22631.5335, 24h2 < 10.0.26100.4061
  4. Verify RRAS is configured for network access
    Open Routing and Remote Access console (rrasmgmt.msc) if available, or check registry under HKLM\System\CurrentControlSet\Services\RemoteAccess\Parameters for configured interfaces. An attacker would need network access to the RRAS service.
    Affected if RRAS is configured to accept remote connections or routing is enabled on any interface

A system is affected if it runs a vulnerable Windows version listed above AND has RRAS installed/enabled, regardless of whether it is currently accepting connections.

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.21014 / 10.0.14393.8066 / 10.0.17763.7314 or later
Fixed in 10.0.10240.2101410.0.14393.806610.0.17763.7314
Interim mitigation

Apply the Microsoft security update for CVE-2025-29830 to all affected Windows servers running RRAS. Prioritize internet-facing RRAS servers given the network-based attack vector.

Recommended fix High confidence
  1. Open Settings > Update & Security > Windows Update
  2. Click 'Check for updates' to retrieve the latest security updates
  3. Look for and install the security update containing CVE-2025-29830 (Windows Routing and Remote Access Service security update)
  4. Restart the system if prompted to complete the installation
  5. Verify the update was installed by checking Windows Update history

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
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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