# CVE-2019-0708: Microsoft Remote Desktop Services Remote Code Execution

> Unauthenticated attackers can execute arbitrary code on Windows systems via specially crafted RDP requests, requiring immediate patching.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 3 Nov 2021 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 May 2019
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-fq64-gmq7-jjvg

## What is CVE-2019-0708?

CVE-2019-0708 is a critical use after free vulnerability in Microsoft Windows 7, published on 16 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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'.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2019-0708?

It affects 67 products.


Products: Huawei Agile Controller-Campus Firmware, Huawei Bh620 V2 Firmware, Huawei Bh621 V2 Firmware, Huawei Bh622 V2 Firmware, Huawei Bh640 V2 Firmware, Huawei Ch121 Firmware, Huawei Ch140 Firmware, Huawei Ch220 Firmware, Huawei Ch221 Firmware, Huawei Ch222 Firmware, Huawei Ch240 Firmware, Huawei Ch242 Firmware, Huawei Ch242 V3 Firmware, Huawei E6000 Chassis Firmware, Huawei E6000 Firmware, Huawei Elog Firmware, Huawei Espace Ecs Firmware, Huawei Gtsoftx3000 Firmware, Huawei Oceanstor 18500 Firmware, Huawei Oceanstor 18800 Firmware and 47 more.

## How do I fix CVE-2019-0708?

No fix has been published for CVE-2019-0708 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 3 May 2022.

## Is CVE-2019-0708 being exploited?

Yes. Attackers have exploited CVE-2019-0708 in the wild since at least 3 Nov 2021, including in ransomware campaigns.

Public exploit code:

- Proof of concept for CVE-2019-0708 (github_poc): https://github.com/Ekultek/BlueKeep
- A quick scanner for the CVE-2019-0708 "BlueKeep" vulnerability. (github_poc): https://github.com/robertdavidgraham/rdpscan
- dump (github_poc): https://github.com/n1xbyte/CVE-2019-0708
- 3389远程桌面代码执行漏洞CVE-2019-0708批量检测工具(Rdpscan Bluekeep Check) (github_poc): https://github.com/k8gege/CVE-2019-0708
- An Attempt to Port BlueKeep PoC from @Ekultek to actual exploits (github_poc): https://github.com/algo7/bluekeep_CVE-2019-0708_poc_to_exploit
- CVE-2019-0708-EXP-Windows版单文件exe版,运行后直接在当前控制台反弹System权限Shell (github_poc): https://github.com/cbwang505/CVE-2019-0708-EXP-Windows

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-0708 and fix it if it is affected.

What it is: CVE-2019-0708 is a critical use after free vulnerability in Microsoft Windows 7, published on 16 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2019-0708 in the wild since at least 3 Nov 2021, including in ransomware campaigns.

Affected product: Microsoft Windows 7. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-0708/ (Markdown: https://insights.sbomify.com/CVE-2019-0708/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-0708
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-0708
- OSV: https://osv.dev/vulnerability/CVE-2019-0708

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-0708/
Summaries are generated and may contain mistakes; the official description above is the record.