Error Message Analysis

What is Error Message Analysis?

Detects verbose error messages that disclose stack traces, database queries, or internal paths.

This vulnerability class falls under the Error Handling phase of the OWASP Testing Guide (WSTG-ERRH). Security engineers prioritise error handling checks early in an assessment because weaknesses here provide a foothold that amplifies the severity of vulnerabilities found in later phases.

Security Impact

Detailed errors help attackers understand your stack. This module identifies information disclosure through error handling.

Left undetected, error message analysis issues can persist unnoticed for months. Continuous automated scanning ensures your team receives an alert the moment a regression or new exposure is introduced — long before an attacker discovers it through manual enumeration or automated offensive tooling.

How DygDog Detects It

DygDog triggers edge-case requests to expose information-leaking error pages, stack traces, and debug output that attackers use to map internal architecture.

The Error Message Analysis check is implemented as a passive scan module, meaning it never sends dangerous payloads or modifies application state. Scans complete in approximately 600 ms and run continuously in the background so your security posture reflects the current state of your site — not a point-in-time snapshot.

Remediation Approach

Configure a custom error handler that returns generic, user-friendly messages without stack traces or internal paths; ensure production builds strip debug middleware; and route all exceptions to a centralised logging service.

DygDog does not stop at detection. When a Error Message Analysis finding is confirmed, the platform generates infrastructure-aware, copy-paste-ready remediation snippets using frontier AI models. Instead of generic advice you need to adapt, you receive code that targets your exact server, framework, and configuration.

OWASP References

This check maps to the following OWASP Testing Guide test cases:

• WSTG-ERRH-01View OWASP WSTG →
• WSTG-ERRH-02View OWASP WSTG →

Related Error Handling Checks

These checks belong to the same testing phase and are often assessed together:

• Cryptographic Implementation

  Analyses encryption indicators in cookies, tokens, and API responses for weak or deprecated algorithms.

• Business Logic Indicators

  Detects patterns that may enable business logic abuse: price manipulation fields, quantity limits, workflow bypass paths.

• Rate Limiting Detection

  Checks for rate limiting headers (X-RateLimit-*), retry-after responses, and CAPTCHA implementations on sensitive endpoints.

• Exposed Secrets & API Keys

  Scans page source for leaked credentials: AWS keys, API tokens, database connection strings, private keys.