> 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/race-condition-attack/race-condition-file-write-pentesting-web.md).

# 競合状態 ファイル書き込み

競合状態 ファイル書き込みに関する、Webアプリケーションのペネトレーションテスト、エクスプロイトのワークフロー、ペイロード検証、影響評価、修正の文脈でのメモ。

ディレクトリを検索するたびに、 **shared-file.txt** ファイルが作成され、次の場所に保存されます：

<figure><img src="https://2001299964-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-3362b7221752f245627af2bc696068845c880702%2FPasted%20image%2020231115224610.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://2001299964-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-2bfcde6932e9d248b5ce6e0e300f95abde8e641f%2FPasted%20image%2020231115224938.png?alt=media" alt=""><figcaption></figcaption></figure>

これが **コード** RaceCondition-file-write の

<figure><img src="https://2001299964-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-ccf3384811e2deb2c3c642d1acc53c7b4a497b0d%2FPasted%20image%2020231115224406.png?alt=media" alt=""><figcaption></figcaption></figure>

1. 私たちは設定する **en リスナーのリクエスト** en、私たちが関心を持つフィールドでフィルタリングして：

```bash
whithe true; do curl -s -X GET 'http://localhost:5000/test' | grep -v "test"; done

```

2. から [Burp Suite](/ja/hacking-tools/web/burpsuite.md)、別のURLに同時に複数のリクエストを送信します：

<figure><img src="https://2001299964-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-02e00fbb8caf4be66b9d3973bc856ab9eeceafa5%2FPasted%20image%2020231115230037.png?alt=media" alt=""><figcaption></figcaption></figure>

3. 時々飽和状態になるため、私たちは **コードを受け取ります** 別のファイルから：

<figure><img src="https://2001299964-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-d54c4e41f4e7866443dc823288f88da57973b7ce%2FPasted%20image%2020231115225958.png?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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/race-condition-attack/race-condition-file-write-pentesting-web.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.
