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-2025-31141 JetBrains TeamCity 安全漏洞 — TeamCity 2.7 Low2025-03-27
CVE-2024-12380 Generation of Error Message Containing Sensitive Information in GitLab — GitLab 4.4 Medium2025-03-13
CVE-2025-2239 Absolute Path Disclosure Vulnerability in Hillstone Next Generation FireWall — Hillstone Next Generation FireWall 5.3 Medium2025-03-12
CVE-2025-23185 Information Disclosure in SAP Business Objects Business Intelligence Platform — SAP Business Objects Business Intelligence Platform 4.1 Medium2025-03-11
CVE-2025-20002 GMOD Apollo Generation of Error Message Containing Sensitive Information — Apollo 5.3 Medium2025-03-05
CVE-2024-56810 IBM EntireX information disclosure — EntireX 3.3 Low2025-02-27
CVE-2024-56496 IBM EntireX information disclosure — EntireX 3.3 Low2025-02-27
CVE-2024-56495 IBM EntireX information disclosure — EntireX 3.3 Low2025-02-27
CVE-2024-56811 IBM EntireX information disclosure — EntireX 3.3 Low2025-02-27
CVE-2024-56493 IBM EntireX information disclosure — EntireX 3.3 Low2025-02-27
CVE-2024-56494 IBM EntireX information disclosure — EntireX 3.3 Low2025-02-27
CVE-2024-56812 IBM EntireX information disclosure — EntireX 3.3 Low2025-02-27
CVE-2025-0941 MET ONE 3400+ Potential Credential Exposure — MET ONE 3400+ 5.8 Medium2025-02-26
CVE-2024-13537 C9 Blocks <= 1.7.7 - Unauthenticated Full Path Disclosure — C9 Blocks 5.3 Medium2025-02-21
CVE-2024-13535 Actionwear products sync <= 2.3.2 - Unauthenticated Full Patch Disclosure — Actionwear products sync 5.3 Medium2025-02-18
CVE-2024-13540 WooODT Lite – Delivery & pickup date time location for WooCommerce <= 2.5.1 - Unauthenticated Full Path Dsiclosure — WooODT Lite – Delivery & pickup date time location for WooCommerce 5.3 Medium2025-02-18
CVE-2024-13538 BigBuy Dropshipping Connector for WooCommerce <= 2.0.0 - Unauthenticated Full Path Disclosute — BigBuy Dropshipping Connector for WooCommerce 5.3 Medium2025-02-18
CVE-2024-13539 AForms Eats <= 1.3.1 - Unauthenticated Full Path Disclosure — AForms Eats 5.3 Medium2025-02-12
CVE-2024-52611 SolarWinds Platform Information Disclosure Vulnerability — SolarWinds Platform 3.5 Low2025-02-11
CVE-2024-56467 IBM EntireX information disclosure — EntireX 3.3 Low2025-02-06
CVE-2024-49798 IBM ApplinX Information Disclosure — ApplinX 4.3 Medium2025-02-05
CVE-2024-45658 IBM Security Verify Access information disclosure — Security Verify Access Appliance 2.7 Low2025-02-04
CVE-2024-45659 IBM Security Verify Access information disclosure — Security Verify Access Appliance 5.3 Medium2025-02-04
CVE-2025-23216 Argo CD does not scrub secret values from patch errors — argo-cd 6.8 Medium2025-01-30
CVE-2024-35134 IBM Analytics Content Hub information disclosure — Analytics Content Hub 5.3 Medium2025-01-25
CVE-2023-38713 IBM Cloud Pak System information disclosure — Cloud Pak System 5.3 Medium2025-01-25
CVE-2023-38714 IBM Cloud Pak System information disclosure — Cloud Pak System 5.3 Medium2025-01-25
CVE-2023-38716 IBM Cloud Pak System information disclosure — Cloud Pak System 5.3 Medium2025-01-25
CVE-2024-35111 IBM Control Center information disclosure — Control Center 4.3 Medium2025-01-25
CVE-2025-24552 WordPress Paytium plugin <= 4.4.11 - Full Path Disclosure (FPD) vulnerability — Paytium 5.3 Medium2025-01-24

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