dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 3 May 2022. Known ransomware use
Windows 7Operating system · Microsoft

CVE-2019-0708

CRITICAL · 9.8 CVSS v3.1 Published 2019-05-16
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
In the wild Ransomware High EPSS Public exploit Remotely reachable No privileges Zero-click Patch available

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
A remote code execution vulnerability exists in Remote Desktop Services formerly known as Terminal Services when an unauthenticated attacker connects to the target system using RDP and sends specially crafted requests, aka 'Remote Desktop Services Remote Code Execution Vulnerability'.

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

This is a pre-authentication remote code execution vulnerability in Microsoft Remote Desktop Services (RDS). An unauthenticated attacker can send specially crafted RDP packets to achieve arbitrary code execution on the target system without any user interaction or credentials, making it wormable.

MitigationApply the Microsoft security patches (KB4499175 for Windows 7/Server 2008 R2 and newer), enable Network Level Authentication (NLA) as an interim control, or block RDP port 3389 at the perimeter firewall if RDP is 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 7Operating system
Affected:all versions
Windows Server 2008Operating system
Affected:all versions= r2
Axiom Multix M FirmwareOperating system
Affected:all versions
Axiom Vertix Md Trauma FirmwareOperating system
Affected:all versions
Axiom Vertix Solitaire M FirmwareOperating system
Affected:all versions
Mobilett Xp Digital FirmwareOperating system
Affected:all versions
Multix Pro Acss P FirmwareOperating system
Affected:all versions
Multix Pro P FirmwareOperating system
Affected:all versions

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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. Confirm Windows version is affected
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to identify the Windows edition and version
    Affected if The version is Windows 7 (any build) or Windows Server 2008/2008 R2 (any build)
  2. Verify Remote Desktop Services is enabled
    Check the registry key HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\fDenyTSConnections (value 0 means RDP is enabled), or check if the Remote Desktop Services service (TermService) is running
    Affected if fDenyTSConnections is set to 0 or the TermService service is running - RDP is active and the system is potentially vulnerable
  3. Check Network Level Authentication status
    Run 'reg query "HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp" /v UserAuthentication' - a value of 1 means NLA is enabled
    Affected if UserAuthentication is set to 0 - NLA is disabled and the system is fully vulnerable to pre-authentication exploitation
  4. For Siemens medical devices, confirm firmware version
    Access the device management interface or check system information to identify the firmware version of Axiom Multix M, Axiom Vertix Md Trauma, Axiom Vertix Solitaire M, Mobilett Xp Digital, Multix Pro Acss P, or Multix Pro P
    Affected if The device runs any firmware version (all versions of these Siemens products are affected)
  5. Verify patch installation status
    Run 'wmic qfe list' or check 'Get-HotFix' in PowerShell to list installed security updates - look for May 2019 security updates such as KB4499175 (Windows 7/Server 2008 R2)
    Affected if The May 2019 security updates are NOT installed - the system lacks the BlueKeep vulnerability fix

A system is affected if it runs Windows 7 or Windows Server 2008/2008 R2 (or is one of the listed Siemens devices) AND has Remote Desktop Services enabled, especially without NLA protection or the May 2019 security patches.

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
Patch available Apply the vendor patch
Vendor patch portal.msrc.microsoft.com →
Interim mitigation

Apply the Microsoft security patches (KB4499175 for Windows 7/Server 2008 R2 and newer), enable Network Level Authentication (NLA) as an interim control, or block RDP port 3389 at the perimeter firewall if RDP is not required.

Recommended fix High confidence

Windows 7: Upgrade to Windows 10 or Windows 11 (end of support for Windows 7 was January 2020). Windows Server 2008 R2: Upgrade to Windows Server 2019 or Windows Server 2022.

  1. Install the official Microsoft security update for CVE-2019-0708 (BlueKeep): For Windows 7, install security update KB4490628. For Windows Server 2008 R2, install security update KB4490628. These were released in May 2019.
  2. Verify the update was successfully installed by checking Windows Update history or by reviewing installed updates for the specific KB number.
  3. If RDP is not required, disable Remote Desktop Services on affected systems via Control Panel > System and Security > System > Remote settings, or via PowerShell: Set-ItemProperty -Path 'HKLM:\System\CurrentControlSet\Control\Terminal Server' -Name 'fDenyTSConnections' -Value 1
  4. Ensure network-level authentication (NLA) is enabled as an interim mitigation: Go to Computer Policy > Administrative Templates > Windows Components > Remote Desktop Services > Security, enable 'Require user authentication for remote connections by using NLA'.
  5. Apply to all affected systems in your environment - this vulnerability is wormable and can spread autonomously.
Caveat Windows 7 extended support ended in January 2020 - no security updates available. Windows Server 2008 R2 mainstream support ended in 2020, extended support continues to 2029 but requires separate subscription. Some legacy applications may not be compatible with newer OS versions.

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

Fix this in Windows 7 Exploited in the wild — priority engagement
  • Consultation12.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,200
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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