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.
919 vulnerabilities reference this CWE, most recent first.
GHSA-6938-R83G-5RJP
Vulnerability from github – Published: 2025-04-16 18:31 – Updated: 2025-04-16 18:31A 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.
{
"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:30Hitachi 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.
{
"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:49Summary
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=falseerror 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.messagefrom the responsedata(or replace with a correlation id) in production.
{
"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"
}
GHSA-6G23-6JW5-9VRF
Vulnerability from github – Published: 2022-05-24 17:33 – Updated: 2022-05-24 17:33PackageKit provided detailed error messages to unprivileged callers that exposed information about file presence and mimetype of files that the user would be unable to determine on its own.
{
"affected": [],
"aliases": [
"CVE-2020-16121"
],
"database_specific": {
"cwe_ids": [
"CWE-209"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2020-11-07T04:15:00Z",
"severity": "LOW"
},
"details": "PackageKit provided detailed error messages to unprivileged callers that exposed information about file presence and mimetype of files that the user would be unable to determine on its own.",
"id": "GHSA-6g23-6jw5-9vrf",
"modified": "2022-05-24T17:33:24Z",
"published": "2022-05-24T17:33:24Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-16121"
},
{
"type": "WEB",
"url": "https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1888887"
},
{
"type": "WEB",
"url": "https://www.eyecontrol.nl/blog/the-story-of-3-cves-in-ubuntu-desktop.html"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-6G9V-7GQ3-P2C6
Vulnerability from github – Published: 2026-07-01 20:16 – Updated: 2026-09-04 20:07A record user with UPDATE access could read field values that field-level SELECT permissions hid from them. Arithmetic operators and extend embedded the raw operand into their error messages, and UPDATE permission checks evaluate against the unreduced document — so triggering such an error against a hidden field returned its value in the resulting error.
Impact
A record user issues an UPDATE that performs an incompatible operation against a hidden field — e.g. UPDATE person:me SET probe = email + 1 when email is a string — and reads the value from the returned error (Tried to compute "alice@example.com" + 1 …). One field per operation, but the attacker can repeat against any field on any record they can UPDATE.
Patches
A patch has been introduced that replaces the raw operand in every try_* operator and in extend with the operand's type name ("string", "int", "array", etc.).
- Versions 3.1.0 and later are not affected by this issue.
Workarounds
Affected users who are unable to update should not grant UPDATE permission on records whose field-level SELECT permissions are expected to hide values from the same caller.
{
"affected": [
{
"package": {
"ecosystem": "crates.io",
"name": "surrealdb"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3.1.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-63748"
],
"database_specific": {
"cwe_ids": [
"CWE-209"
],
"github_reviewed": true,
"github_reviewed_at": "2026-07-01T20:16:52Z",
"nvd_published_at": null,
"severity": "MODERATE"
},
"details": "A record user with UPDATE access could read field values that field-level SELECT permissions hid from them. Arithmetic operators and `extend` embedded the raw operand into their error messages, and UPDATE permission checks evaluate against the unreduced document \u2014 so triggering such an error against a hidden field returned its value in the resulting error.\n\n### Impact\n\nA record user issues an UPDATE that performs an incompatible operation against a hidden field \u2014 e.g. `UPDATE person:me SET probe = email + 1` when `email` is a string \u2014 and reads the value from the returned error (`Tried to compute \"alice@example.com\" + 1 \u2026`). One field per operation, but the attacker can repeat against any field on any record they can UPDATE.\n\n### Patches\n\nA patch has been introduced that replaces the raw operand in every `try_*` operator and in `extend` with the operand\u0027s type name (`\"string\"`, `\"int\"`, `\"array\"`, etc.).\n\n- Versions 3.1.0 and later are not affected by this issue.\n\n### Workarounds\n\nAffected users who are unable to update should not grant UPDATE permission on records whose field-level SELECT permissions are expected to hide values from the same caller.",
"id": "GHSA-6g9v-7gq3-p2c6",
"modified": "2026-09-04T20:07:40Z",
"published": "2026-07-01T20:16:52Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/surrealdb/surrealdb/security/advisories/GHSA-6g9v-7gq3-p2c6"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-63748"
},
{
"type": "WEB",
"url": "https://github.com/surrealdb/surrealdb/commit/0aaa332c79195e4c40275eb5224aed3d52f5cf90"
},
{
"type": "PACKAGE",
"url": "https://github.com/surrealdb/surrealdb"
},
{
"type": "WEB",
"url": "https://www.vulncheck.com/advisories/surrealdb-before-information-disclosure-via-error-messages"
}
],
"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"
}
],
"summary": "SurrealDB: Authenticated callers can read fields hidden by field-level SELECT permissions via error messages"
}
GHSA-6HF3-MHGC-CM65
Vulnerability from github – Published: 2026-02-18 22:43 – Updated: 2026-02-20 16:47Vulnerability
In some shared-agent deployments, OpenClaw session tools (sessions_list, sessions_history, sessions_send) allowed broader session targeting than some operators intended. This is primarily a configuration/visibility-scoping issue in multi-user environments where peers are not equally trusted.
In Telegram webhook mode, monitor startup also did not fall back to per-account webhookSecret when only the account-level secret was configured.
Typical Use Case Context
Most regular OpenClaw deployments run a single agent, or run in trusted environments. In those setups, practical risk from this issue is generally low.
Impact
- Shared-agent, multi-user, less-trusted environments: session-tool access could expose transcript content across peer sessions.
- Single-agent or trusted environments: practical impact is limited.
- Telegram webhook mode: account-level secret wiring could be missed unless an explicit monitor webhook secret override was provided.
Affected Packages / Versions
- Package: npm
openclaw - Affected versions:
<= 2026.2.14 - Patched version:
2026.2.15(planned next release)
Remediation
- Add and enforce
tools.sessions.visibility(self | tree | agent | all) across session tools, defaulting totree. - Keep sandbox clamping behavior so sandboxed runs can be restricted to spawned/session-tree visibility.
- Resolve Telegram webhook secret from account config fallback in monitor webhook startup.
Fix Commit(s)
c6c53437f7da033b94a01d492e904974e7bda74c
Thanks @aether-ai-agent for reporting.
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "openclaw"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2026.2.15"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-27004"
],
"database_specific": {
"cwe_ids": [
"CWE-209",
"CWE-346"
],
"github_reviewed": true,
"github_reviewed_at": "2026-02-18T22:43:53Z",
"nvd_published_at": "2026-02-20T00:16:17Z",
"severity": "MODERATE"
},
"details": "## Vulnerability\n\nIn some shared-agent deployments, OpenClaw session tools (`sessions_list`, `sessions_history`, `sessions_send`) allowed broader session targeting than some operators intended. This is primarily a configuration/visibility-scoping issue in multi-user environments where peers are not equally trusted.\n\nIn Telegram webhook mode, monitor startup also did not fall back to per-account `webhookSecret` when only the account-level secret was configured.\n\n## Typical Use Case Context\n\nMost regular OpenClaw deployments run a single agent, or run in trusted environments. In those setups, practical risk from this issue is generally low.\n\n## Impact\n\n- Shared-agent, multi-user, less-trusted environments: session-tool access could expose transcript content across peer sessions.\n- Single-agent or trusted environments: practical impact is limited.\n- Telegram webhook mode: account-level secret wiring could be missed unless an explicit monitor webhook secret override was provided.\n\n## Affected Packages / Versions\n\n- Package: npm `openclaw`\n- Affected versions: `\u003c= 2026.2.14`\n- Patched version: `2026.2.15` (planned next release)\n\n## Remediation\n\n- Add and enforce `tools.sessions.visibility` (`self | tree | agent | all`) across session tools, defaulting to `tree`.\n- Keep sandbox clamping behavior so sandboxed runs can be restricted to spawned/session-tree visibility.\n- Resolve Telegram webhook secret from account config fallback in monitor webhook startup.\n\n## Fix Commit(s)\n\n- `c6c53437f7da033b94a01d492e904974e7bda74c`\n\nThanks @aether-ai-agent for reporting.",
"id": "GHSA-6hf3-mhgc-cm65",
"modified": "2026-02-20T16:47:17Z",
"published": "2026-02-18T22:43:53Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/openclaw/openclaw/security/advisories/GHSA-6hf3-mhgc-cm65"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-27004"
},
{
"type": "WEB",
"url": "https://github.com/openclaw/openclaw/commit/c6c53437f7da033b94a01d492e904974e7bda74c"
},
{
"type": "PACKAGE",
"url": "https://github.com/openclaw/openclaw"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N",
"type": "CVSS_V4"
}
],
"summary": "OpenClaw session tool visibility hardening and Telegram webhook secret fallback"
}
GHSA-6J36-R33Q-6MRW
Vulnerability from github – Published: 2025-12-18 21:31 – Updated: 2025-12-18 21:31An information disclosure vulnerability in Kentico Xperience allows attackers to view sensitive stack trace details via Portal Engine form control error messages. Detailed error messages can expose internal system information and potentially reveal implementation details to unauthorized users.
{
"affected": [],
"aliases": [
"CVE-2022-50686"
],
"database_specific": {
"cwe_ids": [
"CWE-209"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-12-18T20:15:50Z",
"severity": "MODERATE"
},
"details": "An information disclosure vulnerability in Kentico Xperience allows attackers to view sensitive stack trace details via Portal Engine form control error messages. Detailed error messages can expose internal system information and potentially reveal implementation details to unauthorized users.",
"id": "GHSA-6j36-r33q-6mrw",
"modified": "2025-12-18T21:31:43Z",
"published": "2025-12-18T21:31:43Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-50686"
},
{
"type": "WEB",
"url": "https://devnet.kentico.com/download/hotfixes"
},
{
"type": "WEB",
"url": "https://www.vulncheck.com/advisories/kentico-xperience-portal-engine-form-control-information-disclosure"
}
],
"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"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
"type": "CVSS_V4"
}
]
}
GHSA-6J3G-2JH3-Q8RG
Vulnerability from github – Published: 2026-01-13 18:31 – Updated: 2026-01-13 18:31Generation of error message containing sensitive information in Windows Kernel allows an authorized attacker to disclose information locally.
{
"affected": [],
"aliases": [
"CVE-2026-20838"
],
"database_specific": {
"cwe_ids": [
"CWE-209"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-01-13T18:16:12Z",
"severity": "MODERATE"
},
"details": "Generation of error message containing sensitive information in Windows Kernel allows an authorized attacker to disclose information locally.",
"id": "GHSA-6j3g-2jh3-q8rg",
"modified": "2026-01-13T18:31:09Z",
"published": "2026-01-13T18:31:09Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-20838"
},
{
"type": "WEB",
"url": "https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-20838"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-6J45-CC69-5JV8
Vulnerability from github – Published: 2022-05-13 01:50 – Updated: 2022-05-13 01:50Artifex Ghostscript 9.25 and earlier allows attackers to bypass a sandbox protection mechanism via vectors involving errorhandler setup. NOTE: this issue exists because of an incomplete fix for CVE-2018-17183.
{
"affected": [],
"aliases": [
"CVE-2018-17961"
],
"database_specific": {
"cwe_ids": [
"CWE-209"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2018-10-15T16:29:00Z",
"severity": "HIGH"
},
"details": "Artifex Ghostscript 9.25 and earlier allows attackers to bypass a sandbox protection mechanism via vectors involving errorhandler setup. NOTE: this issue exists because of an incomplete fix for CVE-2018-17183.",
"id": "GHSA-6j45-cc69-5jv8",
"modified": "2022-05-13T01:50:35Z",
"published": "2022-05-13T01:50:35Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2018-17961"
},
{
"type": "WEB",
"url": "https://access.redhat.com/errata/RHSA-2018:3834"
},
{
"type": "WEB",
"url": "https://bugs.chromium.org/p/project-zero/issues/detail?id=1682\u0026desc=2"
},
{
"type": "WEB",
"url": "https://bugs.ghostscript.com/show_bug.cgi?id=699816"
},
{
"type": "WEB",
"url": "https://lists.debian.org/debian-lts-announce/2018/10/msg00013.html"
},
{
"type": "WEB",
"url": "https://usn.ubuntu.com/3803-1"
},
{
"type": "WEB",
"url": "https://www.debian.org/security/2018/dsa-4336"
},
{
"type": "WEB",
"url": "https://www.exploit-db.com/exploits/45573"
},
{
"type": "WEB",
"url": "http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=a54c9e61e7d0"
},
{
"type": "WEB",
"url": "http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=a5a9bf8c6a63"
},
{
"type": "WEB",
"url": "http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=a6807394bd94"
},
{
"type": "WEB",
"url": "http://www.openwall.com/lists/oss-security/2018/10/09/4"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-6JV7-GP56-RQ3M
Vulnerability from github – Published: 2026-02-04 21:30 – Updated: 2026-02-04 21:30IBM Cloud Pak System does not set the secure attribute on authorization tokens or session cookies. Attackers may be able to get the cookie values by sending a http:// link to a user or by planting this link in a site the user goes to. The cookie will be sent to the insecure link and the attacker can then obtain the cookie value by snooping the traffic.
{
"affected": [],
"aliases": [
"CVE-2023-38281"
],
"database_specific": {
"cwe_ids": [
"CWE-209"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-02-04T21:15:56Z",
"severity": "MODERATE"
},
"details": "IBM Cloud Pak System does not set the secure attribute on authorization tokens or session cookies. Attackers may be able to get the cookie values by sending a http:// link to a user or by planting this link in a site the user goes to. The cookie will be sent to the insecure link and the attacker can then obtain the cookie value by snooping the traffic.",
"id": "GHSA-6jv7-gp56-rq3m",
"modified": "2026-02-04T21:30:32Z",
"published": "2026-02-04T21:30:32Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-38281"
},
{
"type": "WEB",
"url": "https://www.ibm.com/support/pages/node/7254419"
}
],
"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.