> 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/ja/privesc/capabilities/python-capabilities.md).
# Python Capabilities
cap\_setuid と GTFOBins のペイロードを通じた Linux 権限昇格のための Python capability 悪用。
Linuxのケーパビリティは、root権限を細かな権利に分割し、バイナリに割り当てられるようにします。危険なケーパビリティとしては `cap_setuid+ep`, `cap_dac_read_search+ep`、またはファイル書き込みのケーパビリティは、通常のユーザー制限を回避できます。
## 手法
* ファイルのケーパビリティを列挙し、危険な権限ビットを持つバイナリを特定します。
* GTFOBinsや各言語固有のペイロードを確認し、シェル、読み取り、書き込み、またはsetuidの悪用を探します。
* rootシェルを試す前に、最小限の検証コマンドを優先します。
## クイックチェック
```bash
getcap -r / 2>/dev/null
```
:user-lock:
Python 3.8 の機能
Linux の権限昇格に関する機能（Python3.8）のノート。列挙手順、悪用例、レポート重視の検証を含みます。
---
# 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/ja/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.