# CVE-2023-22479: KubePi vulnerable to session fixation attack

> Attackers can hijack legitimate user sessions in KubePi, leading to unauthorized account access.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 10 Jan 2023
- **Updated:** 10 Mar 2025
- **Also known as:** GHSA-v4w5-r2xc-7f8h, GO-2023-1468

## What is CVE-2023-22479?

CVE-2023-22479 is a high-severity authentication bypass vulnerability in KubeOperator KubePi, published on 10 Jan 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

KubePi is a modern Kubernetes panel. A session fixation attack allows an attacker to hijack a legitimate user session, versions 1.6.3 and below are susceptible. A patch will be released in version 1.6.4.

Weakness: CWE-384 (Session Fixation)

## Which versions are affected by CVE-2023-22479?

3 open source packages ship an affected version, including github.com/KubeOperator/kubepi. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/KubeOperator/kubepi` | Go | All versions | 1.6.4 |
| `github.com/KubeOperator/kubepi` | Go | All versions | 1.6.4 |
| `github.com/KubeOperator/kubepi` | Go | All versions | 1.6.4 |

Products: Fit2cloud Kubepi.

## How do I fix CVE-2023-22479?

Upgrade github.com/KubeOperator/kubepi to 1.6.4 or later.

## Is CVE-2023-22479 being exploited?

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

## Other vulnerabilities in KubeOperator KubePi

- [CVE-2023-22463](https://insights.sbomify.com/CVE-2023-22463/): KubePi's Hardcoded Jwtsigkeys allows malicious actor to login with a forged JWT token (critical 9.8)
- [CVE-2023-37917](https://insights.sbomify.com/CVE-2023-37917/): Privilege Escalation in kubepi (critical 9.1)
- [CVE-2023-22478](https://insights.sbomify.com/CVE-2023-22478/): KubePi is vulnerable to missing authorization (high 7.3)
- [CVE-2023-37916](https://insights.sbomify.com/CVE-2023-37916/): Leak password hash of any user (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-22479 and fix it if it is affected.

What it is: CVE-2023-22479 is a high-severity authentication bypass vulnerability in KubeOperator KubePi, published on 10 Jan 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-22479 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/KubeOperator/kubepi (Go): affected all versions; fixed in 1.6.4
- github.com/KubeOperator/kubepi (Go): affected all versions; fixed in 1.6.4
- github.com/KubeOperator/kubepi (Go): affected all versions; fixed in 1.6.4

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

## Sources

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

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