GCVE Workshop - 22 September 2026 (14:00-18:00), Luxembourg Before The Vulnopticon Conference - Registration
Common Weakness Enumeration

CWE-209

Allowed

Generation 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.

901 vulnerabilities reference this CWE, most recent first.

GHSA-5WP7-5X9C-363F

Vulnerability from github – Published: 2022-05-24 17:40 – Updated: 2022-05-24 17:40
VLAI
Details

IBM Cloud Pak for Security (CP4S) 1.3.0.1 and 1.4.0.0 could allow a remote attacker to obtain sensitive information when a detailed technical error message is returned in the browser. This information could be used in further attacks against the system. IBM X-Force ID: 185369.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2020-4628"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-209"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2021-01-27T13:15:00Z",
    "severity": "MODERATE"
  },
  "details": "IBM Cloud Pak for Security (CP4S) 1.3.0.1 and 1.4.0.0 could allow a remote attacker to obtain sensitive information when a detailed technical error message is returned in the browser. This information could be used in further attacks against the system. IBM X-Force ID: 185369.",
  "id": "GHSA-5wp7-5x9c-363f",
  "modified": "2022-05-24T17:40:25Z",
  "published": "2022-05-24T17:40:25Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2020-4628"
    },
    {
      "type": "WEB",
      "url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/185369"
    },
    {
      "type": "WEB",
      "url": "https://www.ibm.com/support/pages/node/6408656"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}

GHSA-5X25-C2RF-F2JX

Vulnerability from github – Published: 2026-06-11 09:31 – Updated: 2026-08-21 19:13
VLAI
Summary
Spring Web Services: SOAP security faults leak Spring Security account state
Details

Several Spring WS integration paths with Spring Security could surface detailed account state (for example locked or disabled user semantics) to remote SOAP clients through exception messages or callback outcomes, instead of failing with generic authentication errors. That behavior assists remote attackers in distinguishing valid accounts from invalid ones and inferring lifecycle state.

Affected versions: Spring Web Services 5.0.0 through 5.0.1; 4.1.0 through 4.1.3; 4.0.0 through 4.0.18; 3.1.0 through 3.1.8.

Show details on source website

{
  "affected": [
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 5.0.1"
      },
      "package": {
        "ecosystem": "Maven",
        "name": "org.springframework.ws:spring-ws-security"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "5.0.0"
            },
            {
              "fixed": "5.0.2"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 4.1.3"
      },
      "package": {
        "ecosystem": "Maven",
        "name": "org.springframework.ws:spring-ws-security"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "4.1.0"
            },
            {
              "fixed": "4.1.4"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Maven",
        "name": "org.springframework.ws:spring-ws-security"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "4.0.0"
            },
            {
              "last_affected": "4.0.18"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Maven",
        "name": "org.springframework.ws:spring-ws-security"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "3.1.0"
            },
            {
              "last_affected": "3.1.8"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-40997"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-209"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-08-21T19:13:01Z",
    "nvd_published_at": "2026-06-11T07:16:27Z",
    "severity": "MODERATE"
  },
  "details": "Several Spring WS integration paths with Spring Security could surface detailed account state (for example locked or disabled user semantics) to remote SOAP clients through exception messages or callback outcomes, instead of failing with generic authentication errors. That behavior assists remote attackers in distinguishing valid accounts from invalid ones and inferring lifecycle state.\n\nAffected versions:\nSpring Web Services 5.0.0 through 5.0.1; 4.1.0 through 4.1.3; 4.0.0 through 4.0.18; 3.1.0 through 3.1.8.",
  "id": "GHSA-5x25-c2rf-f2jx",
  "modified": "2026-08-21T19:13:01Z",
  "published": "2026-06-11T09:31:56Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-40997"
    },
    {
      "type": "WEB",
      "url": "https://github.com/spring-projects/spring-ws/commit/5051fae1a836c4d7fa12dedebdca23494764e421"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/spring-projects/spring-ws"
    },
    {
      "type": "WEB",
      "url": "https://spring.io/security/cve-2026-40997"
    }
  ],
  "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"
    }
  ],
  "summary": "Spring Web Services: SOAP security faults leak Spring Security account state"
}

GHSA-5X86-XGVW-J25W

Vulnerability from github – Published: 2021-12-14 00:01 – Updated: 2023-04-20 18:30
VLAI
Details

An issue was discovered in /goform/login_process in Reprise RLM 14.2. When an attacker attempts to login, the response if a username is valid includes Login Failed, but does not include this string if the username is invalid. This allows an attacker to enumerate valid users.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2021-44155"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-209"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2021-12-13T04:15:00Z",
    "severity": "MODERATE"
  },
  "details": "An issue was discovered in /goform/login_process in Reprise RLM 14.2. When an attacker attempts to login, the response if a username is valid includes Login Failed, but does not include this string if the username is invalid. This allows an attacker to enumerate valid users.",
  "id": "GHSA-5x86-xgvw-j25w",
  "modified": "2023-04-20T18:30:49Z",
  "published": "2021-12-14T00:01:11Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2021-44155"
    },
    {
      "type": "WEB",
      "url": "https://reprisesoftware.com/admin/rlm-admin-download.php?\u0026euagree=yes"
    },
    {
      "type": "WEB",
      "url": "https://www.reprisesoftware.com/RELEASE_NOTES"
    },
    {
      "type": "WEB",
      "url": "http://packetstormsecurity.com/files/165182/Reprise-License-Manager-14.2-User-Enumeration.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"
    }
  ]
}

GHSA-6282-5CPC-5895

Vulnerability from github – Published: 2026-05-06 21:31 – Updated: 2026-05-06 21:31
VLAI
Details

HCL BigFix Service Management (SM) is vulnerable to information exposure due to improper error handling within its reporting module. It was observed that supplying an invalid or out-of-range value to the consumer_company parameter during a report-viewing request causes the application to trigger an unhandled exception.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2025-31960"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-209"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-05-06T19:16:35Z",
    "severity": "MODERATE"
  },
  "details": "HCL BigFix Service Management (SM) is vulnerable to information exposure due to improper error handling within its reporting module. It was observed that supplying an invalid or out-of-range value to the consumer_company parameter during a report-viewing request causes the application to trigger an unhandled exception.",
  "id": "GHSA-6282-5cpc-5895",
  "modified": "2026-05-06T21:31:36Z",
  "published": "2026-05-06T21:31:36Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-31960"
    },
    {
      "type": "WEB",
      "url": "https://support.hcl-software.com/csm?id=kb_article\u0026sysparm_article=KB0128144"
    }
  ],
  "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"
    }
  ]
}

GHSA-62J9-5XW8-8J5F

Vulnerability from github – Published: 2026-01-16 06:30 – Updated: 2026-01-16 06:30
VLAI
Details

The Fancy Product Designer plugin for WordPress is vulnerable to Full Path Disclosure in all versions up to, and including, 6.4.8. This is due to improper error handling in the PDF upload functionality that exposes server filesystem paths and stack traces in error messages. This makes it possible for unauthenticated attackers to retrieve the full path of the web application, which can be used to aid other attacks. The information displayed is not useful on its own, and requires another vulnerability to be present for damage to an affected website.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2025-15526"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-209"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-01-16T05:16:13Z",
    "severity": "MODERATE"
  },
  "details": "The Fancy Product Designer plugin for WordPress is vulnerable to Full Path Disclosure in all versions up to, and including, 6.4.8. This is due to improper error handling in the PDF upload functionality that exposes server filesystem paths and stack traces in error messages. This makes it possible for unauthenticated attackers to retrieve the full path of the web application, which can be used to aid other attacks. The information displayed is not useful on its own, and requires another vulnerability to be present for damage to an affected website.",
  "id": "GHSA-62j9-5xw8-8j5f",
  "modified": "2026-01-16T06:30:15Z",
  "published": "2026-01-16T06:30:15Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-15526"
    },
    {
      "type": "WEB",
      "url": "https://support.fancyproductdesigner.com/support/discussions/topics/13000036024"
    },
    {
      "type": "WEB",
      "url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/9b39b4ce-3885-4ea4-8cf0-84e66e7f6a12?source=cve"
    }
  ],
  "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"
    }
  ]
}

GHSA-62XX-CV5C-2CJF

Vulnerability from github – Published: 2022-11-01 12:00 – Updated: 2022-11-03 12:00
VLAI
Details

The application allowed for Unauthenticated User Enumeration by interacting with an unsecured endpoint to retrieve information on each account within the system.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2022-40292"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-209"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2022-10-31T21:15:00Z",
    "severity": "MODERATE"
  },
  "details": "The application allowed for Unauthenticated User Enumeration by interacting with an unsecured endpoint to retrieve information on each account within the system.",
  "id": "GHSA-62xx-cv5c-2cjf",
  "modified": "2022-11-03T12:00:28Z",
  "published": "2022-11-01T12:00:34Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2022-40292"
    },
    {
      "type": "WEB",
      "url": "https://www.themissinglink.com.au/security-advisories/cve-2022-40292"
    }
  ],
  "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"
    }
  ]
}

GHSA-65QP-579H-GFWC

Vulnerability from github – Published: 2025-02-21 06:31 – Updated: 2025-02-21 06:31
VLAI
Details

The C9 Blocks plugin for WordPress is vulnerable to Full Path Disclosure in all versions up to, and including, 1.7.7. This is due the plugin containing a publicly accessible composer-setup.php file with error display enabled. This makes it possible for unauthenticated attackers to retrieve the full path of the web application, which can be used to aid other attacks. The information displayed is not useful on its own, and requires another vulnerability to be present for damage to an affected website.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2024-13537"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-209"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-02-21T04:15:09Z",
    "severity": "MODERATE"
  },
  "details": "The C9 Blocks plugin for WordPress is vulnerable to Full Path Disclosure in all versions up to, and including, 1.7.7. This is due the plugin containing a publicly accessible composer-setup.php file with error display enabled. This makes it possible for unauthenticated attackers to retrieve the full path of the web application, which can be used to aid other attacks. The information displayed is not useful on its own, and requires another vulnerability to be present for damage to an affected website.",
  "id": "GHSA-65qp-579h-gfwc",
  "modified": "2025-02-21T06:31:09Z",
  "published": "2025-02-21T06:31:09Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-13537"
    },
    {
      "type": "WEB",
      "url": "https://plugins.trac.wordpress.org/browser/c9-blocks/trunk/composer-setup.php"
    },
    {
      "type": "WEB",
      "url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/e3e682fb-e821-45cb-a087-d97d42a3743e?source=cve"
    }
  ],
  "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"
    }
  ]
}

GHSA-6938-R83G-5RJP

Vulnerability from github – Published: 2025-04-16 18:31 – Updated: 2025-04-16 18:31
VLAI
Details

A vulnerability in Cisco Nexus Dashboard could allow an unauthenticated, remote attacker to enumerate LDAP user accounts.

This vulnerability is due to the improper handling of LDAP authentication requests. An attacker could exploit this vulnerability by sending authentication requests to an affected system. A successful exploit could allow an attacker to determine which usernames are valid LDAP user accounts.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2025-20150"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-209"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-04-16T16:15:29Z",
    "severity": "MODERATE"
  },
  "details": "A vulnerability in Cisco Nexus Dashboard could allow an unauthenticated, remote attacker to enumerate LDAP user accounts.\n\nThis vulnerability is due to the improper handling of LDAP authentication requests. An attacker could exploit this vulnerability by sending authentication requests to an affected system. A successful exploit could allow an attacker to determine which usernames are valid LDAP user accounts.",
  "id": "GHSA-6938-r83g-5rjp",
  "modified": "2025-04-16T18:31:50Z",
  "published": "2025-04-16T18:31:50Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-20150"
    },
    {
      "type": "WEB",
      "url": "https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-nd-unenum-2xFFh472"
    }
  ],
  "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"
    }
  ]
}

GHSA-69JC-R7P8-4CPG

Vulnerability from github – Published: 2024-02-29 00:30 – Updated: 2025-02-14 18:30
VLAI
Details

Hitachi Vantara Pentaho Data Integration & Analytics versions before 10.1.0.0 and 9.3.0.6, including 9.5.x and 8.3.x, display the version of Tomcat when a server error is encountered.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2023-5617"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-209",
      "CWE-550"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2024-02-28T23:15:08Z",
    "severity": "MODERATE"
  },
  "details": "Hitachi Vantara Pentaho Data Integration \u0026 Analytics versions before 10.1.0.0 and 9.3.0.6, including\u00a09.5.x and 8.3.x, display the version of Tomcat when a server error is encountered.",
  "id": "GHSA-69jc-r7p8-4cpg",
  "modified": "2025-02-14T18:30:43Z",
  "published": "2024-02-29T00:30:23Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-5617"
    },
    {
      "type": "WEB",
      "url": "https://support.pentaho.com/hc/en-us/articles/24313358254861--Resolved-Hitachi-Vantara-Pentaho-Data-Integration-Analytics-Server-generated-Error-Message-Containing-Sensitive-Information-Versions-before-10-1-0-0-and-9-3-0-6-including-all-versions-before-10-0-x-Impacted-CVE-2023-5617"
    }
  ],
  "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"
    }
  ]
}

GHSA-6F9W-9HF2-5RG3

Vulnerability from github – Published: 2026-09-03 14:49 – Updated: 2026-09-03 14:49
VLAI
Summary
CKAN MCP Server: Information disclosure via verbose error reflection
Details

Summary

Error paths reflect raw upstream response bodies and internal exception messages back to the caller instead of a sanitized, generic message. When the server is pointed at (or redirected/SSRF'd to) a host that returns a non-CKAN response, or when an internal exception occurs, the caller receives verbatim upstream content and internal detail (hostnames, internal IPs, DB errors, stack fragments).

Affected code

src/utils/http.ts — the entire decoded upstream body is embedded in the thrown error, which formatCkanError returns to the tool result:

} else {
  throw new CkanApiError(
    `CKAN API returned success=false: ${JSON.stringify(decodedData)}`,   // full body reflected
    undefined,
    action
  );
}

src/worker.ts — the catch-all handler returns the raw Error.message in the JSON-RPC data field:

return new Response(JSON.stringify({
  jsonrpc: '2.0',
  error: { code: -32603, message: 'Internal error',
           data: error instanceof Error ? error.message : String(error) },  // raw internal message
  id: null
}), { status: 500, ... });

Impact

  • Reflects arbitrary upstream response content to the caller. Combined with the SSRF vectors (advisories #01/#06), an attacker can use this as the read channel: point the server at an internal endpoint and receive its body inside the success=false error string (turning otherwise-blind SSRF into a semi-blind/return-value SSRF for any host that reaches the guards).
  • Leaks internal operational detail via exception messages: node error codes and target addresses (e.g. ECONNREFUSED 169.254.169.254:80), which confirm internal reachability and infrastructure, and any stack/path fragments an upstream includes.
  • Aids reconnaissance and error-oracle attacks against the deployment.

Severity is Low on its own (the server holds no credentials of its own and sends no auth upstream), but it meaningfully amplifies the SSRF findings by providing a response-content channel.

Proof of concept

poc/error-disclosure-poc.mjs reproduces both paths and shows an upstream body (containing a simulated DB error with an internal IP) and an internal ECONNREFUSED 169.254.169.254 message being reflected to the caller.

Remediation

  • Return generic, action-scoped error messages to the caller; log the detailed upstream body/exception server-side only.
  • Do not embed JSON.stringify(decodedData) in caller-visible errors; cap and redact any reflected content.
  • In the Workers catch-all, omit error.message from the response data (or replace with a correlation id) in production.
Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "npm",
        "name": "@aborruso/ckan-mcp-server"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "0.4.112"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-73844"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-209",
      "CWE-210"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-09-03T14:49:10Z",
    "nvd_published_at": "2026-08-14T17:20:36Z",
    "severity": "LOW"
  },
  "details": "## Summary\n\nError paths reflect raw upstream response bodies and internal exception messages back to the caller instead of a sanitized, generic message. When the server is pointed at (or redirected/SSRF\u0027d to) a host that returns a non-CKAN response, or when an internal exception occurs, the caller receives verbatim upstream content and internal detail (hostnames, internal IPs, DB errors, stack fragments).\n\n## Affected code\n\n`src/utils/http.ts` \u2014 the entire decoded upstream body is embedded in the thrown error, which `formatCkanError` returns to the tool result:\n\n```js\n} else {\n  throw new CkanApiError(\n    `CKAN API returned success=false: ${JSON.stringify(decodedData)}`,   // full body reflected\n    undefined,\n    action\n  );\n}\n```\n\n`src/worker.ts` \u2014 the catch-all handler returns the raw `Error.message` in the JSON-RPC `data` field:\n\n```js\nreturn new Response(JSON.stringify({\n  jsonrpc: \u00272.0\u0027,\n  error: { code: -32603, message: \u0027Internal error\u0027,\n           data: error instanceof Error ? error.message : String(error) },  // raw internal message\n  id: null\n}), { status: 500, ... });\n```\n\n## Impact\n\n- Reflects arbitrary upstream response content to the caller. Combined with the SSRF vectors (advisories #01/#06), an attacker can use this as the *read* channel: point the server at an internal endpoint and receive its body inside the `success=false` error string (turning otherwise-blind SSRF into a semi-blind/return-value SSRF for any host that reaches the guards).\n- Leaks internal operational detail via exception messages: node error codes and target addresses (e.g. `ECONNREFUSED 169.254.169.254:80`), which confirm internal reachability and infrastructure, and any stack/path fragments an upstream includes.\n- Aids reconnaissance and error-oracle attacks against the deployment.\n\nSeverity is Low on its own (the server holds no credentials of its own and sends no auth upstream), but it meaningfully amplifies the SSRF findings by providing a response-content channel.\n\n## Proof of concept\n\n`poc/error-disclosure-poc.mjs` reproduces both paths and shows an upstream body\n(containing a simulated DB error with an internal IP) and an internal\n`ECONNREFUSED 169.254.169.254` message being reflected to the caller.\n\n## Remediation\n\n- Return generic, action-scoped error messages to the caller; log the detailed\n  upstream body/exception server-side only.\n- Do not embed `JSON.stringify(decodedData)` in caller-visible errors; cap and\n  redact any reflected content.\n- In the Workers catch-all, omit `error.message` from the response `data` (or\n  replace with a correlation id) in production.",
  "id": "GHSA-6f9w-9hf2-5rg3",
  "modified": "2026-09-03T14:49:10Z",
  "published": "2026-09-03T14:49:10Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/ondata/ckan-mcp-server/security/advisories/GHSA-6f9w-9hf2-5rg3"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-73844"
    },
    {
      "type": "WEB",
      "url": "https://github.com/ondata/ckan-mcp-server/commit/3b827af72b228d42aa7b0d7dac5347d16af3f4e5"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/ondata/ckan-mcp-server"
    },
    {
      "type": "WEB",
      "url": "https://github.com/ondata/ckan-mcp-server/releases/tag/v0.4.112"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "CKAN MCP Server: Information disclosure via verbose error reflection"
}

Mitigation MIT-39
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.
Mitigation
Implementation

Handle exceptions internally and do not display errors containing potentially sensitive information to a user.

Mitigation MIT-33
Implementation

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
Implementation Build and Compilation

Strategy: Compilation or Build Hardening

Debugging information should not make its way into a production release.

Mitigation MIT-40
Implementation Build and Compilation

Strategy: Environment Hardening

Debugging information should not make its way into a production release.

Mitigation
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.

Mitigation
System Configuration

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.