> 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 权限提升

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 %}

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-c85d645312425f2066339222d0c88a04d34a92e8%2Fimage%20(1141).png?alt=media" alt=""><figcaption></figcaption></figure>

**搜索 GTFOBins 技巧：**

* 查阅 GTFOBins 后，我们发现 `journalctl` 可通过启动 shell 命令来提升权限。

{% embed url="<https://gtfobins.github.io/gtfobins/journalctl/>" %}

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-c538ffed75cd2cf69914bc74acb001c051bd943a%2F%7B8538B02D-B4A2-4564-8B19-6F13D68A4D62%7D.png?alt=media" alt=""><figcaption></figcaption></figure>

**实施条件：**

要触发此操作，终端窗口大小必须受限，以启用 `less` 中的分页模式 `journalctl`。此模式允许通过 `!`.

```bash
/usr/bin/sudo /usr/bin/journalctl -n5 -unostromo.service
```

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-412b84580d5e82a85cb399f39e5d6c6173c243f9%2Fimage%20(1142).png?alt=media" alt=""><figcaption></figcaption></figure>

一旦处于 `less` 模式下，输入以下命令即可获得 root shell：

```bash
!/bin/sh
```

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-0f99f5c62600d4373730c20c8f04620c369c6ee9%2Fimage%20(1143).png?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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/privesc/sudoers/sudo-journalctl-linux-privilege-escalation.md?ask=<question>&goal=<user_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.
