# Information Disclosure

## Overview

Information disclosure will come in many different types and rank from **Critical-Low.** A lot of them won't lead to direct exploits but they're definitely things adversaries can put in their back pocket to use later&#x20;

## Example 1

<figure><img src="/files/eFwKWFicCa3Kyjf8nWls" alt=""><figcaption><p>Information disclosure via Calender form. Username enumeration was possible through the error</p></figcaption></figure>

<figure><img src="/files/azLdfyJCD57O0TYPEZ9C" alt=""><figcaption><p>Evidence and Remediation</p></figcaption></figure>

## Example 2

{% hint style="info" %}
More for when you're running low on findings and have time to check. Information is information
{% endhint %}

<figure><img src="/files/6fAewf0pdY5vDmLYBfxY" alt=""><figcaption><p>Information disclosure via web server</p></figcaption></figure>

<figure><img src="/files/TXtO7vTTfLLDJWcZ5N8x" alt=""><figcaption><p>Evidence and Remediation</p></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://pnpt.adot8.com/external-pentest-playbook/common-pentest-findings/information-disclosure.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
