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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

320 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-2026-63748 SurrealDB before 3.1.0 Information Disclosure via Error Messages — surrealdb 4.3 Medium2026-07-20
CVE-2026-8861 Security vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access — Verify Identity Access 5.3 Medium2026-07-17
CVE-2024-23575 HCL Aftermarket EPC 信息泄露漏洞 — Aftermarket EPC 5.3 Medium2026-07-17
CVE-2026-56139 Apache Camel Undertow: The muteException consumer option defaulted to false, so a processing error returned the full Java stack trace in the HTTP response body, disclosing sensitive internal information to unauthenticated clients — Apache Camel Undertow--2026-07-06
CVE-2026-49365 Apache Camel: Camel-Netty-HTTP: The muteException consumer option defaulted to false, so a processing error returned the full Java stack trace in the HTTP response body, disclosing sensitive internal information to unauthenticated clients — Apache Camel--2026-07-06
CVE-2026-56331 Capgo - Improper Error Handling in Accept Invitation Endpoint via Invalid Magic String — Capgo 5.3 Medium2026-06-30
CVE-2025-36328 Error Message Containing Sensitive Information found in Watson Data Intelligence — watsonx.data intelligence 4.3 Medium2026-06-30
CVE-2026-47775 Envoy OAuth2 Filter: Padding Oracle via AES-256-CBC Cookie Decryption — envoy 6.8 Medium2026-06-26
CVE-2026-49979 Appsmith: SSRF via `POST /api/v1/admin/send-test-email` — JavaMail Bypasses WebClient IP Filter — appsmith--2026-06-24
CVE-2025-59872 HCL ZIE for Web is affetced by an Unrestricted File Upload vulnerability, — ZIE 4.3 Medium2026-06-17
CVE-2026-47248 Parse Server: GraphQL "Did you mean" validation suggestions disclose schema to unauthenticated callers — parse-server--2026-06-12
CVE-2026-40997 SOAP security faults leak Spring Security account state — Spring Web Services 5.3 Medium2026-06-11
CVE-2026-41730 Spring Data REST exposes persistence-layer internals in error responses — Spring Data REST 5.3 Medium2026-06-09
CVE-2025-52606 HCL iControl was affected by Weak Input Validation vulnerability. . — iControl 4.3 Medium2026-06-04
CVE-2025-52611 HCL iControl was affected by Unhandled Exception - Stack Trace Disclosure vulnerability — iControl 3.1 Low2026-06-04
CVE-2026-9794 Keycloak: keycloak: information disclosure via saml ecp endpoint — Red Hat build of Keycloak 26.4 5.3 Medium2026-05-28
CVE-2024-28765 Security vulnerability was found in IBM Security Directory Integrator — SDI 5.3 Medium2026-05-27
CVE-2026-9583 SourceCodester CET Automated Grading System with AI Predictive Analytics SQL index.php information exposure — CET Automated Grading System with AI Predictive Analytics 4.3 Medium2026-05-26
CVE-2026-45728 Algernon: Single-file mode unconditionally enables debug mode — algernon 7.5 High2026-05-26
CVE-2026-5511 Information Disclosure via Diagnostic Interface Due to Improper Input Validation on TP-Link's Archer AX72 — Archer AX72 (SG) v1.0--2026-05-19
CVE-2026-7860 Possible information disclosure of environment variables in Vaadin Build Plugins via Failed Frontend Build — flow--2026-05-19
CVE-2026-42552 Flight: Sensitive information disclosure via default error handler in flightphp/core — core 7.5 High2026-05-13
CVE-2026-44002 vm2: Host File Path Disclosure via Stack Trace Information Leak — vm2 5.8 Medium2026-05-13
CVE-2026-43873 WWBN AVideo: Unauthenticated Disclosure of CloneSite `myKey` via Error Echo in `cloneClient.json.php` Enables Cross-Site DB Dump of the Configured Clone Server — AVideo 7.5 High2026-05-11
CVE-2026-44226 pyLoad: Unauthenticated traceback disclosure via global exception handler in WebUI — pyload 5.3 Medium2026-05-11
CVE-2026-41644 monetr is vulnerable to server-side request forgery in Lunch Flow link creation and refresh — monetr 4.3AIMediumAI2026-05-07
CVE-2025-31960 HCL BigFix Service Management (SM) is vulnerable to information exposure due to improper error handling within its reporting module — BigFix Service Management (SM) 5.3 Medium2026-05-06
CVE-2025-59853 HCL DFXAnalytics is affected by an Improper Error Handling vulnerability — DFXAnalytics 3.1 Low2026-05-06
CVE-2026-40969 Spring gRPC AuthenticationException message reflected to remote client — Spring gRPC 3.7 Low2026-04-28
CVE-2026-3259 Sensitive Data Disclosure in BigQuery via Materialized View Error Messages — BigQuery 4.3AIMediumAI2026-04-23

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