CWE-211: Externally-Generated Error Message Containing Sensitive Information
0 CVEs have CWE-211 as their primary weakness. 0 of them are in the CISA KEV catalog.
The product performs an operation that triggers an external diagnostic or error message that is not directly generated or controlled by the product, such as an error generated by the programming language interpreter that a software application uses. The error can contain sensitive system information.
Child of CWE-209: Generation of Error Message Containing Sensitive Information
Mitigations
- System Configuration: Configure the application's environment in a way that prevents errors from being generated. For example, in PHP, disable display_errors.
- Implementation Build and Compilation: Debugging information should not make its way into a production release.
- Implementation Build and Compilation: Debugging information should not make its way into a production release.
- Implementation: Handle exceptions internally and do not display errors containing potentially sensitive information to a user. Create default error pages if necessary.
- Implementation: The best way to prevent this weakness during implementation is to avoid any bugs that could trigger the external error message. This typically happens when the program encounters fatal errors, such as a divide-by-zero. You will not always be able to control the use of error pages, and you might not be using a language that handles exceptions.
Observed examples
- CVE-2004-1581: Chain: product does not protect against direct request of an include file, leading to resultant path disclosure when the include file does not successfully execute.
- CVE-2004-1579: Single ' inserted into SQL query leads to invalid SQL query execution, triggering full path disclosure. Possibly resultant from more general SQL injection issue.
- CVE-2005-0459: Chain: product does not protect against direct request of a library file, leading to resultant path disclosure when the file does not successfully execute.
- CVE-2005-0443: invalid parameter triggers a failure to find an include file, leading to infoleak in error message.
- CVE-2005-0433: Various invalid requests lead to information leak in verbose error messages describing the failure to instantiate a class, open a configuration file, or execute an undefined function.
- CVE-2004-1101: Improper handling of filename request with trailing / causes multiple consequences, including information leak in Visual Basic error message.
Get more CVE data from the API.
curl 'https://api.contrastcyber.com/cwe_lookup/CWE-211'curl 'https://api.contrastcyber.com/cve_search?cwe_id=CWE-211'
Sources
- Vulnerability data from the National Vulnerability Database (NIST) and the CVE Program. CVE records: Copyright © 1999-2026, The MITRE Corporation, used under the CVE Program Terms of Use. CVE® is a registered trademark of The MITRE Corporation.
- CWE definitions: Copyright © 2006-2026, The MITRE Corporation, used under the CWE Terms of Use. CWE is a trademark of The MITRE Corporation.
- EPSS scores by FIRST.org EPSS, used with attribution.
- KEV catalog and SSVC decisions by CISA.
- Advisory data from the GitHub Advisory Database through OSV.dev (CC BY 4.0).
- Exploit metadata from the Exploit Database (GPL-2.0-only, metadata only).
- Nuclei template names from nuclei-templates (MIT).