The Apache Airflow Teradata provider's compute-cluster example DAG improperly neutralizes special elements used in SQL commands, leading to an SQL injection vulnerability (CWE-89). The DAG's parameters are unconstrained free text, which are templated directly into Teradata DDL statements. A user authorized to trigger the DAG but without Teradata credentials can supply malicious SQL fragments that execute under the task's connection context. Additionally, the connection ID itself is a free-text parameter, allowing redirection of the task to other connections defined in the deployment. Only deployments running this example DAG or copies thereof are affected; the underlying operator code is unaffected. The vulnerability is fixed in version 3.7.0 by constraining parameters to validated identifiers and closed value sets and removing connection selection and free-form option strings from trigger-time input.

An attacker with permission to trigger the vulnerable DAG can execute arbitrary SQL commands on the Teradata database using the connection privileges of the task. This can lead to unauthorized data access or modification. The vulnerability does not require the attacker to have Teradata credentials, only permission to trigger the DAG. The impact is limited to deployments running the vulnerable example DAG or copies of it; the provider's operator code is not vulnerable.

Upgrade the Apache Airflow Teradata provider to version 3.7.0 or later, which constrains DAG parameters to validated identifiers and closed value sets and removes free-form connection selection from trigger-time input. For users who have copied the vulnerable example DAG, manually apply the same parameter constraints to their copies to mitigate the vulnerability. No other action is required if the example DAG is not used.