Authentication Bypass in flower (CVE-2022-30034)
Summary
Authentication bypass in flower (CVE-2022-30034). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.2.0 or later.
Original description
The description as published by the source.
Flower, a web UI for the Celery Python RPC framework, all versions as of 05-02-2022 is vulnerable to an OAuth authentication bypass. An attacker could then access the Flower API to discover and invoke arbitrary Celery RPC calls or deny service by shutting down Celery task nodes.
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-2022-30034 has been found in flower.
Risk of unauthorized operations or information disclosure. CVSS score: 8.6/10.
What to do: upgrade flower to 1.2.0 or later.
If unsure, ask your IT team or search "flower CVE-2022-30034" on the vendor's site.
CVE-2022-30034 (flower) — CWE-287 / CVSS v3 8.6
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.2.0 — 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.
Authentication bypass (CWE-287) exists in flower.
Check the vendor advisory for the affected versions of flower.
Severity: High (CVSS 8.6/10). Risk of unauthorized operations or information disclosure.
Update to 1.2.0.
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 'flower' . 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 'flower' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
flowerを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade flower to 1.2.0ステージング環境で 1.2.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- report github.com
- web tprynn.github.io
- web githubcommherflower.com