> 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/websockets.md).

# WebSocket

WebSocketテスト、メッセージ操作、ハンドシェイク悪用、クロスサイトWebSocketハイジャック、リアルタイムアプリケーション攻撃。

PortSwigger Web Security Academy のラボ向け WebSockets ノート。実践的なテスト手順、Burp Suite による検証、ペイロードの挙動、エクスプロイトのワークフローに重点を置いています。

## テスト手順

1. 脆弱な機能と、関連するリクエスト、パラメータ、ヘッダー、Cookie、またはブラウザー側の Sink を特定します。
2. 攻撃を拡大する前に、最小限のペイロードで Burp Suite 上で挙動を再現します。
3. アカウントアクセス、データ漏えい、コード実行、SSRF、または状態変更など、明確な PoC で影響を確認します。
4. 侵入の経路を文書化しながら、ペイロード、URL、トークン、ラボの認証情報は変更しないでください。

## ラボ

<table><thead><tr><th data-type="content-ref"></th></tr></thead><tbody><tr><td><a href="/ja/web/websockets/cross-site-websocket-hijacking.md">クロスサイトWebSocketハイジャック</a></td></tr><tr><td><a href="/ja/web/websockets/websocket-handshake-manipulation.md">WebSocketハンドシェイク操作</a></td></tr><tr><td><a href="/ja/web/websockets/websocket-message-manipulation.md">WebSocketメッセージ操作</a></td></tr></tbody></table>


---

# 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/websockets.md?ask=<question>&goal=<user_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.
