CWE-209
AllowedGeneration of Error Message Containing Sensitive Information
Abstraction: Base · Status: Draft
The product generates an error message that includes sensitive information about its environment, users, or associated data.
900 vulnerabilities reference this CWE, most recent first.
GHSA-GQ2R-QH4M-2G7X
Vulnerability from github – Published: 2026-05-27 15:33 – Updated: 2026-05-27 18:31IBM Business Automation Workflow containers and traditional may leak information about its database structure in error messages.
{
"affected": [],
"aliases": [
"CVE-2026-1248"
],
"database_specific": {
"cwe_ids": [
"CWE-209"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-05-27T15:16:24Z",
"severity": "MODERATE"
},
"details": "IBM Business Automation Workflow containers and traditional\u00a0may leak information about its database structure in error messages.",
"id": "GHSA-gq2r-qh4m-2g7x",
"modified": "2026-05-27T18:31:37Z",
"published": "2026-05-27T15:33:25Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-1248"
},
{
"type": "WEB",
"url": "https://www.ibm.com/support/pages/node/7271445"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-GQJ9-6PWJ-7952
Vulnerability from github – Published: 2022-05-04 00:27 – Updated: 2026-04-03 00:31Spacewalk-backend in Red Hat Network (RHN) Satellite and Proxy 5.4 includes cleartext user passwords in an error message when a system registration XML-RPC call fails, which allows remote administrators to obtain the password by reading (1) the server log and (2) an email.
{
"affected": [],
"aliases": [
"CVE-2012-0059"
],
"database_specific": {
"cwe_ids": [
"CWE-209"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2014-02-05T18:55:00Z",
"severity": "MODERATE"
},
"details": "Spacewalk-backend in Red Hat Network (RHN) Satellite and Proxy 5.4 includes cleartext user passwords in an error message when a system registration XML-RPC call fails, which allows remote administrators to obtain the password by reading (1) the server log and (2) an email.",
"id": "GHSA-gqj9-6pwj-7952",
"modified": "2026-04-03T00:31:08Z",
"published": "2022-05-04T00:27:49Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2012-0059"
},
{
"type": "WEB",
"url": "https://access.redhat.com/security/cve/CVE-2012-0059"
},
{
"type": "WEB",
"url": "http://rhn.redhat.com/errata/RHSA-2012-0101.html"
},
{
"type": "WEB",
"url": "http://rhn.redhat.com/errata/RHSA-2012-0102.html"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-GVCF-X6QV-74P4
Vulnerability from github – Published: 2026-08-10 18:32 – Updated: 2026-08-10 18:32HCL BigFix Mobile is vulnerable to information disclosure due to improper handling of exceptions and verbose error reporting.
{
"affected": [],
"aliases": [
"CVE-2026-56620"
],
"database_specific": {
"cwe_ids": [
"CWE-209"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-08-10T16:19:48Z",
"severity": "MODERATE"
},
"details": "HCL BigFix Mobile\u00a0is vulnerable to information disclosure due to improper handling of exceptions and verbose error reporting.",
"id": "GHSA-gvcf-x6qv-74p4",
"modified": "2026-08-10T18:32:12Z",
"published": "2026-08-10T18:32:12Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-56620"
},
{
"type": "WEB",
"url": "https://support.hcl-software.com/csm?id=kb_article\u0026sysparm_article=KB0132661"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-GVV7-WMVP-M3X6
Vulnerability from github – Published: 2025-02-27 15:31 – Updated: 2025-02-27 15:31IBM EntireX 11.1 could allow a local user to obtain sensitive information when a detailed technical error message is returned. This information could be used in further attacks against the system.
{
"affected": [],
"aliases": [
"CVE-2024-56810"
],
"database_specific": {
"cwe_ids": [
"CWE-209"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-02-27T15:15:39Z",
"severity": "LOW"
},
"details": "IBM EntireX 11.1 could allow a local user to obtain sensitive information when a detailed technical error message is returned. This information could be used in further attacks against the system.",
"id": "GHSA-gvv7-wmvp-m3x6",
"modified": "2025-02-27T15:31:52Z",
"published": "2025-02-27T15:31:52Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-56810"
},
{
"type": "WEB",
"url": "https://www.ibm.com/support/pages/node/7184194"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-GVWH-7G48-MFJG
Vulnerability from github – Published: 2023-08-28 15:30 – Updated: 2024-04-04 07:14User enumeration is found in PHPJabbers Document Creator v1.0. This issue occurs during password recovery, where a difference in messages could allow an attacker to determine if the user is valid or not, enabling a brute force attack with valid users.
{
"affected": [],
"aliases": [
"CVE-2023-40758"
],
"database_specific": {
"cwe_ids": [
"CWE-209"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-08-28T13:15:10Z",
"severity": "CRITICAL"
},
"details": "User enumeration is found in PHPJabbers Document Creator v1.0. This issue occurs during password recovery, where a difference in messages could allow an attacker to determine if the user is valid or not, enabling a brute force attack with valid users.",
"id": "GHSA-gvwh-7g48-mfjg",
"modified": "2024-04-04T07:14:21Z",
"published": "2023-08-28T15:30:17Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-40758"
},
{
"type": "WEB",
"url": "https://medium.com/%40mfortinsec/multiple-vulnerabilities-in-phpjabbers-part-3-40fc3565982f"
},
{
"type": "WEB",
"url": "https://medium.com/@mfortinsec/multiple-vulnerabilities-in-phpjabbers-part-3-40fc3565982f"
},
{
"type": "WEB",
"url": "https://www.phpjabbers.com/document-creator"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-GWFQ-86J8-7QHV
Vulnerability from github – Published: 2026-08-05 19:59 – Updated: 2026-08-05 19:59Summary
When an RC API call triggers a panic (recovered by the job runner), the full Go stack trace is included in the JSON error response. This leaks internal file paths, Go module versions, goroutine state, and memory addresses to the API caller.
Details
The panic recovery in fs/rc/jobs/job.go:110-115:
func (j *Job) run(ctx context.Context, fn rc.Func, in rc.Params) {
defer func() {
if r := recover(); r != nil {
j.mu.Lock()
j.EndTime = time.Now()
j.Error = fmt.Sprintf("panic received: %v \n%s", r, string(debug.Stack()))
// ...
}
}()
The full debug.Stack() output is placed into j.Error, which is then returned in the HTTP response JSON.
PoC
Trigger a parse error by setting config path to a non-INI file, then calling dump:
curl -s -X POST http://localhost:5572/config/setpath \
-H "Content-Type: application/json" \
-d '{"path":"/etc/hostname"}'
curl -s -X POST http://localhost:5572/config/dump
Response includes:
{
"error": "panic received: fatal error: Failed to load config file \"/etc/hostname\": could not parse line: ... \ngoroutine 9 [running]:\nruntime/debug.Stack()\n\truntime/debug/stack.go:26 +0x64\ngithub.com/rclone/rclone/fs/rc/jobs.(*Job).run.func1()\n\tgithub.com/rclone/rclone/fs/rc/jobs/job.go:112 +0x34\n...",
"status": 500
}
Disclosed information includes:
- Full filesystem paths (github.com/rclone/rclone/fs/config/config.go:377)
- Go module versions (github.com/go-chi/chi/v5@v5.2.5)
- Go runtime version (from binary)
- Goroutine IDs and states
- Memory addresses (ASLR leak)
- File contents (first unparseable line of the target file)
Tested and confirmed on rclone v1.74.4.
Impact
Information disclosure that aids exploitation of other vulnerabilities. Stack traces reveal internal architecture, dependency versions (useful for known-CVE targeting), and memory layout. The error message also leaks partial file contents (the first line that fails INI parsing), which can be used alongside the arbitrary file read finding as a complementary file read primitive for non-INI files.
Affected Versions
All versions with RC API support through at least v1.74.4.
Remediation
Return a generic error message to the API caller. Log the full stack trace server-side only. Strip debug.Stack() from HTTP responses.
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 1.74.4"
},
"package": {
"ecosystem": "Go",
"name": "github.com/rclone/rclone"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.75.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [],
"database_specific": {
"cwe_ids": [
"CWE-209"
],
"github_reviewed": true,
"github_reviewed_at": "2026-08-05T19:59:55Z",
"nvd_published_at": null,
"severity": "LOW"
},
"details": "### Summary\n\nWhen an RC API call triggers a panic (recovered by the job runner), the full Go stack trace is included in the JSON error response. This leaks internal file paths, Go module versions, goroutine state, and memory addresses to the API caller.\n\n### Details\n\nThe panic recovery in `fs/rc/jobs/job.go:110-115`:\n\n```go\nfunc (j *Job) run(ctx context.Context, fn rc.Func, in rc.Params) {\n defer func() {\n if r := recover(); r != nil {\n j.mu.Lock()\n j.EndTime = time.Now()\n j.Error = fmt.Sprintf(\"panic received: %v \\n%s\", r, string(debug.Stack()))\n // ...\n }\n }()\n```\n\nThe full `debug.Stack()` output is placed into `j.Error`, which is then returned in the HTTP response JSON.\n\n### PoC\n\nTrigger a parse error by setting config path to a non-INI file, then calling dump:\n\n```bash\ncurl -s -X POST http://localhost:5572/config/setpath \\\n -H \"Content-Type: application/json\" \\\n -d \u0027{\"path\":\"/etc/hostname\"}\u0027 \n\ncurl -s -X POST http://localhost:5572/config/dump\n```\n\nResponse includes:\n\n```json\n{\n \"error\": \"panic received: fatal error: Failed to load config file \\\"/etc/hostname\\\": could not parse line: ... \\ngoroutine 9 [running]:\\nruntime/debug.Stack()\\n\\truntime/debug/stack.go:26 +0x64\\ngithub.com/rclone/rclone/fs/rc/jobs.(*Job).run.func1()\\n\\tgithub.com/rclone/rclone/fs/rc/jobs/job.go:112 +0x34\\n...\",\n \"status\": 500\n}\n```\n\n**Disclosed information includes:**\n- Full filesystem paths (`github.com/rclone/rclone/fs/config/config.go:377`)\n- Go module versions (`github.com/go-chi/chi/v5@v5.2.5`)\n- Go runtime version (from binary)\n- Goroutine IDs and states\n- Memory addresses (ASLR leak)\n- File contents (first unparseable line of the target file)\n\n**Tested and confirmed on rclone v1.74.4.**\n\n### Impact\n\nInformation disclosure that aids exploitation of other vulnerabilities. Stack traces reveal internal architecture, dependency versions (useful for known-CVE targeting), and memory layout. The error message also leaks partial file contents (the first line that fails INI parsing), which can be used alongside the arbitrary file read finding as a complementary file read primitive for non-INI files.\n\n### Affected Versions\n\nAll versions with RC API support through at least v1.74.4.\n\n### Remediation\n\nReturn a generic error message to the API caller. Log the full stack trace server-side only. Strip `debug.Stack()` from HTTP responses.",
"id": "GHSA-gwfq-86j8-7qhv",
"modified": "2026-08-05T19:59:55Z",
"published": "2026-08-05T19:59:55Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/rclone/rclone/security/advisories/GHSA-gwfq-86j8-7qhv"
},
{
"type": "WEB",
"url": "https://github.com/rclone/rclone/commit/ff43a1e3ae17627c80e523a0ca7445f96516d199"
},
{
"type": "PACKAGE",
"url": "https://github.com/rclone/rclone"
},
{
"type": "WEB",
"url": "https://github.com/rclone/rclone/releases/tag/v1.75.0"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
],
"summary": "rclone: Verbose Stack Trace Disclosure in RC API Error Responses"
}
GHSA-GXQF-3R4G-3736
Vulnerability from github – Published: 2025-04-04 00:32 – Updated: 2025-04-04 00:32HCL Traveler generates some error messages that provide detailed information about errors and failures, such as internal paths, file names, sensitive tokens, credentials, error codes, or stack traces. Attackers could exploit this information to gain insights into the system's architecture and potentially launch targeted attacks.
{
"affected": [],
"aliases": [
"CVE-2025-0279"
],
"database_specific": {
"cwe_ids": [
"CWE-209"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-04-03T22:15:16Z",
"severity": "MODERATE"
},
"details": "HCL Traveler generates some error messages that provide detailed information about errors and failures, such as internal paths, file names, sensitive tokens, credentials, error codes, or stack traces. Attackers could exploit this information to gain insights into the system\u0027s architecture and potentially launch targeted attacks.",
"id": "GHSA-gxqf-3r4g-3736",
"modified": "2025-04-04T00:32:07Z",
"published": "2025-04-04T00:32:07Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-0279"
},
{
"type": "WEB",
"url": "https://support.hcl-software.com/csm?id=kb_article\u0026sysparm_article=KB0120336"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-H2J5-QH4R-F6CM
Vulnerability from github – Published: 2026-01-30 09:30 – Updated: 2026-06-06 09:31Generation of Error Message Containing Sensitive Information vulnerability in Codriapp Innovation and Software Technologies Inc. HeyGarson allows Fuzzing for application mapping.This issue affects HeyGarson: through 30012026.
NOTE: The vendor was contacted early about this disclosure but did not respond in any way.
{
"affected": [],
"aliases": [
"CVE-2025-1395"
],
"database_specific": {
"cwe_ids": [
"CWE-209"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-01-30T09:15:49Z",
"severity": "HIGH"
},
"details": "Generation of Error Message Containing Sensitive Information vulnerability in Codriapp Innovation and Software Technologies Inc. HeyGarson allows Fuzzing for application mapping.This issue affects HeyGarson: through 30012026.\n\nNOTE: The vendor was contacted early about this disclosure but did not respond in any way.",
"id": "GHSA-h2j5-qh4r-f6cm",
"modified": "2026-06-06T09:31:15Z",
"published": "2026-01-30T09:30:55Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-1395"
},
{
"type": "WEB",
"url": "https://siberguvenlik.gov.tr/guvenlik-bildirimleri/detay/tr-26-0009"
},
{
"type": "WEB",
"url": "https://www.usom.gov.tr/bildirim/tr-26-0009"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-H2XX-FX3F-HJ9X
Vulnerability from github – Published: 2025-03-11 03:30 – Updated: 2025-03-11 03:30Due to improper error handling in SAP Business Objects Business Intelligence Platform, technical details of the application are revealed in exceptions thrown to the user and in stack traces. Only an attacker with administrator level privileges has access to this disclosed information, and they could use it to craft further exploits. There is no impact on the integrity and availability of the application.
{
"affected": [],
"aliases": [
"CVE-2025-23185"
],
"database_specific": {
"cwe_ids": [
"CWE-209"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-03-11T01:15:34Z",
"severity": "MODERATE"
},
"details": "Due to improper error handling in SAP Business Objects Business Intelligence Platform, technical details of the application are revealed in exceptions thrown to the user and in stack traces. Only an attacker with administrator level privileges has access to this disclosed information, and they could use it to craft further exploits. There is no impact on the integrity and availability of the application.",
"id": "GHSA-h2xx-fx3f-hj9x",
"modified": "2025-03-11T03:30:50Z",
"published": "2025-03-11T03:30:50Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-23185"
},
{
"type": "WEB",
"url": "https://me.sap.com/notes/3549494"
},
{
"type": "WEB",
"url": "https://url.sap/sapsecuritypatchday"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-H382-4J66-7V4W
Vulnerability from github – Published: 2023-09-14 03:30 – Updated: 2024-04-04 07:39Due to the lack of validation, SAP BusinessObjects Business Intelligence Platform (Version Management System) - version 403, permits an unauthenticated user to read the code snippet through the UI, which leads to low impact on confidentiality and no impact on the application's availability or integrity.
{
"affected": [],
"aliases": [
"CVE-2023-37489"
],
"database_specific": {
"cwe_ids": [
"CWE-209"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-09-12T02:15:12Z",
"severity": "MODERATE"
},
"details": "Due to the lack of validation, SAP BusinessObjects Business Intelligence Platform (Version Management System) - version 403, permits an unauthenticated user to read the code snippet through the UI, which leads to low impact on confidentiality and no impact on the application\u0027s availability or integrity.\n\n",
"id": "GHSA-h382-4j66-7v4w",
"modified": "2024-04-04T07:39:46Z",
"published": "2023-09-14T03:30:32Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-37489"
},
{
"type": "WEB",
"url": "https://me.sap.com/notes/3352453"
},
{
"type": "WEB",
"url": "https://www.sap.com/documents/2022/02/fa865ea4-167e-0010-bca6-c68f7e60039b.html"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
]
}
Mitigation MIT-39
- 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.
Mitigation
Handle exceptions internally and do not display errors containing potentially sensitive information to a user.
Mitigation MIT-33
Strategy: Attack Surface Reduction
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.
Mitigation MIT-40
Strategy: Compilation or Build Hardening
Debugging information should not make its way into a production release.
Mitigation MIT-40
Strategy: Environment Hardening
Debugging information should not make its way into a production release.
Mitigation
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.
Mitigation
Create default error pages or messages that do not leak any information.
CAPEC-215: Fuzzing for application mapping
An attacker sends random, malformed, or otherwise unexpected messages to a target application and observes the application's log or error messages returned. The attacker does not initially know how a target will respond to individual messages but by attempting a large number of message variants they may find a variant that trigger's desired behavior. In this attack, the purpose of the fuzzing is to observe the application's log and error messages, although fuzzing a target can also sometimes cause the target to enter an unstable state, causing a crash.
CAPEC-463: Padding Oracle Crypto Attack
An adversary is able to efficiently decrypt data without knowing the decryption key if a target system leaks data on whether or not a padding error happened while decrypting the ciphertext. A target system that leaks this type of information becomes the padding oracle and an adversary is able to make use of that oracle to efficiently decrypt data without knowing the decryption key by issuing on average 128*b calls to the padding oracle (where b is the number of bytes in the ciphertext block). In addition to performing decryption, an adversary is also able to produce valid ciphertexts (i.e., perform encryption) by using the padding oracle, all without knowing the encryption key.
CAPEC-54: Query System for Information
An adversary, aware of an application's location (and possibly authorized to use the application), probes an application's structure and evaluates its robustness by submitting requests and examining responses. Often, this is accomplished by sending variants of expected queries in the hope that these modified queries might return information beyond what the expected set of queries would provide.
CAPEC-7: Blind SQL Injection
Blind SQL Injection results from an insufficient mitigation for SQL Injection. Although suppressing database error messages are considered best practice, the suppression alone is not sufficient to prevent SQL Injection. Blind SQL Injection is a form of SQL Injection that overcomes the lack of error messages. Without the error messages that facilitate SQL Injection, the adversary constructs input strings that probe the target through simple Boolean SQL expressions. The adversary can determine if the syntax and structure of the injection was successful based on whether the query was executed or not. Applied iteratively, the adversary determines how and where the target is vulnerable to SQL Injection.