> 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-in-error-messages.md).
# Information Disclosure in Error Messages
Information Disclosure in Error Messages notes for PortSwigger Web Security Academy labs, including exploitation workflow, payload testing, Burp Suite validation, and remediation context.
### Information Disclosure in Error Messages
**Lab objective**
This lab is based on too verbose \*\* error messages\*\* which reveal sensitive information about the application. / The objective is to identify and submit the version of a vulnerable third party framework\*\* used by the server.
**Observation initiale**
By manipulating the `productId` parameter with a non-existent value, for example:
```bash
/product?productId=ufeenu
```
The application returns a **detailed error page** instead of a generic message.
**Disclosed information**
The error message explicitly sets out internal details of the application, including the framework used and its exact version.
In this case, the error reveals that the application works with:
```bash
Apache Struts 2 2.3.31
```
---
# 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-in-error-messages.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)