Missing Authorization in Apache Airflow
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 reading log files of DAG jobs. This issue affects Apache Airflow < 2.1.2.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2021-35936US | medium5.3OT elevated | — | ||
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… | ||||
02
references
External citations — patches, advisories, analysis.
- https://github.com/advisories/GHSA-m6h2-jx9v-58w6ADVISORY
- https://github.com/apache/airflowPACKAGE
- https://github.com/apache/airflow/commit/27265516d2b897585f5019ecd820cfe5471fd351WEB
- https://github.com/apache/airflow/commit/7a5bb88ad78d600fbb1676a55752597928115bd8WEB
- https://github.com/apache/airflow/commit/d772f38f843b9add5319a01cf51a844145b01f63WEB
- https://github.com/apache/airflow/compare/2.1.1...2.1.2WEB
- https://github.com/pypa/advisory-database/tree/main/vulns/apache-airflow/PYSEC-2021-122.yamlWEB
- https://lists.apache.org/thread.html/r53d6bd7b0a66f92ddaf1313282f10fec802e71246606dd30c16536df%40%3Cusers.airflow.apache.org%3EWEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan