No Authentication on Logging Server
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Apache Software Foundation | Apache Airflow | affected |
|
No data.
No data available yet.
Vendor Workaround
Use remote logging with GCS, S3, Elasticsearch etc. This is recommended for production environments. And do not publicly expose any other ports apart from Webserver port, Flower port etc.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2021-0013 | 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. |
Github GHSA |
GHSA-m6h2-jx9v-58w6 | Missing Authorization in Apache Airflow |
No CVSS v4.0
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 5.5% (5.450% probability within 30 days)
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
epss
|
epss
|