{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-24856 exists.","fix":"No fix has been published for CVE-2022-24856 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-24856 is a critical server-side request forgery vulnerability in flyteorg flyteconsole, published on 17 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-24856 and fix it if it is affected.\n\nWhat it is: CVE-2022-24856 is a critical server-side request forgery vulnerability in flyteorg flyteconsole, published on 17 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-24856 exists.\n\nAffected product: flyteorg flyteconsole. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-24856/ (Markdown: https://insights.sbomify.com/CVE-2022-24856/index.md)","id":"CVE-2022-24856","markdown":"https://insights.sbomify.com/CVE-2022-24856/index.md","name":"CVE-2022-24856","record":{"aliases":["GHSA-www6-hf2v-v9m9"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Flyte web console","requires_auth":"none","summary":"Attackers can exploit SSRF in FlyteConsole to access internal metadata servers or unauthenticated URLs when the console is exposed to the internet.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"flyte_console","vendor":"flyte"}],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"FlyteConsole is the web user interface for the Flyte platform. FlyteConsole prior to version 0.52.0 is vulnerable to server-side request forgery (SSRF) when FlyteConsole is open to the general internet. An attacker can exploit any user of a vulnerable instance to access the internal metadata server or other unauthenticated URLs. Passing of headers to an unauthorized actor may occur. The patch for this issue deletes the entire `cors_proxy`, as this is not required for console anymore. A patch is available in FlyteConsole version 0.52.0. Disable FlyteConsole availability on the internet as a workaround.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":1,"refs":[{"date":null,"kind":"nuclei","ref":"http/cves/2022/CVE-2022-24856.yaml","stars":null,"title":"Flyte Console \u003c0.52.0 - Server-Side Request Forgery"}],"tier":"weaponised"},"has_fix":false,"headline":"Server-Side Request Forgery in FlyteConsole","id":"CVE-2022-24856","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2022"},"n_packages":0,"n_references":4,"next":{"headline":"Multi factor authentication bypass in django-mfa3","id":"CVE-2022-24857"},"packages":[],"prev":{"headline":"XSS vulnerability in Metabase","id":"CVE-2022-24855"},"products":["flyteconsole"],"published":"2022-05-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-23","vendors":["flyteorg"]},"summary":"Attackers can exploit SSRF in FlyteConsole to access internal metadata servers or unauthenticated URLs when the console is exposed to the internet.","url":"https://insights.sbomify.com/CVE-2022-24856/"}