dbcve.org
Windows Server 2012Operating system · Microsoft

CVE-2025-30394

MEDIUM · 5.9 CVSS v3.1 Published 2025-05-13
Fix available
A fix is available. Upgrade to 10.0.14393.8066 / 10.0.17763.7314 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
Sensitive data storage in improperly locked memory in Remote Desktop Gateway Service allows an unauthorized attacker to deny service 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

This vulnerability in Remote Desktop Gateway Service involves sensitive data being stored in improperly locked memory, which can be exploited by an unauthorized network attacker to cause a denial of service condition.

MitigationApply the Microsoft security update for CVE-2025-30394 when available, and ensure Remote Desktop Gateway services are not exposed directly to untrusted networks.

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 2012Operating system
Affected:all versions= r2
Windows Server 2016Operating system
Affected:< 10.0.14393.8066
Windows Server 2019Operating system
Affected:< 10.0.17763.7314
Windows Server 2022Operating system
Affected:< 10.0.20348.3692
Windows Server 2022 23h2Operating system
Affected:< 10.0.25398.1611
Windows Server 2025Operating 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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/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. Identify Windows Server version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to obtain the exact Windows Server build number
    Affected if The build number falls within any of the affected ranges: Server 2016 < 10.0.14393.8066, Server 2019 < 10.0.17763.7314, Server 2022 < 10.0.20348.3692, Server 2022 23h2 < 10.0.25398.1611, Server 2025 < 10.0.26100.4061, or is Server 2012/R2 (all versions)
  2. Confirm Remote Desktop Gateway is installed
    Open Services.msc or run 'Get-Service -Name UiPath' - actually check via 'Get-Service' for 'Remote Desktop Gateway' service name, or check for Rdgws.dll presence in system
    Affected if The Remote Desktop Gateway service (RdGateway) is present on the system
  3. Verify Remote Desktop Gateway service status
    Run 'Get-Service -Name RemoteDesktopGatewayServices' or check service 'Remote Desktop Gateway' in Services list to see if it is running or set to start
    Affected if The Remote Desktop Gateway service is installed and enabled (running or set to auto-start)
  4. Check network exposure of RD Gateway
    Review firewall rules and network configuration to determine if TCP port 443 (default RD Gateway port) is open to untrusted networks, or run 'netsh advfirewall firewall show rule name=all' and search for RemoteDesktopGateway rules
    Affected if The RD Gateway service port (typically 443) is accessible from untrusted or external networks

A system is likely affected if it runs an affected Windows Server version, has Remote Desktop Gateway installed/enabled, and has the service port exposed to untrusted networks, allowing unauthorized network attackers to trigger the denial of service condition.

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.8066 / 10.0.17763.7314 / 10.0.20348.3692 or later
Fixed in 10.0.14393.806610.0.17763.731410.0.20348.3692
Interim mitigation

Apply the Microsoft security update for CVE-2025-30394 when available, and ensure Remote Desktop Gateway services are not exposed directly to untrusted networks.

Recommended fix High confidence

Upgrade to the minimum fixed build for your respective Windows Server version (e.g., Server 2022 build 10.0.20348.3692 or later)

  1. Identify the current Windows Server version by running 'winver' or 'systeminfo' commands
  2. For Windows Server 2016: Upgrade to build 10.0.14393.8066 or later
  3. For Windows Server 2019: Upgrade to build 10.0.17763.7314 or later
  4. For Windows Server 2022: Upgrade to build 10.0.20348.3692 or later
  5. For Windows Server 2022 23h2: Upgrade to build 10.0.25398.1611 or later
  6. For Windows Server 2025: Upgrade to build 10.0.26100.4061 or later
  7. Apply the corresponding Windows Update or download the specific KB from Microsoft Update Catalog
  8. Reboot the server after applying the update
Caveat Windows Server 2012 and 2012 R2 are end-of-life with no patch available; requires migration to supported Windows Server version

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

Fix this in Windows Server 2012 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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