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

# Scénario - Fuite d’informations (BlockyCore.jar)

<figure><img src="/files/3b4edb093949613aebed7811a6d6ee5778a0b91e" alt=""><figcaption></figcaption></figure>

**Énumération des répertoires avec Gobuster :**

Utilisez **Gobuster** pour énumérer les répertoires sur le serveur web cible.

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

Un répertoire nommé **plugins** est découvert.

<figure><img src="/files/93390a909ec666b0527ae906ecffb9f2d7bdc059" alt=""><figcaption></figcaption></figure>

**Télécharger et extraire BlockyCore.jar :**

Télécharger **BlockyCore.jar**, qui semble être un plugin personnalisé, puis extrayez-le.

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

#### Décompilation de BlockyCore.class

Le contenu extrait inclut **BlockyCore.class**. Décompilez-le avec **javap** pour inspecter le contenu.

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

Un ensemble d'identifiants de base de données est trouvé :

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

<figure><img src="/files/2af0348b6f3adadbddf7d65756736698a69c1fbc" alt=""><figcaption></figcaption></figure>

#### Accès à la base de données via phpMyAdmin

En utilisant les identifiants extraits, connectez-vous à **phpMyAdmin** et trouvez une table de base de données contenant l'utilisateur **notch**.

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