LiveActive security incident?Get immediate response
CVE Record

CVE-2022-30034: Flower, a web UI for the Celery Python RPC framework, all versions as of 05-02-2022 is vulnerable to an OAu...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2022-30034 describes an OAuth authentication bypass in Flower, the web UI commonly used to administer Celery task systems. If exposed, an attacker may reach administrative API functions, inspect task-related RPC capabilities, invoke Celery RPC calls, or disrupt workers by shutting down task nodes.

Executive priority

Treat this as high priority if Flower is exposed outside a trusted admin boundary. The business risk is unauthorized control or disruption of background job processing, which can affect operations, customer workflows, and service reliability.

Technical view

The CVE record reports that Flower versions current as of 2022-05-02 were vulnerable to OAuth authentication bypass. The stated impact is unauthorized access to the Flower API, enabling discovery and invocation of Celery RPC calls and denial of service against Celery task nodes. No CVSS, CWE, fixed version, or confirmed exploit activity is provided in the supplied bundle.

Likely exposure

Exposure is most relevant where Flower is deployed for Celery administration and reachable beyond tightly controlled administrator networks. Internet-facing or broadly accessible internal Flower instances are the main concern.

Exploitation context

The supplied sources do not show CISA KEV listing or confirmed active exploitation. The reported abuse path requires access to a vulnerable Flower service using the affected OAuth authentication behavior.

Researcher notes

Evidence is limited to the CVE description, a public vulnerability write-up, and the upstream GitHub issue. The bundle does not provide CVSS scoring, CWE classification, exploit confirmation, or a named fixed release. Avoid assuming affected versions beyond Flower versions current as of 2022-05-02.

Mitigation direction

  • Check Flower upstream guidance and issue 1217 for fixed versions or configuration advice.
  • Restrict Flower access to trusted administrator networks or VPN-only paths.
  • Place independent access control in front of Flower until vendor guidance is confirmed.
  • Remove public internet exposure for Flower management interfaces.
  • Monitor Celery worker control activity and unexpected node shutdowns.

Validation and detection

  • Inventory all Flower deployments supporting Celery environments.
  • Identify any Flower services reachable from the internet or broad internal networks.
  • Confirm whether OAuth authentication is enabled on exposed Flower instances.
  • Review Flower and Celery logs for unexpected API access or worker shutdown activity.
  • Compare deployed versions and configuration against upstream Flower guidance.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-30034 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
1ADP providers
3Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.