> 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/daloradius-cms-exploitation.md).
# DaloRADIUS
Enumeración de DaloRADIUS, credenciales predeterminadas, acceso al panel del operador y extracción de hashes sensibles.
**Exploración de directorios con Gobuster:**/ Enumerar directorios web:
```bash
gobuster dir -u http://underpass.htb/daloradius/ -w /usr/share/SecLists/Discovery/Web-Content/directory-list-2.3-medium.txt -t 100
```
Resultado: el **`/app`** directorio es descubierto.
**Enumeración de subdirectorios:**
Enumerando **`/app`** revela:
```bash
gobuster dir -u http://underpass.htb/daloradius/app/ -w /usr/share/SecLists/Discovery/Web-Content/directory-list-2.3-medium.txt -t 100
```
* Un **inicio de sesión de usuario** página.
* Un **inicio de sesión de operador** página.
**Acceso con credenciales predeterminadas de DaloRADIUS:**/ Probar las credenciales RADIUS predeterminadas:
* **Nombre de usuario :** `administrador`
* **Contraseña :** `radius`/ Estas credenciales funcionan en el panel del operador.
### **Extracción de información sensible:**
En el **Administración** sección, recuperar un **nombre de usuario** y **hash de contraseña**:
* **Usuario :** `svcMosh`
* **Hash :** `412DD4759978ACFCC81DEAB01B382403`
---
# 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/daloradius-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)
.png?alt=media)
.png?alt=media)