01Description
The application returned detailed error messages, including stack traces, framework versions, file paths or database errors, in response to unexpected input.
02Impact
Detailed errors reveal the technologies, versions and internal structure of the application, helping an attacker identify vulnerabilities. Database errors in particular can assist injection attacks.
03Severity
Typically
Low
Typically Low. Low unless errors disclose credentials, keys or sensitive data, in which case rate it by what was exposed.
04How to verify
- 1Submit malformed input, unexpected types and invalid routes to the application and API.
- 2Record any response containing stack traces, versions, paths or query details.
- 3Check whether debug mode is enabled.
Testing note: only test systems you are authorized to test, within the agreed scope and rules of engagement. Verification steps are written for professional testers and avoid destructive techniques.
05Remediation
- 1Return generic error messages to users and log details server-side.
- 2Disable debug mode and detailed errors in production configuration.
- 3Add a global exception handler so unhandled errors never reach the client.
Draft findings like this from your own evidence
Book a demo