stigmem Postgres SQL Injection via Schema Identifier
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| eidetic-labs | stigmem | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Eidetic-labs | Stigmem |
|
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.383% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Eidetic-labs
Eidetic-labs stigmem |
|
| Vendors & Products |
Eidetic-labs
Eidetic-labs stigmem |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | stigmem-node 0.9.0a1 interpolates Postgres backend schema identifiers into SQL strings without defensive quoting. In the affected code path the schema value is operator-controlled, but the unsafe pattern could allow SQL injection if a schema name were derived from tenant, request, or user input. Fixed in 0.9.0a2, which adds identifier quoting and validation. As a workaround, only configure schema names from trusted deployment configuration. | |
| Title | stigmem Postgres SQL Injection via Schema Identifier | |
| Weaknesses | CWE-89 | |
| References |
| |
| Metrics |
cvssV4_0
|