# CVE-2022-36089: VelaUX APIServer vulnerable to Authentication Bypass by Capture-replay

> Attackers can bypass authentication in VelaUX APIServer by using the exposed PlatformID to forge JWT tokens, gaining unauthorized access.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** 7 Sep 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-cq42-w295-r29q

## What is CVE-2022-36089?

CVE-2022-36089 is a high-severity authentication bypass vulnerability in kubevela, published on 7 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

KubeVela is an application delivery platform Users using KubeVela's VelaUX APIServer could be affected by an authentication bypass vulnerability. In KubeVela prior to versions 1.4.11 and 1.5.4, VelaUX APIServer uses the `PlatformID` as the signed key to generate the JWT tokens for users. Another API called `getSystemInfo` exposes the platformID. This vulnerability allows users to use the platformID to re-generate the JWT tokens to bypass the authentication. Versions 1.4.11 and 1.5.4 contain a patch for this issue.

Weakness: CWE-294 (Authentication Bypass by Capture-replay)

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

It affects 1 product.


Products: Kubevela Kubevela.

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

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

## Is CVE-2022-36089 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-36089 is a high-severity authentication bypass vulnerability in kubevela, published on 7 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-36089 in the wild and no public exploit code.

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

## Sources

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

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