> 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/capabilities/python-capabilities.md). # Python Capabilities Python capability abuse for Linux privilege escalation through cap\_setuid and GTFOBins payloads. Linux capabilities split root privileges into granular rights that can be assigned to binaries. Dangerous capabilities such as `cap_setuid+ep`, `cap_dac_read_search+ep`, or file write capabilities can bypass normal user restrictions. ## Methodology * Enumerate file capabilities and identify binaries with dangerous privilege bits. * Check GTFOBins and language-specific payloads for shell, read, write, or setuid abuse. * Prefer minimal validation commands before attempting a root shell. ## Quick Checks ```bash getcap -r / 2>/dev/null ```

:user-lock:

Python 3.8 Capabilities

Capabilities (Python3.8) notes for Linux privilege escalation, with enumeration steps, exploitation examples, and reporting-focused validation.Capabilities (Python3.8) - Linux Privilege Escalation

:user-lock:

Python 3.10 Capabilities

Capabilities (Python3.10) notes for Linux privilege escalation, with enumeration steps, exploitation examples, and reporting-focused validation.Capabilities (Python3.10) - Linux Privilege Escalation
--- # 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/capabilities/python-capabilities.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.