dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-29832

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
Out-of-bounds read 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 · moderate confidence

CVE-2025-29832 is an out-of-bounds read vulnerability in Windows Routing and Remote Access Service (RRAS). The flaw allows an unauthenticated remote attacker to read memory beyond allocated buffer boundaries, potentially exposing sensitive information. The CVSS 6.5 indicates network-based exploitability with low complexity and no authentication required.

MitigationApply the appropriate Microsoft Windows security update for RRAS. If immediate patching is not possible, restrict network access to RRAS servers and disable RRAS if not required.

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 if RRAS is installed on the system
    Run PowerShell command: Get-WindowsOptionalFeature -Online -FeatureName RemoteAccess | Select-Object -Property State. Alternatively, check via Server Manager > Add Roles and Features > Remote Access, or review installed Windows features list.
    Affected if RRAS is installed (State = Enabled or the feature is present)
  2. Confirm RRAS service status
    Open Services console (services.msc) and locate 'Routing and Remote Access' service, or run: Get-Service -Name RemoteAccess in PowerShell.
    Affected if The RemoteAccess service is running or set to start automatically (vulnerability is remotely exploitable only when RRAS is active)
  3. Determine installed Windows version and build number
    Run winver to see version and build, or use: systeminfo | findstr /B /C:"OS Name" /C:"OS Version". For precise build, query: reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuildNumber
    Affected if Build number falls below the fixed version for your Windows release (see affected version list)
  4. Compare your build against affected ranges
    Cross-reference your detected build number with: 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
    Affected if Your build number is less than the fixed threshold for your specific Windows release

Your system is affected if RRAS is installed and running, AND your Windows version/build is below the corresponding fixed version for your release.

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 appropriate Microsoft Windows security update for RRAS. If immediate patching is not possible, restrict network access to RRAS servers and disable RRAS if not required.

Recommended fix High confidence

Upgrade to: Windows 10 1507 to 10.0.10240.21014, Windows 10 1607 to 10.0.14393.8066, Windows 10 1809 to 10.0.17763.7314, Windows 10 21h2 to 10.0.19044.5854, Windows 10 22h2 to 10.0.19045.5854, Windows 11 22h2 to 10.0.22621.5335, Windows 11 23h2 to 10.0.22631.5335, Windows 11 24h2 to 10.0.26100.4061

  1. Identify the current Windows version by running 'winver' or checking System Properties
  2. Determine which version branch your system is on (e.g., Windows 10 22h2, Windows 11 23h2)
  3. Open Windows Settings and navigate to Windows Update
  4. Click 'Check for updates' and install all available updates
  5. Alternatively, manually download and install the specific cumulative update matching your fixed version from the Microsoft Update Catalog
  6. Restart the system after updates are installed
  7. Verify the installed version matches or exceeds the fixed version (e.g., for Windows 10 22h2, verify version is 10.0.19045.5854 or higher)
  8. Confirm the RRAS service is running properly after the update
Caveat Standard Windows update risks apply - ensure backups exist and test in staging if possible; some updates may require restart and may affect dependent services

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
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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