Patchfirst
Patchfirst
CVE-2023-22463 Public exploit Critical · 9.8 EPSS 69.7%

KubePi's Hardcoded Jwtsigkeys allows malicious actor to login with a forged JWT token

KubeOperator · KubePi

Summary

KubePi, the Kubernetes management panel from KubeOperator, uses a hard-coded JWT signing key (JwtSigKey in session.go) in its authentication function, so the same key is shared across all deployments. An unauthenticated remote attacker with network access can forge arbitrary JWT tokens without any user interaction or prior credentials, enabling them to take over the administrator account and, from there, the Kubernetes cluster it manages.

Official description · CVE.org

KubePi is a k8s panel. The jwt authentication function of KubePi through version 1.6.2 uses hard-coded Jwtsigkeys, resulting in the same Jwtsigkeys for all online projects. This means that an attacker can forge any jwt token to take over the administrator account of any online project. Furthermore, they may use the administrator to take over the k8s cluster of the target enterprise. `session.go`, the use of hard-coded JwtSigKey, allows an attacker to use this value to forge jwt tokens arbitrarily. The JwtSigKey is confidential and should not be hard-coded in the code. The vulnerability has been fixed in 1.6.3. In the patch, JWT key is specified in app.yml. If the user leaves it blank, a random key will be used. There are no workarounds aside from upgrading.

Breakdown
66.7 / 100
Exploited
Yes, in VulnCheck KEV
Reports
0
Tactics
0/15

First seen exploited 2 years after disclosure.

  1. Disclosedday 0
  2. First seen exploitedVulnCheck KEV evidence+2 yrs

See the family tree

3 related vulnerabilities in the same code over 10 days. The latest fix listed for github.com/KubeOperator/kubepi is 1.6.5.

Same bug familyLinked by evidence that a fix failed or the same code was patched again. Oldest first.

  1. This CVECVE-2023-22463KubePi's Hardcoded Jwtsigkeys allows malicious actor to login…4 Jan 2023
  2. relatedHigh

    Why these are linked:

    • Fixed one release later1.6.3 → 1.6.4 (github.com/KubeOperator/kubepi)
    • Same code patched: session.go, server.go (machine-matched)commit 3be58b8commit 1e9c550
    • Similar weakness in the same product (machine-matched)same product + description similarity
    CVE-2023-22479KubePi vulnerable to session fixation attack10 Jan 2023
  3. same family
    CVE-2023-22478KubePi is vulnerable to missing authorization14 Jan 2023

Fixes in github.com/KubeOperator/kubepiGo package, by fixed version. Earlier and later fixes in the same package, not necessarily the same bug.

  1. 1.6.3CVE-2023-224634 Jan 2023
  2. 1.6.4CVE-2023-2247910 Jan 2023
  3. 1.6.4CVE-2023-2247814 Jan 2023
  4. 1.6.5CVE-2023-3791621 Jul 2023Latest listed

techniques

No techniques linked

No ATT&CK techniques are linked to this CVE yet. MITRE CTID has not mapped it, and no report passage in the corpus ties it to a technique.

Am I affected? What do I upgrade to?

From GitHub Security Advisories and OSV

1 package in 1 ecosystem. Main package: github.com/KubeOperator/kubepi.

Gogithub.com/KubeOperator/kubepiGHSA-vjhf-8vqx-vqpqGO-2023-1283

Upgrade to 1.6.4 or later

Fixes this CVE and 1 other known vulnerability in this package (CVE-2023-22478).

Gogo get github.com/KubeOperator/kubepi@v1.6.4

First fixed in 1.6.3 for CVE-2023-22463.

Affected versions

If you runUpgrade to
All versions before 1.6.31.6.4first fix for this CVE: 1.6.3

“Up to” means the second version is the fix and is not affected.

Check your lockfile against all CVEs

What security researchers reported

Not named in any threat report yet

References

4 links, grouped by NVD tag

x_refsource_CONFIRM 1

github.com/KubeOperator/KubePi/security/advisories/GHSA-vjhf-8vqx-vqpq

x_refsource_MISC 3

github.com/KubeOperator/KubePi/commit/3be58b8df5bc05d2343c30371dd5fcf6a9fbbf8bgithub.com/KubeOperator/KubePi/blob/da784f5532ea2495b92708cacb32703bff3a45a3/internal/api/v1/session/session.go#L35github.com/KubeOperator/KubePi/releases/tag/v1.6.3
↑ ↓ chooseEnter openEsc close