Apache Airflow: Sensitive configuration for providers displayed when "non-sensitive-only" config used
Airflow versions 2.7.0 through 2.8.4 have a vulnerability that allows an authenticated user to see sensitive provider configuration via the "configuration" UI page when "non-sensitive-only" was set as "webserver.expose_config" configuration (The celery provider is the only community provider currently that has sensitive configurations). You should migrate to Airflow 2.9 or change your "expose_config" configuration to False as a workaround. This is similar, but different to CVE-2023-46288 https://github.com/advisories/GHSA-9qqg-mh7c-chfq which concerned API, not UI configuration page.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2024-31869US | medium4.3 | — | ||
Airflow versions 2.7.0 through 2.8.4 have a vulnerability that allows an authenticated user to see sensitive provider configuration via the "configuration" UI page when "non-sensit… | ||||
references
External citations — patches, advisories, analysis.
- http://www.openwall.com/lists/oss-security/2024/04/17/10WEB
- https://github.com/advisories/GHSA-2522-mrjc-m688ADVISORY
- https://github.com/apache/airflowPACKAGE
- https://github.com/apache/airflow/commit/042c2acaed7c01933d37c2f8434640ce140a4b27WEB
- https://github.com/apache/airflow/pull/38795WEB
- https://lists.apache.org/thread/pz6vg7wcjk901rmsgt86h76g6kfcgtk3WEB
- https://nvd.nist.gov/vuln/detail/CVE-2024-31869ADVISORY
- https://pypi.org/project/apache-airflowPACKAGE
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