Kamaji: SQL injection via unescaped datastore identifiers in PostgreSQL/MySQL drivers
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| clastix | kamaji | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Clastix | Kamaji |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.324% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Clastix
Clastix kamaji |
|
| Vendors & Products |
Clastix
Clastix kamaji |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Kamaji is the Hosted Control Plane Manager for Kubernetes. Prior to 26.7.4-edge, the PostgreSQL and MySQL datastore drivers build DDL statements by interpolating the user-supplied DataStoreUsername/DataStoreSchema directly into SQL via fmt.Sprintf, without escaping identifiers. These fields have no format validation, so a value containing a quote character breaks out of the quoted identifier — SQL injection executed over Kamaji's root connection to the shared datastore. etcd driver is not affected.This issue is fixed in version 26.7.4-edge. | |
| Title | Kamaji: SQL injection via unescaped datastore identifiers in PostgreSQL/MySQL drivers | |
| Weaknesses | CWE-89 | |
| References |
| |
| Metrics |
cvssV3_1
|