> 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/cms/wordpress-cms-exploitation/situation-information-leakage-blockycore.jar.md).

# シナリオ - 情報漏えい（BlockyCore.jar）

BlockyCore.jarの抽出と認証情報発見を通じたWordPressプラグインの情報漏えい。

<figure><img src="https://2001299964-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-c35cf77902efc22544732dc8091974f1f117fcd0%2F%7BFFA085C0-2D66-45F3-9B65-AEC3E396A7E2%7D.png?alt=media" alt=""><figcaption></figcaption></figure>

**Gobusterによるディレクトリ列挙：**

使用する **Gobuster** 対象Webサーバー上のディレクトリを列挙するため。

```bash
gobuster dir -u http://blocky.htb/ -w /usr/share/SecLists/Discovery/Web-Content/directory-list-2.3-medium.txt -t 100
```

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

という名前のディレクトリが **plugins** 見つかる。

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

**BlockyCore.jarをダウンロードして展開：**

ダウンロード **BlockyCore.jar**はカスタムプラグインと思われるので、その後展開する。

```java
jar xf BlockyCore.jar
```

#### BlockyCore.classの逆コンパイル

展開された内容には **BlockyCore.class**が含まれている。これを **javap** で逆コンパイルして内容を確認する。

```bash
javap -c BlockyCore.class
```

データベースの認証情報一式が見つかる：

* **localhost**
* **root**
* **8YsqfCTnvxAUeduzjNSXe22**

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

#### phpMyAdminを介したデータベースアクセス

抽出した認証情報を使って、 **phpMyAdmin** にログインし、ユーザーを含むデータベーステーブルを見つける **notch**.

<figure><img src="https://2001299964-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-fb82b983e143790f21a074cad53874753b755438%2Fimage%20(960).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/cms/wordpress-cms-exploitation/situation-information-leakage-blockycore.jar.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.
