# CVE-2022-24856: Server-Side Request Forgery in FlyteConsole

> Attackers can exploit SSRF in FlyteConsole to access internal metadata servers or unauthenticated URLs when the console is exposed to the internet.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 May 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-www6-hf2v-v9m9

## What is CVE-2022-24856?

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.

### Official 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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2022-24856?

It affects 1 product.


Products: Flyte Flyte Console.

## How do I fix CVE-2022-24856?

No fix has been published for CVE-2022-24856 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-24856 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-24856 exists.

Public exploit code:

- Flyte Console <0.52.0 - Server-Side Request Forgery (nuclei): http/cves/2022/CVE-2022-24856.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-24856 and fix it if it is affected.

What 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-24856 exists.

Affected product: flyteorg flyteconsole. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-24856/ (Markdown: https://insights.sbomify.com/CVE-2022-24856/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-24856
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-24856
- OSV: https://osv.dev/vulnerability/CVE-2022-24856

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-24856/
Summaries are generated and may contain mistakes; the official description above is the record.