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.
833 vulnerabilities reference this CWE, most recent first.
GHSA-J5JJ-CV4X-3RPR
Vulnerability from github – Published: 2022-05-24 19:07 – Updated: 2022-05-24 19:07A vulnerability has been identified in Teamcenter Active Workspace V4 (All versions < V4.3.9), Teamcenter Active Workspace V5.0 (All versions < V5.0.7), Teamcenter Active Workspace V5.1 (All versions < V5.1.4). The affected application allows verbose error messages which allow leaking of sensitive information, such as full paths.
{
"affected": [],
"aliases": [
"CVE-2021-33711"
],
"database_specific": {
"cwe_ids": [
"CWE-209"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2021-07-13T11:15:00Z",
"severity": "MODERATE"
},
"details": "A vulnerability has been identified in Teamcenter Active Workspace V4 (All versions \u003c V4.3.9), Teamcenter Active Workspace V5.0 (All versions \u003c V5.0.7), Teamcenter Active Workspace V5.1 (All versions \u003c V5.1.4). The affected application allows verbose error messages which allow leaking of sensitive information, such as full paths.",
"id": "GHSA-j5jj-cv4x-3rpr",
"modified": "2022-05-24T19:07:43Z",
"published": "2022-05-24T19:07:43Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-33711"
},
{
"type": "WEB",
"url": "https://cert-portal.siemens.com/productcert/pdf/ssa-622535.pdf"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-J64J-2VJ4-M2M8
Vulnerability from github – Published: 2024-10-30 09:30 – Updated: 2026-04-01 18:32Generation of Error Message Containing Sensitive Information vulnerability in Posti Posti Shipping allows Retrieve Embedded Sensitive Data.This issue affects Posti Shipping: from n/a through 3.10.2.
{
"affected": [],
"aliases": [
"CVE-2024-50512"
],
"database_specific": {
"cwe_ids": [
"CWE-209"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-10-30T08:15:04Z",
"severity": "MODERATE"
},
"details": "Generation of Error Message Containing Sensitive Information vulnerability in Posti Posti Shipping allows Retrieve Embedded Sensitive Data.This issue affects Posti Shipping: from n/a through 3.10.2.",
"id": "GHSA-j64j-2vj4-m2m8",
"modified": "2026-04-01T18:32:15Z",
"published": "2024-10-30T09:30:48Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-50512"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/Wordpress/Plugin/posti-shipping/vulnerability/wordpress-posti-shipping-plugin-3-10-2-full-path-disclosure-fpd-vulnerability?_s_id=cve"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/vulnerability/posti-shipping/wordpress-posti-shipping-plugin-3-10-2-full-path-disclosure-fpd-vulnerability?_s_id=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-J654-GF62-FHPJ
Vulnerability from github – Published: 2022-05-24 16:47 – Updated: 2023-02-03 21:30IBM InfoSphere Information Server 11.5 and 11.7 is affected by an information disclosure vulnerability. Sensitive information in an error message may be used to conduct further attacks against the system. IBM X-Force ID: 159945.
{
"affected": [],
"aliases": [
"CVE-2019-4257"
],
"database_specific": {
"cwe_ids": [
"CWE-209"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2019-06-06T21:29:00Z",
"severity": "MODERATE"
},
"details": "IBM InfoSphere Information Server 11.5 and 11.7 is affected by an information disclosure vulnerability. Sensitive information in an error message may be used to conduct further attacks against the system. IBM X-Force ID: 159945.",
"id": "GHSA-j654-gf62-fhpj",
"modified": "2023-02-03T21:30:26Z",
"published": "2022-05-24T16:47:30Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2019-4257"
},
{
"type": "WEB",
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/159945"
},
{
"type": "WEB",
"url": "https://www.ibm.com/support/docview.wss?uid=ibm10882478"
}
],
"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-J6R3-VQ2C-4GHW
Vulnerability from github – Published: 2023-10-16 21:30 – Updated: 2024-04-04 08:42The Defender Security WordPress plugin before 4.1.0 does not prevent redirects to the login page via the auth_redirect WordPress function, allowing an unauthenticated visitor to access the login page, even when the hide login page functionality of the plugin is enabled.
{
"affected": [],
"aliases": [
"CVE-2023-5089"
],
"database_specific": {
"cwe_ids": [
"CWE-209"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-10-16T20:15:17Z",
"severity": "MODERATE"
},
"details": "The Defender Security WordPress plugin before 4.1.0 does not prevent redirects to the login page via the auth_redirect WordPress function, allowing an unauthenticated visitor to access the login page, even when the hide login page functionality of the plugin is enabled.",
"id": "GHSA-j6r3-vq2c-4ghw",
"modified": "2024-04-04T08:42:02Z",
"published": "2023-10-16T21:30:27Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-5089"
},
{
"type": "WEB",
"url": "https://wpscan.com/vulnerability/2b547488-187b-44bc-a57d-f876a7d4c87d"
},
{
"type": "WEB",
"url": "https://www.sprocketsecurity.com/resources/discovering-wp-admin-urls-in-wordpress-with-gravityforms"
}
],
"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-J8MX-J73W-9MXW
Vulnerability from github – Published: 2026-05-19 12:31 – Updated: 2026-06-04 18:38A possible information disclosure vulnerability exists in the Vaadin Maven plugin and Vaadin Gradle plugin that exposes the full set of environment variables in build logs whenever the frontend build process exits with a non-zero status. Because the build environment may contain credentials supplied as secrets, any failed frontend build can expose those secrets in clear text in CI logs and archived build artifacts.
Users of affected versions should apply the following mitigation or upgrade. Releases that have fixed this issue include:
| Product version | Mitigation |
|---|---|
Vaadin 23.0.0 - 23.6.10 |
Upgrade to 23.6.11 |
Vaadin 24.0.0 - 24.9.17 |
Upgrade to 24.9.18 |
Vaadin 24.10.0 - 24.10.3 |
Upgrade to 24.10.4 |
Vaadin 25.0.0 - 25.0.11 |
Upgrade to 25.0.12 |
Vaadin 25.1.0 - 25.1.4 |
Upgrade to 25.1.5 or newer |
Please note that Vaadin versions 10-13 and 15-22 are no longer supported and you should update either to the latest 23, 24, or 25 version.
| Maven coordinates | Vulnerable version | Fixed version |
|---|---|---|
com.vaadin:flow-plugin-base |
23.0.0 - 23.6.10 |
≥ 23.6.11 |
com.vaadin:flow-plugin-base |
24.0.0 - 24.9.17 |
≥ 24.9.18 |
com.vaadin:flow-plugin-base |
24.0.0 - 24.10.3 |
≥ 24.10.4 |
com.vaadin:flow-plugin-base |
25.0.0 - 25.0.11 |
≥ 25.0.12 |
com.vaadin:flow-plugin-base |
25.1.0 - 25.1.4 |
≥ 25.1.5 |
com.vaadin:flow-maven-plugin |
23.0.0 - 23.6.10 |
≥ 23.6.11 |
com.vaadin:flow-maven-plugin |
24.0.0 - 24.9.17 |
≥ 24.9.18 |
com.vaadin:flow-maven-plugin |
24.0.0 - 24.10.3 |
≥ 24.10.4 |
com.vaadin:flow-maven-plugin |
25.0.0 - 25.0.11 |
≥ 25.0.12 |
com.vaadin:flow-maven-plugin |
25.1.0 - 25.1.4 |
≥ 25.1.5 |
com.vaadin:flow-gradle-plugin |
24.0.0 - 24.9.17 |
≥ 24.9.18 |
com.vaadin:flow-gradle-plugin |
24.0.0 - 24.10.3 |
≥ 24.10.4 |
com.vaadin:flow-gradle-plugin |
25.0.0 - 25.0.11 |
≥ 25.0.12 |
com.vaadin:flow-gradle-plugin |
25.1.0 - 25.1.4 |
≥ 25.1.5 |
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c 23.6.10"
},
"package": {
"ecosystem": "Maven",
"name": "com.vaadin:flow-plugins"
},
"ranges": [
{
"events": [
{
"introduced": "23.0.0"
},
{
"fixed": "23.6.11"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"database_specific": {
"last_known_affected_version_range": "\u003c 24.9.17"
},
"package": {
"ecosystem": "Maven",
"name": "com.vaadin:flow-plugins"
},
"ranges": [
{
"events": [
{
"introduced": "24.0.0"
},
{
"fixed": "24.9.18"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Maven",
"name": "com.vaadin:flow-plugins"
},
"ranges": [
{
"events": [
{
"introduced": "24.10.0"
},
{
"fixed": "24.10.4"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"database_specific": {
"last_known_affected_version_range": "\u003c 25.0.11"
},
"package": {
"ecosystem": "Maven",
"name": "com.vaadin:flow-plugins"
},
"ranges": [
{
"events": [
{
"introduced": "25.0.0"
},
{
"fixed": "25.0.12"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Maven",
"name": "com.vaadin:flow-plugins"
},
"ranges": [
{
"events": [
{
"introduced": "25.1.0"
},
{
"fixed": "25.1.5"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"database_specific": {
"last_known_affected_version_range": "\u003c 23.6.10"
},
"package": {
"ecosystem": "Maven",
"name": "com.vaadin:flow-maven-plugin"
},
"ranges": [
{
"events": [
{
"introduced": "23.0.0"
},
{
"fixed": "23.6.11"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"database_specific": {
"last_known_affected_version_range": "\u003c 24.9.17"
},
"package": {
"ecosystem": "Maven",
"name": "com.vaadin:flow-maven-plugin"
},
"ranges": [
{
"events": [
{
"introduced": "24.0.0"
},
{
"fixed": "24.9.18"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Maven",
"name": "com.vaadin:flow-maven-plugin"
},
"ranges": [
{
"events": [
{
"introduced": "24.10.0"
},
{
"fixed": "24.10.4"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"database_specific": {
"last_known_affected_version_range": "\u003c 25.0.11"
},
"package": {
"ecosystem": "Maven",
"name": "com.vaadin:flow-maven-plugin"
},
"ranges": [
{
"events": [
{
"introduced": "25.0.0"
},
{
"fixed": "25.0.12"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Maven",
"name": "com.vaadin:flow-maven-plugin"
},
"ranges": [
{
"events": [
{
"introduced": "25.1.0"
},
{
"fixed": "25.1.5"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"database_specific": {
"last_known_affected_version_range": "\u003c 24.9.17"
},
"package": {
"ecosystem": "Maven",
"name": "com.vaadin:flow-gradle-plugin"
},
"ranges": [
{
"events": [
{
"introduced": "24.0.0"
},
{
"fixed": "24.9.18"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Maven",
"name": "com.vaadin:flow-gradle-plugin"
},
"ranges": [
{
"events": [
{
"introduced": "24.10.0"
},
{
"fixed": "24.10.4"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"database_specific": {
"last_known_affected_version_range": "\u003c 25.0.11"
},
"package": {
"ecosystem": "Maven",
"name": "com.vaadin:flow-gradle-plugin"
},
"ranges": [
{
"events": [
{
"introduced": "25.0.0"
},
{
"fixed": "25.0.12"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Maven",
"name": "com.vaadin:flow-gradle-plugin"
},
"ranges": [
{
"events": [
{
"introduced": "25.1.0"
},
{
"fixed": "25.1.5"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-7860"
],
"database_specific": {
"cwe_ids": [
"CWE-209"
],
"github_reviewed": true,
"github_reviewed_at": "2026-06-04T18:38:34Z",
"nvd_published_at": "2026-05-19T12:16:19Z",
"severity": "LOW"
},
"details": "A possible information disclosure vulnerability exists in the Vaadin Maven plugin and Vaadin Gradle plugin that exposes the full set of environment variables in build logs whenever the frontend build process exits with a non-zero status. Because the build environment may contain credentials supplied as secrets, any failed frontend build can expose those secrets in clear text in CI logs and archived build artifacts.\n\n\nUsers of affected versions should apply the following mitigation or upgrade. Releases that have fixed this issue include:\n\n\n| Product version | Mitigation |\n|---|---|\n| `Vaadin 23.0.0 - 23.6.10` | `Upgrade to 23.6.11` |\n| `Vaadin 24.0.0 - 24.9.17` | `Upgrade to 24.9.18` |\n| `Vaadin 24.10.0 - 24.10.3` | `Upgrade to 24.10.4` |\n| `Vaadin 25.0.0 - 25.0.11` | `Upgrade to 25.0.12` |\n| `Vaadin 25.1.0 - 25.1.4` | `Upgrade to 25.1.5 or newer` |\n\nPlease note that Vaadin versions 10-13 and 15-22 are no longer supported and you should update either to the latest 23, 24, or 25 version.\n\n| Maven coordinates | Vulnerable version | Fixed version |\n|---|---|---|\n| `com.vaadin:flow-plugin-base` | `23.0.0 - 23.6.10` | `\u2265 23.6.11` |\n| `com.vaadin:flow-plugin-base` | `24.0.0 - 24.9.17` | `\u2265 24.9.18` |\n| `com.vaadin:flow-plugin-base` | `24.0.0 - 24.10.3` | `\u2265 24.10.4` |\n| `com.vaadin:flow-plugin-base` | `25.0.0 - 25.0.11` | `\u2265 25.0.12` |\n| `com.vaadin:flow-plugin-base` | `25.1.0 - 25.1.4` | `\u2265 25.1.5` |\n| `com.vaadin:flow-maven-plugin` | `23.0.0 - 23.6.10` | `\u2265 23.6.11` |\n| `com.vaadin:flow-maven-plugin` | `24.0.0 - 24.9.17` | `\u2265 24.9.18` |\n| `com.vaadin:flow-maven-plugin` | `24.0.0 - 24.10.3` | `\u2265 24.10.4` |\n| `com.vaadin:flow-maven-plugin` | `25.0.0 - 25.0.11` | `\u2265 25.0.12` |\n| `com.vaadin:flow-maven-plugin` | `25.1.0 - 25.1.4` | `\u2265 25.1.5` |\n| `com.vaadin:flow-gradle-plugin` | `24.0.0 - 24.9.17` | `\u2265 24.9.18` |\n| `com.vaadin:flow-gradle-plugin` | `24.0.0 - 24.10.3` | `\u2265 24.10.4` |\n| `com.vaadin:flow-gradle-plugin` | `25.0.0 - 25.0.11` | `\u2265 25.0.12` |\n| `com.vaadin:flow-gradle-plugin` | `25.1.0 - 25.1.4` | `\u2265 25.1.5` |",
"id": "GHSA-j8mx-j73w-9mxw",
"modified": "2026-06-04T18:38:34Z",
"published": "2026-05-19T12:31:42Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-7860"
},
{
"type": "WEB",
"url": "https://github.com/vaadin/flow/pull/24219"
},
{
"type": "PACKAGE",
"url": "https://github.com/vaadin/flow"
},
{
"type": "WEB",
"url": "https://vaadin.com/security/cve-2026-7860"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:P/VC:H/VI:N/VA:N/SC:H/SI:H/SA:N/E:U/S:N/AU:N/R:A/V:C/RE:L/U:Green",
"type": "CVSS_V4"
}
],
"summary": "Vaadin Build Plugins is Affected by a Possible Information Disclosure Vulnerability"
}
GHSA-J9V2-2X9X-CMCF
Vulnerability from github – Published: 2024-01-03 03:30 – Updated: 2025-06-18 18:30HCL DRYiCE MyXalytics is impacted by an improper error handling vulnerability. The application returns detailed error messages that can provide an attacker with insight into the application, system, etc.
{
"affected": [],
"aliases": [
"CVE-2023-50348"
],
"database_specific": {
"cwe_ids": [
"CWE-209"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-01-03T02:15:44Z",
"severity": "LOW"
},
"details": "HCL DRYiCE MyXalytics is impacted by an improper error handling vulnerability. The application returns detailed error messages that can provide an attacker with insight into the application, system, etc.",
"id": "GHSA-j9v2-2x9x-cmcf",
"modified": "2025-06-18T18:30:21Z",
"published": "2024-01-03T03:30:33Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-50348"
},
{
"type": "WEB",
"url": "https://support.hcltechsw.com/csm?id=kb_article\u0026sysparm_article=KB0109608"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-JFWG-RXF3-P7R9
Vulnerability from github – Published: 2026-04-06 17:56 – Updated: 2026-04-06 17:56Vulnerability Details
CWE: CWE-943 - Improper Neutralization of Special Elements in Data Query Logic
All 66+ CQL queries in internal/storage/db/cassandradb/ use fmt.Sprintf to interpolate user-controlled values directly into CQL query strings without parameterization.
Unauthenticated endpoints (signup, login, forgot_password, magic_link_login) pass user input directly into CQL query strings.
Note: This advisory covers the Cassandra CQL injection only. The Couchbase N1QL injection is tracked in a separate advisory per CVE rule 4.2.11.
Affected Code Pattern
// Before (VULNERABLE) - e.g. cassandradb/user.go
query := fmt.Sprintf("SELECT ... FROM %s WHERE email = '%s'", table, email)
err := p.db.Query(query).Scan(...)
Steps to Reproduce
- Deploy Authorizer <= 2.0.0 with Cassandra backend
- Send a signup request with a CQL injection payload in the email field:
curl -X POST http://localhost:8080/graphql \
-H 'Content-Type: application/json' \
-d '{"query":"mutation { signup(params: { email: \"test'\" }) { message } }"}'
- The single quote breaks out of the CQL string literal, causing a CQL parse error that leaks internal schema information
- Crafted payloads can manipulate query logic to bypass authentication or extract data
Affected Files (10 Cassandra files)
| Package | File | Queries Fixed |
|---|---|---|
| cassandradb | user.go | 7 |
| cassandradb | otp.go | 4 |
| cassandradb | session_token.go | 19 |
| cassandradb | verification_requests.go | 4 |
| cassandradb | authenticator.go | 3 |
| cassandradb | email_template.go | 5 |
| cassandradb | webhook.go | 5 |
| cassandradb | webhook_log.go | 2 |
| cassandradb | session.go | 1 |
| cassandradb | env.go | 2 |
Impact
An unauthenticated attacker can inject arbitrary CQL operators through the email, phone, or token parameters on public-facing endpoints (signup, login, forgot_password, magic_link_login). This enables authentication bypass and data exfiltration from the Cassandra keyspace.
Proposed Fix
Use parameterized queries:
// After (FIXED)
query := fmt.Sprintf("SELECT ... FROM %s WHERE email = ?", table)
err := p.db.Query(query, email).Scan(...)
Fixed in https://github.com/authorizerdev/authorizer/pull/500 (merged 2026-03-27).
{
"affected": [
{
"package": {
"ecosystem": "Go",
"name": "github.com/authorizerdev/authorizer"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.0.0-20260327055742-73679faa53cd"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [],
"database_specific": {
"cwe_ids": [
"CWE-209",
"CWE-943"
],
"github_reviewed": true,
"github_reviewed_at": "2026-04-06T17:56:31Z",
"nvd_published_at": null,
"severity": "HIGH"
},
"details": "## Vulnerability Details\n\n**CWE:** CWE-943 - Improper Neutralization of Special Elements in Data Query Logic\n\nAll 66+ CQL queries in `internal/storage/db/cassandradb/` use `fmt.Sprintf` to interpolate user-controlled values directly into CQL query strings without parameterization.\n\nUnauthenticated endpoints (`signup`, `login`, `forgot_password`, `magic_link_login`) pass user input directly into CQL query strings.\n\n**Note:** This advisory covers the Cassandra CQL injection only. The Couchbase N1QL injection is tracked in a separate advisory per CVE rule 4.2.11.\n\n## Affected Code Pattern\n\n```go\n// Before (VULNERABLE) - e.g. cassandradb/user.go\nquery := fmt.Sprintf(\"SELECT ... FROM %s WHERE email = \u0027%s\u0027\", table, email)\nerr := p.db.Query(query).Scan(...)\n```\n\n## Steps to Reproduce\n\n1. Deploy Authorizer \u003c= 2.0.0 with Cassandra backend\n2. Send a signup request with a CQL injection payload in the email field:\n\n```bash\ncurl -X POST http://localhost:8080/graphql \\\n -H \u0027Content-Type: application/json\u0027 \\\n -d \u0027{\"query\":\"mutation { signup(params: { email: \\\"test\u0027\\\" }) { message } }\"}\u0027\n```\n\n3. The single quote breaks out of the CQL string literal, causing a CQL parse error that leaks internal schema information\n4. Crafted payloads can manipulate query logic to bypass authentication or extract data\n\n## Affected Files (10 Cassandra files)\n\n| Package | File | Queries Fixed |\n|---------|------|--------------|\n| cassandradb | user.go | 7 |\n| cassandradb | otp.go | 4 |\n| cassandradb | session_token.go | 19 |\n| cassandradb | verification_requests.go | 4 |\n| cassandradb | authenticator.go | 3 |\n| cassandradb | email_template.go | 5 |\n| cassandradb | webhook.go | 5 |\n| cassandradb | webhook_log.go | 2 |\n| cassandradb | session.go | 1 |\n| cassandradb | env.go | 2 |\n\n## Impact\n\nAn unauthenticated attacker can inject arbitrary CQL operators through the email, phone, or token parameters on public-facing endpoints (signup, login, forgot_password, magic_link_login). This enables authentication bypass and data exfiltration from the Cassandra keyspace.\n\n## Proposed Fix\n\nUse parameterized queries:\n\n```go\n// After (FIXED)\nquery := fmt.Sprintf(\"SELECT ... FROM %s WHERE email = ?\", table)\nerr := p.db.Query(query, email).Scan(...)\n```\n\nFixed in https://github.com/authorizerdev/authorizer/pull/500 (merged 2026-03-27).",
"id": "GHSA-jfwg-rxf3-p7r9",
"modified": "2026-04-06T17:56:31Z",
"published": "2026-04-06T17:56:31Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/authorizerdev/authorizer/security/advisories/GHSA-jfwg-rxf3-p7r9"
},
{
"type": "WEB",
"url": "https://github.com/authorizerdev/authorizer/pull/500"
},
{
"type": "WEB",
"url": "https://github.com/authorizerdev/authorizer/commit/73679faa53cd215c7524d651046e402c43809786"
},
{
"type": "PACKAGE",
"url": "https://github.com/authorizerdev/authorizer"
},
{
"type": "WEB",
"url": "https://github.com/authorizerdev/authorizer/releases/tag/2.0.1"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L",
"type": "CVSS_V3"
}
],
"summary": "Authorizer: CQL/N1QL Injection in Cassandra and Couchbase Backends via fmt.Sprintf String Interpolation"
}
GHSA-JG6V-CRQ7-F587
Vulnerability from github – Published: 2026-04-08 15:31 – Updated: 2026-04-08 15:31Dell PowerScale OneFS, versions 9.5.0.0 through 9.10.1.6 and versions 9.11.0.0 through 9.13.0.0, contains a generation of error message containing sensitive information vulnerability. A high privileged attacker with local access could potentially exploit this vulnerability, leading to information disclosure.
{
"affected": [],
"aliases": [
"CVE-2026-24511"
],
"database_specific": {
"cwe_ids": [
"CWE-209"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-04-08T13:16:40Z",
"severity": "MODERATE"
},
"details": "Dell PowerScale OneFS, versions 9.5.0.0 through 9.10.1.6 and\u00a0versions 9.11.0.0 through 9.13.0.0, contains a generation of error message containing sensitive information vulnerability. A\u00a0high privileged attacker with local access\u00a0could potentially exploit this vulnerability, leading to information disclosure.",
"id": "GHSA-jg6v-crq7-f587",
"modified": "2026-04-08T15:31:43Z",
"published": "2026-04-08T15:31:43Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-24511"
},
{
"type": "WEB",
"url": "https://www.dell.com/support/kbdoc/en-us/000449337/dsa-2026-125-security-update-for-dell-powerscale-onefs-multiple-vulnerabilities"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-JH3R-77V7-VR84
Vulnerability from github – Published: 2022-06-29 00:00 – Updated: 2022-07-10 00:00Dell PowerScale OneFS, 8.2.x through 9.3.0.x, contain an error message with sensitive information. An administrator could potentially exploit this vulnerability, leading to disclosure of sensitive information. This sensitive information can be used to access sensitive resources.
{
"affected": [],
"aliases": [
"CVE-2022-31229"
],
"database_specific": {
"cwe_ids": [
"CWE-209"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-06-28T19:15:00Z",
"severity": "MODERATE"
},
"details": "Dell PowerScale OneFS, 8.2.x through 9.3.0.x, contain an error message with sensitive information. An administrator could potentially exploit this vulnerability, leading to disclosure of sensitive information. This sensitive information can be used to access sensitive resources.",
"id": "GHSA-jh3r-77v7-vr84",
"modified": "2022-07-10T00:00:47Z",
"published": "2022-06-29T00:00:25Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-31229"
},
{
"type": "WEB",
"url": "https://www.dell.com/support/kbdoc/en-us/000200681/dsa-2022-118-dell-emc-powerscale-onefs-security-update?lang=en"
}
],
"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-JHPR-J7CQ-3JP3
Vulnerability from github – Published: 2023-06-22 19:59 – Updated: 2024-11-18 16:26Impact
An authenticated malicious actor with Admin privileges, could by adding a special character on the add, edit User forms trigger a database error, this error is surfaced back to this actor on the UI. On certain database engines this error can include the entire user row including the pbkdf2:sha256 hashed password.
Patches
Fixed on 4.3.2
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "Flask-AppBuilder"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.3.2"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2023-34110"
],
"database_specific": {
"cwe_ids": [
"CWE-209"
],
"github_reviewed": true,
"github_reviewed_at": "2023-06-22T19:59:03Z",
"nvd_published_at": "2023-06-22T23:15:09Z",
"severity": "MODERATE"
},
"details": "### Impact\nAn authenticated malicious actor with Admin privileges, could by adding a special character on the add, edit User forms trigger a database error, this error is surfaced back to this actor on the UI. On certain database engines this error can include the entire user row including the pbkdf2:sha256 hashed password.\n \n### Patches\nFixed on 4.3.2\n",
"id": "GHSA-jhpr-j7cq-3jp3",
"modified": "2024-11-18T16:26:30Z",
"published": "2023-06-22T19:59:03Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/dpgaspar/Flask-AppBuilder/security/advisories/GHSA-jhpr-j7cq-3jp3"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-34110"
},
{
"type": "WEB",
"url": "https://github.com/dpgaspar/Flask-AppBuilder/pull/2045"
},
{
"type": "WEB",
"url": "https://github.com/dpgaspar/Flask-AppBuilder/commit/ae25ad4c87a9051ebe4a4e8f02aee73232642626"
},
{
"type": "PACKAGE",
"url": "https://github.com/dpgaspar/Flask-AppBuilder"
},
{
"type": "WEB",
"url": "https://github.com/dpgaspar/Flask-AppBuilder/releases/tag/v4.3.2"
},
{
"type": "WEB",
"url": "https://github.com/pypa/advisory-database/tree/main/vulns/flask-appbuilder/PYSEC-2023-94.yaml"
}
],
"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"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N",
"type": "CVSS_V4"
}
],
"summary": "Flask-AppBuilder vulnerable to possible disclosure of sensitive information on user error"
}
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.