> 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/web/information-disclosure/information-disclosure-on-a-debug-page.md).
# Information Disclosure on a Debug Page
Information Disclosure on a Debug Page notes for PortSwigger Web Security Academy labs, including exploitation workflow, payload testing, Burp Suite validation, and remediation context.
### Information Disclosure on Debug Page
**Description of lab**
This lab contains a debugging page that discloses sensitive information about the application. / The objective is to identify and submit the environment variable **SECRET/ KEY**.
**Observation initiale**
By intercepting HTTP requests, we see the sending of a **GET** query containing a socket key -related parameter. / This indicates the presence of exposed debugging or diagnostic mechanisms.
**Analysis with Burp Suite**
* By exploring the **Map Site** of Burp Suite, a sensitive page is identified.
* A **phpinfo** page is accessible, which is a critical information leak.
**Vulnerable resource**
Path identified:
```bash
/cgi-bin/phpinfo.php
```
This page displays the full configuration of PHP, including environment variables.
**Disclosed sensitive data**
On the `phpinfo.php` page, the following variable is displayed:
* **SECRET/\_KEY** :
---
# 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/web/information-disclosure/information-disclosure-on-a-debug-page.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)