CWE-209: Generation of Error Message Containing Sensitive Information
627 CVEs have CWE-209 as their primary weakness. 3 of them are in the CISA KEV catalog. The highest EPSS score among them is 98.624%.
The product generates an error message that includes sensitive information about its environment, users, or associated data.
Child of CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Mitigations
- Implementation: Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended). The messages should not reveal the methods that were used to determine the error. Attackers can use detailed information to refine or optimize their original attack, thereby increasing their chances of success. If errors must be captured in some detail, record them in log messages, but consider what could occur if the log messages can be viewed by attackers. Highly sensitive information such as passwords should never be saved to log files. Avoid inconsistent messaging that might accidentally tip off an attacker about internal state, such as whether a user account exists or not.
- Implementation: Handle exceptions internally and do not display errors containing potentially sensitive information to a user.
- Implementation: Use naming conventions and strong types to make it easier to spot when sensitive data is being used. When creating structures, objects, or other complex entities, separate the sensitive and non-sensitive data as much as possible.
- 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.
- System Configuration: Where available, configure the environment to use less verbose error messages. For example, in PHP, disable the display_errors setting during configuration, or at runtime using the error_reporting() function.
- System Configuration: Create default error pages or messages that do not leak any information.
Observed examples
- CVE-2008-2049: POP3 server reveals a password in an error message after multiple APOP commands are sent. Might be resultant from another weakness.
- CVE-2007-5172: Program reveals password in error message if attacker can trigger certain database errors.
- CVE-2008-4638: Composite: application running with high privileges (CWE-250) allows user to specify a restricted file to process, which generates a parsing error that leaks the contents of the file (CWE-209).
- CVE-2008-1579: Existence of user names can be determined by requesting a nonexistent blog and reading the error message.
- CVE-2007-1409: Direct request to library file in web application triggers pathname leak in error message.
- CVE-2008-3060: Malformed input to login page causes leak of full path when IMAP call fails.
- CVE-2005-0603: Malformed regexp syntax leads to information exposure in error message.
- CVE-2017-9615: verbose logging stores admin credentials in a world-readable log file
- CVE-2018-1999036: SSH password for private key stored in build log
Top released CVEs
KEV first, then the highest EPSS score, the highest CVSS score and the newest.
| CVE | Published | Severity | CVSS | EPSS | Description |
|---|---|---|---|---|---|
| CVE-2024-29059 | 2024-03-22 | HIGH | 7.5 | 98.624% | .NET Framework Information Disclosure Vulnerability |
| CVE-2025-47813 | 2025-07-10 | MEDIUM | 4.3 | 63.245% | loginok.html in Wing FTP Server before 7.4.4 discloses the full local installation path of the application when using a long value in the UID cookie. |
| CVE-2013-7331 | 2014-02-26 | MEDIUM | 6.5 | 50.210% | The Microsoft.XMLDOM ActiveX control in Microsoft Windows 8.1 and earlier allows remote attackers to determine the existence of local pathnames, UNC share… |
| CVE-2026-113445 | 2026-11-16 | MEDIUM | 6.9 | not scored | visualTicket is vulnerable to information exposure through an error message in the order creation functionality. Because detailed data-layer exceptions are… |
| CVE-2026-125160 | 2026-11-17 | MEDIUM | 6.3 | not scored | Files uploaded through FileUpload or ImageUpload elements are stored in an unguessable sub-folder that remains the same for the whole form session. If storing… |
| CVE-2026-113456 | 2026-11-16 | MEDIUM | 5.1 | not scored | visualTicket exposes sensitive information in error messages in the cinema report generator. An authenticated attacker with an admin privileges can supply an… |
| CVE-2026-113454 | 2026-11-16 | MEDIUM | 5.1 | not scored | visualTicket exposes sensitive information in error messages in the administrative report generator. Because application exception details and SQL queries are… |
Get more CVE data from the API.
curl 'https://api.contrastcyber.com/cwe_lookup/CWE-209'curl 'https://api.contrastcyber.com/cve_search?cwe_id=CWE-209'
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).