> 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-version-vulnerabilities-linux-privilege-escalation.md).

# Sudo 版本漏洞 - Linux 权限提升

关于 CVE-2019-14287 和 CVE-2025-32463 的 sudo 版本漏洞 Linux 权限提升笔记。

sudoers 权限提升始于用户可以通过……运行的命令 `sudo`. 配置错误的二进制文件、不安全的脚本参数、符号链接处理以及存在漏洞的 sudo 版本，都可能将有限的 sudo 权限转化为 root shell。

## 方法

* 运行 `sudo -l` 并记录每个允许的命令、目标用户和 NOPASSWD 规则。
* 在 GTFOBins 中检查 shell 逃逸、文件写入以及由参数控制的执行。
* 检查脚本中的可写路径、符号链接处理、通配符展开以及缺失的文件引用。
* 检查 `sudo --version` 当路径依赖于已知的 sudo CVE 时。

## 快速检查

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

<table data-view="cards" data-full-width="false" data-search="false"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h3><i class="fa-user-lock" style="color:$primary;">:user-lock:</i></h3></td><td><h4>sudo 1.8.27 CVE-2019-14287</h4></td><td>sudo 1.8.27 [CVE-2019-14287] Linux 提权笔记，包含枚举步骤、利用示例以及面向报告的验证。</td><td><a href="/zh/privesc/sudoers/sudo-version-vulnerabilities-linux-privilege-escalation/sudo-version-1.8.27-cve-2019-14287.md">sudo 1.8.27 CVE-2019-14287</a></td></tr><tr><td><h3><i class="fa-user-lock" style="color:$primary;">:user-lock:</i></h3></td><td><h4>sudo 1.9.17 CVE-2025-32463</h4></td><td>sudo 1.9.17 [CVE-2025-32463] Linux 提权笔记，包含枚举步骤、利用示例以及面向报告的验证。</td><td><a href="/zh/privesc/sudoers/sudo-version-vulnerabilities-linux-privilege-escalation/sudo-version-1.9.17-cve-2025-32463.md">sudo 1.9.17 CVE-2025-32463</a></td></tr></tbody></table>


---

# 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-version-vulnerabilities-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.