dbcve.org
Windows Server 2008Operating system · Microsoft

CVE-2025-50157

MEDIUM · 5.7 CVSS v3.1 Published 2025-08-12
Fix available
A fix is available. Upgrade to 10.0.14393.8330 / 10.0.17763.7678 or later.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable

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 authorized 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

Windows Routing and Remote Access Service (RRAS) uses an uninitialized resource, allowing an authorized attacker to potentially read memory contents and disclose information over a network. This is a memory safety flaw where data is not properly initialized before being accessed or returned to the caller.

MitigationApply the Microsoft security update for this CVE through Windows Update or manual patch deployment. If RRAS is not required, disable the service. Restrict network access to RRAS to authorized personnel only as a defense-in-depth measure.

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 Server 2008Operating system
Affected:all versions= r2
Windows Server 2012Operating system
Affected:all versions= r2
Windows Server 2016Operating system
Affected:< 10.0.14393.8330
Windows Server 2019Operating system
Affected:< 10.0.17763.7678
Windows Server 2022Operating system
Affected:< 10.0.20348.3989
Windows Server 2022 23h2Operating system
Affected:< 10.0.25398.1791
Windows Server 2025Operating system
Affected:< 10.0.26100.4851

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
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 installed
    Open Server Manager, navigate to 'Add Roles and Features', or run 'Get-WindowsFeature -Name RemoteAccess' in PowerShell to check if the Remote Access role (which includes RRAS) is installed.
    Affected if Remote Access role with RRAS is installed on the server.
  2. Verify RRAS service status
    Open Services console (services.msc) or run 'Get-Service RemoteAccess' in PowerShell to check if the RemoteAccess service is running.
    Affected if The RemoteAccess service is running or set to start automatically.
  3. Check Windows Server build version
    Run 'winver' from command prompt, or run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' or check the registry key 'HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion' to obtain the full build number.
    Affected if The build number is lower than 10.0.14393.8330 (Server 2016), 10.0.17763.7678 (Server 2019), 10.0.20348.3989 (Server 2022), 10.0.25398.1791 (Server 2022 23h2), or 10.0.26100.4851 (Server 2025); or if running Server 2008/2012 any version.
  4. Identify RRAS configuration state
    Open Routing and Remote Access console (rrasmgmt.msc) or check registry under 'HKLM\SYSTEM\CurrentControlSet\Services\RemoteAccess\Parameters' to see if RRAS is configured with any routing or remote access features.
    Affected if RRAS is configured with any routing interfaces, VPN, or dial-in settings.

The server is affected if RRAS (RemoteAccess service) is installed and running on a Windows Server version below the fixed build numbers listed in the CVE, as the uninitialized resource flaw only applies when RRAS is present and active.

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.8330 / 10.0.17763.7678 / 10.0.20348.3989 or later
Fixed in 10.0.14393.833010.0.17763.767810.0.20348.3989
Interim mitigation

Apply the Microsoft security update for this CVE through Windows Update or manual patch deployment. If RRAS is not required, disable the service. Restrict network access to RRAS to authorized personnel only as a defense-in-depth measure.

Recommended fix High confidence

Windows Server 2016 to 10.0.14393.8330+; Windows Server 2019 to 10.0.17763.7678+; Windows Server 2022 to 10.0.20348.3989+; Windows Server 2022 23h2 to 10.0.25398.1791+; Windows Server 2025 to 10.0.26100.4851+

  1. Obtain the latest Windows Update for your Windows Server version from Microsoft Update Catalog or WSUS
  2. For Windows Server 2016: Install build 10.0.14393.8330 or later via Windows Update
  3. For Windows Server 2019: Install build 10.0.17763.7678 or later via Windows Update
  4. For Windows Server 2022: Install build 10.0.20348.3989 or later via Windows Update
  5. For Windows Server 2022 23h2: Install build 10.0.25398.1791 or later via Windows Update
  6. For Windows Server 2025: Install build 10.0.26100.4851 or later via Windows Update
  7. For Windows Server 2008/2012 (all versions): These are end-of-life and receive no patches; disable RRAS if not needed, or isolate on network
  8. Verify the installed build matches or exceeds the target version using 'winver' or 'systeminfo'
Caveat Windows Server 2008 and 2012 have no supported upgrade path (EOL); RRAS should be disabled if not needed on legacy systems

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

Fix this in Windows Server 2008 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-50157 — 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-50157 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