dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2025-62473

MEDIUM · 6.5 CVSS v3.1 Published 2025-12-09
Fix available
A fix is available. Upgrade to 10.0.14393.8688 / 10.0.17763.8146 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
Buffer over-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

A buffer over-read vulnerability exists in Windows Routing and Remote Access Service (RRAS) that allows an unauthenticated attacker to read memory contents beyond allocated buffers, potentially exposing sensitive information. The flaw is network-exploitable against systems with RRAS enabled.

MitigationApply the relevant Microsoft security update for this CVE to the affected Windows servers running RRAS. If immediate patching is not possible, consider restricting network access to RRAS services or disabling 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 1607Operating system
Affected:< 10.0.14393.8688
Windows 10 1809Operating system
Affected:< 10.0.17763.8146
Windows 10 21h2Operating system
Affected:< 10.0.19044.6691
Windows 10 22h2Operating system
Affected:< 10.0.19045.6691
Windows 11 23h2Operating system
Affected:< 10.0.22631.6345
Windows 11 24h2Operating system
Affected:< 10.0.26100.7392
Windows 11 25h2Operating system
Affected:< 10.0.26200.7392
Windows Server 2008Operating system
Affected:all versions= r2

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. Confirm RRAS is enabled
    Check the RemoteAccess service start type via Registry: reg query 'HKLM\SYSTEM\CurrentControlSet\Services\RemoteAccess' /v Start. A value of 2 means disabled, 3 means auto-start (enabled).
    Affected if The Start value is 3 (auto-start) or the RRAS service is running.
  2. Check Windows build number
    Run 'winver' or 'systeminfo' and note the build number displayed (for example, 19045 for Windows 10 22h2).
    Affected if The build number falls below the affected threshold for your Windows version branch.
  3. Identify exact Windows version and compare
    Run 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v BuildLabEx' to get the full version string, then map to the affected product list.
    Affected if The version matches any of the affected products listed with a version lower than the fixed threshold.
  4. Verify RRAS service status
    Run 'sc query RemoteAccess' to confirm the service state. Also run 'netsh routing ip show status' if available to confirm RRAS functionality is active.
    Affected if The RemoteAccess service shows STATE: RUNNING.

You are affected if RRAS is enabled/running AND your Windows version/build falls within any of the affected ranges listed for this CVE.

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.14393.8688 / 10.0.17763.8146 / 10.0.19044.6691 or later
Fixed in 10.0.14393.868810.0.17763.814610.0.19044.6691
Interim mitigation

Apply the relevant Microsoft security update for this CVE to the affected Windows servers running RRAS. If immediate patching is not possible, consider restricting network access to RRAS services or disabling RRAS if not required.

Recommended fix High confidence

Windows 10: upgrade to version 1607 (10.0.14393.8688), 1809 (10.0.17763.8146), 21h2 (10.0.19044.6691), or 22h2 (10.0.19045.6691) respectively | Windows 11: upgrade to 23h2 (10.0.22631.6345), 24h2 (10.0.26100.7392), or 25h2 (10.0.26200.7392) respectively | Windows Server 2008/R2: migrate to supported

  1. Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine if RRAS (Routing and Remote Access Service) is enabled by opening 'Routing and Remote Access' in Server Manager or running 'netsh routing ip status'
  3. For Windows 10/11 systems: Apply the relevant Windows security update from Microsoft Update Catalog or WSUS that addresses CVE-2025-62473 (typically released in a monthly security patch)
  4. For Windows Server systems: Apply the relevant Windows Server security update from Microsoft Update Catalog or WSUS
  5. Verify the update was installed successfully by checking Windows Update history for the security patch
  6. Restart the system if prompted to complete the installation
  7. For Windows Server 2008/R2: Since these versions are end-of-life with no security updates, migrate to a supported Windows Server version (2016 or later recommended)
Caveat Windows Server 2008/R2 has no security patches available - requires OS migration; minor risk of service interruption from patch installation requiring reboot

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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