> 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/network-admin-panel-cms-exploitation.md).
# Panel de administración de red
Notas de explotación del panel de administración de red para captura de callbacks LDAP, abuso de print.return.local, divulgación de credenciales, validación WinRM y acceso con evil-winrm.
La configuración del puerto 80 revela una configuración del servidor que apunta a `print.return.local` a través del puerto 389.
**Escuchando en el puerto 389**/ Lugar `netcat` en modo escucha en el puerto 389:
```bash
nc -nlvp 389
```
* Se recibe una conexión, revelando credenciales para `svc-printer` con la contraseña `1edFg43012!!`.
**Validación de credenciales con WinRM**
Con el puerto 5985 de WinRM abierto, valida las credenciales con `crackmapexec`:
```bash
crackmapexec winrm 10.10.11.108 -u 'svc-printer' -p '1edFg43012!!'
```
* El `comprometido` la respuesta confirma credenciales válidas.
**Inicio de sesión en Evil-WinRM**
Use `evil-winrm` para obtener una shell como `svc-printer`:
---
# 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/es/cms/network-admin-panel-cms-exploitation.md?ask=&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.
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)