CVE-2022-30034

Exp

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.

Published: 2022-06-02 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2022-30034 is rated High Exploit Risk (64.6/100): CVSS High severity, with low exploitation likelihood (EPSS 0.21%). Core evidence: 2 public exploit reference(s) are indexed (Exploit-DB). Mandatory action: Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2022-30034

EDB-ID Source Kind Published Link
nvd_ref exploit_tag Exploit-DB ↗
nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2022-30034

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-11-21 0.39% 0.21% -0.17%
2 2025-11-18 0.21% 0.39% +0.17%
3 2025-10-27 0.21%

Full EPSS history (18 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-30034

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.6 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
3.9 4.7 [email protected]
7.5 2.0 HIGH
AV:N/AC:L/Au:N/C:P/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
10.0 6.4 [email protected]

Weakness enumeration for CVE-2022-30034

GitHub Security Advisory for CVE-2022-30034

GHSA-q4qm-xhf9-4p8f · Severity: high · Ecosystem: pip — Flower OAuth authentication bypass

OS Trackers for CVE-2022-30034

vendor priority summary link
ubuntu medium CVE-2022-30034 medium priority: Ubuntu including 1 source packages (flower), 3 status rows across 3 suites (bionic, upstream, xenial): needs-triage 3. https://ubuntu.com/security/CVE-2022-30034

Affected software / configurations for CVE-2022-30034

Vendor Product Version Raw CPE
flower_project flower < 1.2.0 cpe:2.3:a:flower_project:flower:*:*:*:*:*:*:*:*

References for CVE-2022-30034

URL Tags
http://githubcommherflower.com Broken Link URL Repurposed
https://github.com/mher/flower/issues/1217 Exploit Issue Tracking
https://tprynn.github.io/2022/05/26/flower-vulns.html Exploit Third Party Advisory
cvelogic Threat Intelligence