stigm-node SQL Injection via Unquoted Postgres Schema Identifier (GHSA-9pc9-4crj-mhjq)

Vulnerability Overview Vulnerability Name: Postgres schema identifier handling required defensive quoting Vulnerability ID: GHSA-9pc9-4crj-mhjq Severity: High (7.5 / 10) Publication Date: May 19, 2023 CVE ID: No known CVE CVSS v4 base metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Attack Requirements: Present - Privileges Required: High - User Interaction: None - Vulnerable System Impact Metrics: - Confidentiality: High - Integrity: High - Availability: High - Subsequent System Impact Metrics: - Confidentiality: None - Integrity: None - Availability: None Scope of Impact Affected Version: 0.9.0a1 Fixed Version: 0.9.0a2 Impact Description: Postgres backend schema identifiers are inserted into SQL strings. In the reviewed code paths, the schema value is controlled by the operator, but the approach is insecure because future calls allow tenant- or request-controlled schema names. The affected users are those using the Postgres backend operators. Remediation Patch: In 0.9.0a2, schema identifier handling now uses defensive identifier quoting and validation, accompanied by regression coverage. Temporary Solution: Before upgrading, configure Postgres schema names only from trusted deployment configurations, and do not derive schema names from requests, tenants, headers, or user input. Upgrade: Upgrade to the patched version: If installed via the Stigmen meta-package, use the corresponding extra for deployment, for example: References Release: https://github.com/eidetic-labs/stigm-node/releases/tag/v0.9.0a2 Changelog: https://github.com/eidetic-labs/stigm-node/blob/v0.9.0a2/CHANGELOG.md#1-35 Security policy and posture: https://github.com/eidetic-labs/stigm-node/blob/v0.9.0a2/SECURITY.md

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

stigm-node SQL Injection via Unquoted Postgres Schema Identifier (GHSA-9pc9-4crj-mhjq)

More from this source