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

# Cenário - Vazamento de Informação (BlockyCore.jar)

<figure><img src="/files/bf2d03f55cff53505ce83ed822ce567cb97e6b43" alt=""><figcaption></figcaption></figure>

**Enumeração de diretórios com o Gobuster:**

Use **Gobuster** para enumerar diretórios no servidor web alvo.

```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="/files/118d1d1692d227632018444710d64477939867dd" alt=""><figcaption></figcaption></figure>

Um diretório chamado **plugins** é descoberto.

<figure><img src="/files/9736105b0df3f698e34ede7319889125dbff37a1" alt=""><figcaption></figcaption></figure>

**Baixe e extraia o BlockyCore.jar:**

Baixar **BlockyCore.jar**, que parece ser um plugin personalizado, e então extraia-o.

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

#### Descompilando BlockyCore.class

O conteúdo extraído inclui **BlockyCore.class**. Descompile-o com **javap** para inspecionar o conteúdo.

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

Um conjunto de credenciais do banco de dados é encontrado:

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

<figure><img src="/files/8e28c9a191d9b86bee0b9fdab01fc28eabdcaca3" alt=""><figcaption></figcaption></figure>

#### Acesso ao banco de dados via phpMyAdmin

Usando as credenciais extraídas, faça login em **phpMyAdmin** e encontre uma tabela do banco de dados contendo o usuário **notch**.

<figure><img src="/files/704afcda8c618e32c01db2a60b3c15596b863c75" 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://hacking-notes.jord4n.pro/pt-br/cms/wordpress-cms-exploitation/situation-information-leakage-blockycore.jar.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
