CVE-2023-22463

high-risk
Published 2023-01-04

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.

Do I need to act?

!
91.5% chance of exploitation in next 30 days
EPSS score — higher than 8% of all CVEs
-
Not on CISA KEV list
No confirmed active exploitation reported to CISA
?
Patch status unknown
Check vendor advisories for fix availability and mitigation guidance
9
CVSS 9.8/10 Critical
NETWORK / LOW complexity

Affected Products (1)

Affected Vendors

Fit2Cloud

References (8)

Third Party Advisory https://github.com/KubeOperator/KubePi/blob/da784f5532ea2495b92708cacb32703bff3a...
Patch https://github.com/KubeOperator/KubePi/commit/3be58b8df5bc05d2343c30371dd5fcf6a9...
Release Notes https://github.com/KubeOperator/KubePi/releases/tag/v1.6.3
Exploit https://github.com/KubeOperator/KubePi/security/advisories/GHSA-vjhf-8vqx-vqpq
Third Party Advisory https://github.com/KubeOperator/KubePi/blob/da784f5532ea2495b92708cacb32703bff3a...
Patch https://github.com/KubeOperator/KubePi/commit/3be58b8df5bc05d2343c30371dd5fcf6a9...
Release Notes https://github.com/KubeOperator/KubePi/releases/tag/v1.6.3
Exploit https://github.com/KubeOperator/KubePi/security/advisories/GHSA-vjhf-8vqx-vqpq
57
/ 100
high-risk
Severity 32/34 · Critical
Exploitability 20/34 · Moderate
Exposure 5/34 · Minimal