Dagster Vulnerable to SQL Injection via Dynamic Partition Keys in Database I/O Manager Integrations
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 0.29.1, 1.13.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 1 proof of concept on GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- dagster-io dagster
dagster < 1.13.1, dagster-duckdb < 0.29.1, dagster-snowflake < 0.29.1, dagster-gcp < 0.29.1, dagster-deltalake < 0.29.1, dagster-snowflake-polars < 0.29.1
- dagster-duckdbPyPI
fixed in 0.29.1
- dagster-snowflakePyPI
fixed in 0.29.1
- dagster-gcpPyPI
fixed in 0.29.1
- dagsterPyPI
fixed in 1.13.1
- dagster-deltalakePyPI
fixed in 0.29.1
- dagster-snowflake-polarsPyPI
fixed in 0.29.1