Log in Start free

Vulnerability · Published Jan 4, 2023 · Assigned by GitHub_M

CVE-2023-22463KubePi's Hardcoded Jwtsigkeys allows malicious actor to login with a forged JWT token

Critical 9.8

In plain English

A critical-severity hard-coded credentials in KubePi from KubeOperator. Proof-of-concept exploit code is public. The chance it is exploited in the next 30 days is estimated at 69.7% (higher than 99.4% of all known vulnerabilities). Ready-made attack tooling exists: Nuclei. Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.0)9.8Critical
Exploit odds (30 days)69.7%top 0.6% of all CVEs
Exploited in the wildNo reportsCISA SSVC: poc
Attack tooling1Nuclei

Official description

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.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Gogithub.com/KubeOperator/kubepi1.6.3GHSA-vjhf-8vqx-vqpq
Gogithub.com/KubeOperator/kubepi1.6.3GO-2023-1283

Affected products (as reported)

VendorProductVersions
KubeOperator KubePi < 1.6.3

Weakness: CWE-798 · Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

References