Dagster Vulnerable to SQL Injection via Dynamic Partition Keys in Database I/O Manager Integrations
dagster-io dagster
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| dagster-duckdb PyPI |
|
|
| dagster-snowflake PyPI |
|
|
| dagster-gcp PyPI |
dagster-io dagster
| Product | Affected | Fixed in |
|---|---|---|
| dagster-duckdb PyPI |
|
|
| dagster-snowflake PyPI |
|
|
| dagster-gcp PyPI |
< 0.29.1
|
| dagster PyPI |
|
|
| dagster-deltalake PyPI |
|
|
| dagster-snowflake-polars PyPI |
|
|
Dagster is an orchestration platform for the development, production, and observation of data assets. Prior to Dagster Core version 1.13.1 and prior to Dagster libraries version 0.29.1, the DuckDB, Snowflake, BigQuery, and DeltaLake I/O managers constructed SQL WHERE clauses by interpolating dynamic partition key values into queries without escaping. A user with the Add Dynamic Partitions permission could create a partition key that injects arbitrary SQL, which would execute against the target database backend under the I/O manager's credentials. Only deployments that use dynamic partitions are affected. Pipelines using static or time-window partitions are not impacted. This issue has been patched in Dagster Core version 1.13.1 and Dagster libraries version 0.29.1.
From the CVE record · GitHub_M
The DuckDB, Snowflake, BigQuery, and DeltaLake I/O managers interpolate dynamic partition keys into SQL WHERE clauses without escaping. In deployments using dynamic partitions, a user with Add Dynamic Partitions permission can create a key that executes arbitrary SQL against the target database under the I/O manager's credentials. Static and time-window partitions are not affected.
Check deployments using dagster before 1.13.1 or dagster-duckdb, dagster-snowflake, dagster-gcp, dagster-deltalake, or dagster-snowflake-polars before 0.29.1.