CWE-210: Information Exposure Through Generated Error Message
Information Exposure Through Generated Error Message
Weakness ID: 210 (Weakness Base)
Status: Draft
Description
Description Summary
The software identifies an error condition and creates its own diagnostic or error messages that contain sensitive information.
Time of Introduction
Architecture and Design
Implementation
Operation
Applicable Platforms
Languages
All
Common Consequences
Scope
Effect
Confidentiality
Technical Impact: Read application
data
Demonstrative Examples
Example 1
The following code uses custom configuration files for each user in
the application. It checks to see if the file exists on the system before
attempting to open and use the file. If the configuration file does not
exist, then an error is generated, and the application exits.
If this code is running on a server, such as a web application, then
the person making the request should not know what the full pathname of
the configuration directory is. By submitting a username that is not
associated with a configuration file, an attacker could get this
pathname from the error message. It could then be used to exploit path
traversal, symbolic link following, or other problems that may exist
elsewhere in the application.
Infoleak of sensitive information in error message
(physical access required).
Potential Mitigations
Phase: Implementation
Any error should be parsed for dangerous revelations.
Phases: Implementation; Build and Compilation
Strategies: Compilation or Build Hardening; Environment Hardening
Debugging information should not make its way into a production
release.
Handle exceptions internally and do not display errors containing
potentially sensitive information to a user. Create default error pages
if necessary.
Description
