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

# Escenario - Fuga de información (BlockyCore.jar)

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

**Enumeración de directorios con Gobuster:**

Utilice **Gobuster** para enumerar directorios en el servidor web objetivo.

```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/7cc93fe4f93072328191887e255fd2baf7ebe62c" alt=""><figcaption></figcaption></figure>

Un directorio llamado **plugins** es descubierto.

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

**Descargar y extraer BlockyCore.jar:**

Descargar **BlockyCore.jar**, que parece ser un complemento personalizado, y luego extráelo.

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

#### Descompilando BlockyCore.class

El contenido extraído incluye **BlockyCore.class**. Descompílalo con **javap** para inspeccionar el contenido.

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

Se encuentra un conjunto de credenciales de base de datos:

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

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

#### Acceso a la base de datos mediante phpMyAdmin

Usando las credenciales extraídas, inicia sesión en **phpMyAdmin** y encuentra una tabla de la base de datos que contiene al usuario **notch**.

<figure><img src="/files/b0ebbd5b99ab16e451c45bf9461a41917d5d2701" 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/es/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.
