apache-airflow

Vulnerabilities (111)

• CVE-2022-40604Sep 21, 2022
  affected >= 2.3.0, < 2.4.0rc1fixed 2.4.0rc1

  In Apache Airflow 2.3.0 through 2.3.4, part of a url was unnecessarily formatted, allowing for possible information extraction.

• CVE-2022-38170Sep 2, 2022
  affected < 2.3.4fixed 2.3.4

  In Apache Airflow prior to 2.3.4, an insecure umask was configured for numerous Airflow components when running with the `--daemon` flag which could result in a race condition giving world-writable files in the Airflow home directory and allowing local users to expose arbitrary f

• CVE-2022-38054Sep 2, 2022
  affected >= 2.2.4, < 2.3.4rc1fixed 2.3.4rc1

  In Apache Airflow versions 2.2.4 through 2.3.3, the `database` webserver session backend was susceptible to session fixation.

• CVE-2022-24288Feb 25, 2022
  affected < 2.2.4fixed 2.2.4

  In Apache Airflow, prior to version 2.2.4, some example DAGs did not properly sanitize user-provided params, making them susceptible to OS Command Injection from the web UI.

• CVE-2021-45229Feb 25, 2022
  affected < 2.2.4rc1fixed 2.2.4rc1

  It was discovered that the "Trigger DAG with config" screen was susceptible to XSS attacks via the `origin` query argument. This issue affects Apache Airflow versions 2.2.3 and below.

• CVE-2021-45230Jan 20, 2022
  affected < 2.2.0fixed 2.2.0

  In Apache Airflow prior to 2.2.0. This CVE applies to a specific case where a User who has "can_create" permissions on DAG Runs can create Dag Runs for dags that they don't have "edit" permissions for.

• CVE-2021-38540Sep 9, 2021
  affected >= 2.0.0, < 2.1.3fixed 2.1.3

  The variable import endpoint was not protected by authentication in Airflow >=2.0.0, <2.1.3. This allowed unauthenticated users to hit that endpoint to add/modify Airflow variables used in DAGs, potentially resulting in a denial of service, information disclosure or remote code e

• CVE-2021-35936Aug 16, 2021
  affected < 2.1.2fixed 2.1.2

  If remote logging is not used, the worker (in the case of CeleryExecutor) or the scheduler (in the case of LocalExecutor) runs a Flask logging server and is listening on a specific port and also binds on 0.0.0.0 by default. This logging server had no authentication and allows rea

• CVE-2021-28359May 2, 2021
  affected < 1.10.15fixed 1.10.15

  The "origin" parameter passed to some of the endpoints like '/trigger' was vulnerable to XSS exploit. This issue affects Apache Airflow versions <1.10.15 in 1.x series and affects 2.0.0 and 2.0.1 and 2.x series. This is the same as CVE-2020-13944 & CVE-2020-17515 but the implemen

• CVE-2021-26697Feb 17, 2021
  affected >= 2.0.0, < 2.0.1rc1fixed 2.0.1rc1

  The lineage endpoint of the deprecated Experimental API was not protected by authentication in Airflow 2.0.0. This allowed unauthenticated users to hit that endpoint. This is low-severity issue as the attacker needs to be aware of certain parameters to pass to that endpoint and e

• CVE-2021-26559Feb 17, 2021
  affected >= 2.0.0, < 2.0.1rc1fixed 2.0.1rc1

  Improper Access Control on Configurations Endpoint for the Stable API of Apache Airflow allows users with Viewer or User role to get Airflow Configurations including sensitive information even when `[webserver] expose_config` is set to `False` in `airflow.cfg`. This allowed a pri

• CVE-2020-17526Dec 21, 2020
  affected < 1.10.14fixed 1.10.14

  Incorrect Session Validation in Apache Airflow Webserver versions prior to 1.10.14 with default config allows a malicious airflow user on site A where they log in normally, to access unauthorized Airflow Webserver on Site B through the session from Site A. This does not affect us

• CVE-2020-17513Dec 14, 2020
  affected < 1.10.13fixed 1.10.13

  In Apache Airflow versions prior to 1.10.13, the Charts and Query View of the old (Flask-admin based) UI were vulnerable for SSRF attack.

• CVE-2020-17511Dec 14, 2020
  affected < 1.10.13fixed 1.10.13

  In Airflow versions prior to 1.10.13, when creating a user using airflow CLI, the password gets logged in plain text in the Log table in Airflow Metadatase. Same happened when creating a Connection with a password field.

• CVE-2020-17515Dec 11, 2020
  affected < 1.10.15rc1fixed 1.10.15rc1

  The "origin" parameter passed to some of the endpoints like '/trigger' was vulnerable to XSS exploit. This issue affects Apache Airflow versions prior to 1.10.13. This is same as CVE-2020-13944 but the implemented fix in Airflow 1.10.13 did not fix the issue completely.

• CVE-2020-13927KEVNov 10, 2020
  affected < 1.10.11fixed 1.10.11

  The previous default setting for Airflow's Experimental API was to allow all API requests without authentication, but this poses security risks to users who miss this fact. From Airflow 1.10.11 the default has been changed to deny all requests by default and is documented at http

• CVE-2020-13944Sep 17, 2020
  affected < 1.10.12fixed 1.10.12

  In Apache Airflow < 1.10.12, the "origin" parameter passed to some of the endpoints like '/trigger' was vulnerable to XSS exploit.

• CVE-2020-9485Jul 16, 2020
  affected < 1.10.11fixed 1.10.11

  An issue was found in Apache Airflow versions 1.10.10 and below. A stored XSS vulnerability was discovered in the Chart pages of the the "classic" UI.

• CVE-2020-11983Jul 16, 2020
  affected < 1.10.11fixed 1.10.11

  An issue was found in Apache Airflow versions 1.10.10 and below. It was discovered that many of the admin management screens in the new/RBAC UI handled escaping incorrectly, allowing authenticated users with appropriate permissions to create stored XSS attacks.

• CVE-2020-11982Jul 16, 2020
  affected < 1.10.11fixed 1.10.11

  An issue was found in Apache Airflow versions 1.10.10 and below. When using CeleryExecutor, if an attack can connect to the broker (Redis, RabbitMQ) directly, it was possible to insert a malicious payload directly to the broker which could lead to a deserialization attack (and th