apache-airflow-core 3.3.1rc1

Direct Vulnerabilities

Known vulnerabilities in the apache-airflow-core package. This does not include vulnerabilities belonging to this package’s dependencies.

Fix vulnerabilities automatically

Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

Fix for free

Vulnerability	Vulnerable Version
H Authorization Bypass Through User-Controlled Key Affected versions of this package are vulnerable to Authorization Bypass Through User-Controlled Key in the `connections/test` API endpoint due to improper enforcement of team-scoped access controls. An attacker can access another team's environment connection and authenticate outward using that team's credentials by supplying a crafted request with knowledge of the encoded identifier. Note: This is only exploitable if the `[core] multi_team` option is enabled, `[core] test_connection` is set to `Enabled`, team-scoped secrets are provisioned as environment variables in the API-server process, and the attacker knows the encoded identifier. How to fix Authorization Bypass Through User-Controlled Key? Upgrade `apache-airflow-core` to version 3.3.1 or higher.	[,3.3.1)
H Deserialization of Untrusted Data Affected versions of this package are vulnerable to Deserialization of Untrusted Data in the `deserialize`. An attacker can execute arbitrary code by supplying a crafted serialized blob that causes the import and invocation of malicious callables. This can be exploited by a DAG author through the `executor_config` field, affecting both the Scheduler and API server components, which may expose sensitive credentials. How to fix Deserialization of Untrusted Data? Upgrade `apache-airflow-core` to version 3.3.1 or higher.	[,3.3.1)
H Deserialization of Untrusted Data Affected versions of this package are vulnerable to Deserialization of Untrusted Data in the `BaseXCom.deserialize_value`. An attacker can execute arbitrary code on the API server by submitting specially crafted JSON string literals to the `GET /api/v2/{...}/xcomEntries/{key}?deserialize=true` endpoint, provided they have authenticated API access with both write and read permissions for XCom values. Note: This is only exploitable if the attacker is an authenticated user with XCom write-and-read access. How to fix Deserialization of Untrusted Data? Upgrade `apache-airflow-core` to version 3.3.1 or higher.	[,3.3.1)
H Deserialization of Untrusted Data Affected versions of this package are vulnerable to Deserialization of Untrusted Data in the `awaiting_input`. An attacker can execute arbitrary code or terminate the scheduler process by supplying crafted data to the `next_kwargs` parameter during task execution. Note: This is only exploitable if the attacker has DAG author permissions, as the sweep runs unconditionally every 15 seconds and no non-default configuration is required. How to fix Deserialization of Untrusted Data? Upgrade `apache-airflow-core` to version 3.3.1 or higher.	[3.3.0,3.3.1)
M Interpretation Conflict Affected versions of this package are vulnerable to Interpretation Conflict due to inconsistent parsing of the `backfill_id` path segment between the authorization dependency and the route handler. An attacker can gain unauthorized access to read, pause, and cancel backfills for other Dags, as well as move queued runs to `failed`, by supplying specially crafted values for `backfill_id`. How to fix Interpretation Conflict? Upgrade `apache-airflow-core` to version 3.3.1 or higher.	[,3.3.1)
M Insertion of Sensitive Information into Log File Affected versions of this package are vulnerable to Insertion of Sensitive Information into Log File in the handling of bulk requests to the `PATCH /api/v2/variables` and `PATCH /api/v2/connections` endpoints. An attacker can obtain sensitive secret values in cleartext by accessing the audit log, as the masking process did not apply to nested fields within bulk requests. This allows any authenticated user with audit-log read access to recover secrets without needing direct access to variables or connections. How to fix Insertion of Sensitive Information into Log File? Upgrade `apache-airflow-core` to version 3.3.1 or higher.	[,3.3.1)
H Missing Authorization Affected versions of this package are vulnerable to Missing Authorization in the `POST /api/v2/assets/{asset_id}/materialize` endpoint and the XCom result check on `wait_dag_run_until_finished`. An attacker can access and manipulate DAG runs and read XCom values belonging to other teams by supplying their own `dag_run_id` and `conf` parameters in a multi-team deployment with a team-aware authentication manager. Note: This is only exploitable if the deployment is running in multi-team mode with a team-aware authentication manager; deployments using the FAB auth manager are not affected. How to fix Missing Authorization? Upgrade `apache-airflow-core` to version 3.3.1 or higher.	[,3.3.1)
M Insertion of Sensitive Information Into Sent Data Affected versions of this package are vulnerable to Insertion of Sensitive Information Into Sent Data in the `Config API` when multi-team mode is enabled and the API is exposed. An attacker can obtain sensitive team-scoped Celery broker credentials by accessing configuration-read endpoints as an authenticated Viewer, due to improper masking of secrets in team-prefixed sections. How to fix Insertion of Sensitive Information Into Sent Data? Upgrade `apache-airflow-core` to version 3.3.1 or higher.	[3.3.0,3.3.1)

Vulnerability

Vulnerable Version

Authorization Bypass Through User-Controlled Key

Affected versions of this package are vulnerable to Authorization Bypass Through User-Controlled Key in the connections/test API endpoint due to improper enforcement of team-scoped access controls. An attacker can access another team's environment connection and authenticate outward using that team's credentials by supplying a crafted request with knowledge of the encoded identifier.

Note: This is only exploitable if the [core] multi_team option is enabled, [core] test_connection is set to Enabled, team-scoped secrets are provisioned as environment variables in the API-server process, and the attacker knows the encoded identifier.

How to fix Authorization Bypass Through User-Controlled Key?