Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CWE-209 (通过错误消息导致的信息暴露) — Vulnerability Class 297

297 vulnerabilities classified as CWE-209 (通过错误消息导致的信息暴露). AI Chinese analysis included.

CWE-209 represents a critical information disclosure weakness where software inadvertently exposes sensitive internal details through error messages. This flaw typically occurs when applications return verbose stack traces, database paths, or user-specific data to end-users during failure states. Attackers exploit this by triggering specific errors to gather reconnaissance information, such as server architecture, file structures, or valid user identifiers, which facilitates further targeted attacks like SQL injection or privilege escalation. To mitigate this risk, developers must implement robust error handling mechanisms that separate internal diagnostic logs from user-facing messages. By standardizing generic, non-descriptive error responses for external users while retaining detailed logs for internal debugging, organizations can prevent attackers from leveraging error output to map system vulnerabilities or compromise sensitive data integrity.

MITRE CWE Description
The product generates an error message that includes sensitive information about its environment, users, or associated data.
Common Consequences (1)
ConfidentialityRead Application Data
Often this will either reveal sensitive information which may be used to launch another, more focused attack or disclose private information stored in the server. For example, an attempt to exploit a path traversal weakness (CWE-22) might yield the full pathname of the installed application. In tur…
Mitigations (5)
ImplementationEnsure 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…
ImplementationHandle exceptions internally and do not display errors containing potentially sensitive information to a user.
ImplementationUse 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.
Effectiveness: Defense in Depth
Implementation, Build and CompilationDebugging information should not make its way into a production release.
Implementation, Build and CompilationDebugging information should not make its way into a production release.
Examples (2)
In the following example, sensitive information might be printed depending on the exception that occurs.
try { /.../ } catch (Exception e) { System.out.println(e); }
Bad · Java
This code tries to open a database connection, and prints any exceptions that occur.
try { openDbConnection(); } //print exception message that includes exception message and configuration file location catch (Exception $e) { echo 'Caught exception: ', $e->getMessage(), '\n'; echo 'Check credentials in config file at: ', $Mysql_config_location, '\n'; }
Bad · PHP
CVE IDTitleCVSSSeverityPublished
CVE-2020-2505 Sensitive information via generation of error messages vulnerability in QES — QES 2.3 Low2020-12-24
CVE-2020-16128 Aptdaemon error messages disclosed file existence to unprivileged users via dbus properties — aptdaemon 3.8 Low2020-12-09
CVE-2020-25640 Red Hat Wildfly 日志信息泄露漏洞 — wildfly 5.3 -2020-11-24
CVE-2020-16121 PackageKit error messages leak presence and mimetype of files to unprivileged users — PackageKit 3.3 Low2020-11-07
CVE-2020-25633 Red Hat Resteasy 安全漏洞 — resteasy-client 5.3 Medium2020-09-18
CVE-2020-15132 Reset Password / Login vulnerability in Sulu — sulu 5.3 Medium2020-08-05
CVE-2020-14337 Red Hat Ansible Tower 安全漏洞 — Ansible Tower 5.8 -2020-07-31
CVE-2020-8213 Ubiquiti Networks UniFi Protect 信息泄露漏洞 — Protect for UniFi Cloud Key Gen2 Plus 5.3 -2020-07-30
CVE-2020-15125 Authorization header is not sanitized in an error object in auth0 — node-auth0 7.7 High2020-07-29
CVE-2019-11252 Credential leakage when failing to mount — Kubernetes 5.9 Medium2020-07-23
CVE-2020-5274 Exceptions displayed in non-debug configurations in Symfony — symfony 4.6 Medium2020-03-30
CVE-2019-19342 Ansible Tower 安全漏洞 — Tower 5.3 -2019-12-19
CVE-2019-16768 Internal exception message exposure for login action in Sylius — Sylius 3.5 Low2019-12-05
CVE-2019-3756 Dell EMC RSA Archer 信息泄露漏洞 — RSA Archer 6.5 -2019-09-18
CVE-2019-5483 Seneca 安全漏洞 — seneca 5.3 -2019-09-09
CVE-2019-7612 Elasticsearch Logstash 日志信息泄露漏洞 — Logstash 9.8 -2019-03-25
CVE-2017-2659 dropbear 授权问题漏洞 — dropbear 7.5 -2019-03-20
CVE-2018-17891 Carestream Vue RIS 信息泄露漏洞 — Vue RIS 3.7 -2018-10-04
CVE-2018-10913 Red Hat glusterfs服务器信息泄露漏洞 — glusterfs 6.5 -2018-09-04
CVE-2018-10624 Johnson Controls Metasys and BCPro Generation of Error Message Containing Sensitive Information — Metasys System 6.5 -2018-08-01
CVE-2018-12536 Eclipse Jetty Server 信息泄露漏洞 — Eclipse Jetty 5.3 -2018-06-27
CVE-2018-1073 Red Hat ovirt-engine 信息泄露漏洞 — ovirt-engine 5.3 -2018-06-19
CVE-2017-2594 hawtio 路径遍历漏洞 — hawtio 7.5 -2018-05-08
CVE-2017-7551 389-ds-base 授权问题漏洞 — 389-ds-base 9.8 -2017-08-16
CVE-2017-0885 Nextcloud Server 安全漏洞 — Nextcloud Server 4.3 -2017-04-05
CVE-2016-9459 Nextcloud Server和ownCloud Server 跨站脚本漏洞 — Nextcloud Server & ownCloud Server Nextcloud Server before 9.0.52 & ownCloud Server before 9.0.4 6.1 -2017-03-28
CVE-2012-0059 Spacewalk-backend: spacewalk-backend: information disclosure via cleartext passwords in error messages — Red Hat Enterprise Linux 6 4.9 Medium2014-02-05

Vulnerabilities classified as CWE-209 (通过错误消息导致的信息暴露) represent 297 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.