{"answers":{"affected":"3 open source packages ship an affected version, including flower. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-30034 in the wild and no public exploit code.","fix":"Upgrade flower to 1.2.0 or later.","what":"CVE-2022-30034 is a high-severity authentication bypass vulnerability in n/a, published on 31 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-30034 and fix it if it is affected.\n\nWhat it is: CVE-2022-30034 is a high-severity authentication bypass vulnerability in n/a, published on 31 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-30034 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- flower (PyPI): affected all versions; fixed in 1.2.0\n- flower (PyPI): affected all versions; fixed in 1.2.0\n- flower (PyPI): affected all versions; fixed in 1.2.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-30034/ (Markdown: https://insights.sbomify.com/CVE-2022-30034/index.md)","id":"CVE-2022-30034","markdown":"https://insights.sbomify.com/CVE-2022-30034/index.md","name":"CVE-2022-30034","record":{"aliases":["GHSA-q4qm-xhf9-4p8f","PYSEC-2022-42973","ROOT-APP-PYPI-CVE-2022-30034","UBUNTU-CVE-2022-30034"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Celery Flower UI","requires_auth":"none","summary":"Attackers can bypass OAuth authentication in Flower to invoke arbitrary Celery RPC calls or shut down task nodes.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"flower","vendor":"flower_project"}],"cvss":{"score":8.6,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Flower OAuth authentication bypass","id":"CVE-2022-30034","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"auth_bypass","year":"2022"},"n_packages":3,"n_references":2,"next":{"headline":"Hardcoded credentials in n/a","id":"CVE-2022-30036"},"packages":[{"ecosystem":"PyPI","fixed":["1.2.0"],"introduced":["0"],"last_affected":[],"package":"flower","purl":null,"source":"GHSA-q4qm-xhf9-4p8f"},{"ecosystem":"PyPI","fixed":["1.2.0"],"introduced":["0"],"last_affected":[],"package":"flower","purl":"pkg:pypi/flower","source":"GHSA-q4qm-xhf9-4p8f"},{"ecosystem":"PyPI","fixed":["1.2.0"],"introduced":["0"],"last_affected":[],"package":"flower","purl":"pkg:pypi/flower","source":"PYSEC-2022-42973"}],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2022-30033"},"products":["n/a"],"published":"2022-05-31","related":[{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2019-16925","kev_date_added":null,"published":"2019-09-27"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2019-16926","kev_date_added":null,"published":"2019-09-27"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-07-09","vendors":["n/a"]},"summary":"Attackers can bypass OAuth authentication in Flower to invoke arbitrary Celery RPC calls or shut down task nodes.","url":"https://insights.sbomify.com/CVE-2022-30034/"}