Externally-Generated Error Message Containing Sensitive Information
CWE-211
Short description
Best practices to prevent this CWE
Phase: System Configuration
Configure the application's environment in a way that prevents errors from being generated. For example, in PHP, disable display_errors.
Phase: Implementation; Build and Compilation
Strategy: Compilation or Build Hardening
Debugging information should not make its way into a production release.
Phase: Implementation; Build and Compilation
Strategy: Environment Hardening
Debugging information should not make its way into a production release.
Phase: Implementation
Handle exceptions internally and do not display errors containing potentially sensitive information to a user. Create default error pages if necessary.
Phase: 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.