CVE-2022-30034
No exploitation reported by the sources we read.
- Published2022-06-02
- Fixed in1.2.0
- WeaknessCWE-287
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
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.
Timeline
dates in UTC- 2022-06-0214:15CVE publishedNVD
Versions per branch
NVD · OSV| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 1.2 | < 1.2.0 | 1.2.0 | NVD · OSV |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Packages
- flowerUbuntu:18.04:LTSall versions · no fixed version listed
- flowerUbuntu:16.04:LTSall versions · no fixed version listed
- flowerRoot:PyPIall versions · fixed in 1.1.0+aikido.2
- rootio-flowerRoot:PyPIall versions · fixed in 1.1.0+root.io.1
- rootio-flowerRoot:PyPIall versions · fixed in 1.1.0+root.io.2
Fix
- Update Flower project flower to 1.2.0
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof of concept
- PoC-in-GitHubno public repository identifiedread 2026-11-19
- Metasploit modules
- none listed Metasploit Framework
Sources
- NVDCVSS 3.18.6read 2026-10-23
- NVDCVSS 2.07.5read 2026-10-23
- NVDweakness (CWE)CWE-287read 2026-10-23
- FIRST EPSSEPSS score1.1 %2026-11-18
- OSVaffected packages—
- GitHub AdvisoriesadvisoryHIGH2022-06-03
Identifiers
- EUVD-2022-0106same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-q4qm-xhf9-4p8fsame flawGitHub Advisory Database · CC-BY-4.0
- PYSEC-2022-42973same flawPyPA Advisory Database · CC-BY-4.0
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H
- Published
- 2022-06-02
- Last Modified
- 2026-07-09
- NVD status
- Modified
- GitHub Advisory
- GHSA-q4qm-xhf9-4p8f
Frequently asked questions
What is CVE-2022-30034?
Is CVE-2022-30034 actively exploited?
What is the CVSS score for CVE-2022-30034?
Running flower? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- FIRST EPSS · EPSS terms of use (free use, attribution requested)
- GitHub Advisory Database · CC-BY-4.0 · GHSA-q4qm-xhf9-4p8f
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- OSV.dev · Per record, as its publisher states it: each row carries the label in sourceLicense when one is served