Vulnerability in apache-airflow-providers-celery (CVE-2023-46215)
Summary
Vulnerability in apache-airflow-providers-celery (CVE-2023-46215). Confidential information can be exposed externally. Mitigation: upgrade to 3.4.1 or later.
Original description
The description as published by the source.
Insertion of Sensitive Information into Log File vulnerability in Apache Airflow Celery provider, Apache Airflow.
Sensitive information logged as clear text when rediss, amqp, rpc protocols are used as Celery result backend
Note: the vulnerability is about the information exposed in the logs not about accessing the logs.
This issue affects Apache Airflow Celery provider: from 3.3.0 through 3.4.0; Apache Airflow: from 1.10.0 through 2.6.3.
Users are recommended to upgrade Airflow Celery provider to version 3.4.1 and Apache Airlfow to version 2.7.0 which fixes the issue.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2023-46215 has been found in apache-airflow-providers-celery.
Confidential information can be exposed externally.
What to do: upgrade apache-airflow-providers-celery to 3.4.1 or later.
If unsure, ask your IT team or search "apache-airflow-providers-celery CVE-2023-46215" on the vendor's site.
CVE-2023-46215 (apache-airflow-providers-celery) — CWE-532
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 3.4.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-532) exists in apache-airflow-providers-celery.
Check the vendor advisory for the affected versions of apache-airflow-providers-celery.
Severity: ?. Confidential information can be exposed externally.
Update to 3.4.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'apache-airflow-providers-celery' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'apache-airflow-providers-celery' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
apache-airflow-providers-celeryを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade apache-airflow-providers-celery to 3.4.1ステージング環境で 3.4.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory lists.apache.org
- advisory openwall.com
- package github.com
- patch github.com
- web nvd.nist.gov