> 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/zh/web/information-disclosure/information-disclosure-on-a-debug-page.md).

# 调试页面上的信息泄露

调试页面上的信息泄露，PortSwigger Web Security Academy 实验笔记，包括利用流程、载荷测试、Burp Suite 验证以及修复上下文。

### 调试页面上的信息泄露

**实验描述**

此实验包含一个会泄露有关应用程序敏感信息的调试页面。/ 目标是识别并提交环境变量 **SECRET/ 密钥**.

**初步观察**

通过拦截 HTTP 请求，我们看到发送了一个 **GET** 包含与套接字密钥相关参数的查询。/ 这表明存在暴露的调试或诊断机制。

**使用 Burp Suite 进行分析**

* 通过查看 **站点地图** 在 Burp Suite 中，识别出了一个敏感页面。
* 一个 **phpinfo** 页面可访问，这构成了严重的信息泄露。

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-2cd2f955a9f4a52866ad4195d4087e8726534d57%2Fimage%20(197).png?alt=media" alt=""><figcaption></figcaption></figure>

**易受攻击的资源**

已识别路径：

```bash
/cgi-bin/phpinfo.php
```

该页面显示了 PHP 的完整配置，包括环境变量。

**泄露的敏感数据**

在 `phpinfo.php` 页面中，显示了以下变量：

* **SECRET/\_KEY** :

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-77922536c7bcc4679c20fda8d4159e12fab0fe29%2Fimage%20(198).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/zh/web/information-disclosure/information-disclosure-on-a-debug-page.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.
