# CVE-2022-39383: SSRF vulnerability in KubeVela VelaUX APIServer

> Attackers can exploit a blind SSRF vulnerability in KubeVela VelaUX APIServer when using Helm Chart delivery, potentially accessing internal resources.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Nov 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-m5xf-x7q6-3rm7, GO-2022-1113

## What is CVE-2022-39383?

CVE-2022-39383 is a medium-severity server-side request forgery vulnerability in kubevela, published on 16 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

KubeVela is an open source application delivery platform. Users using the VelaUX APIServer could be affected by this vulnerability. When using Helm Chart as the component delivery method, the request address of the warehouse is not restricted, and there is a blind SSRF vulnerability. Users who're using v1.6, please update the v1.6.1. Users who're using v1.5, please update the v1.5.8. There are no known workarounds for this issue.

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

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

5 open source packages ship an affected version, including github.com/oam-dev/kubevela. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/oam-dev/kubevela` | Go | All versions | 1.5.8, 1.6.1 |
| `github.com/oam-dev/kubevela` | Go | All versions | 1.5.9 |
| `github.com/oam-dev/kubevela` | Go | All versions | 1.5.9 |
| `github.com/oam-dev/kubevela` | Go | From 1.6.0-alpha.1 | 1.6.2 |
| `github.com/oam-dev/kubevela` | Go | From 1.6.0-alpha.1 | 1.6.2 |

Products: Linuxfoundation Kubevela.

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

Upgrade github.com/oam-dev/kubevela to a fixed version for your release line: 1.5.8, 1.6.1, 1.5.9 or 1.6.2.

## Is CVE-2022-39383 being exploited?

There is no known exploitation of CVE-2022-39383 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2022-39383 is a medium-severity server-side request forgery vulnerability in kubevela, published on 16 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-39383 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/oam-dev/kubevela (Go): affected all versions; fixed in 1.5.8, 1.6.1
- github.com/oam-dev/kubevela (Go): affected all versions; fixed in 1.5.9
- github.com/oam-dev/kubevela (Go): affected all versions; fixed in 1.5.9
- github.com/oam-dev/kubevela (Go): affected from 1.6.0-alpha.1; fixed in 1.6.2
- github.com/oam-dev/kubevela (Go): affected from 1.6.0-alpha.1; fixed in 1.6.2

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-39383/ (Markdown: https://insights.sbomify.com/CVE-2022-39383/index.md)
```

## Sources

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

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