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.
Metrics
Affected Vendors & Products
References
History
No history.
MITRE
Status: PUBLISHED
Assigner: GitHub_M
Published: 2023-01-04T15:04:18.195Z
Updated: 2024-08-02T10:13:48.349Z
Reserved: 2022-12-29T03:00:40.879Z
Link: CVE-2023-22463
Vulnrichment
No data.
NVD
Status : Modified
Published: 2023-01-04T16:15:09.143
Modified: 2024-11-21T07:44:51.303
Link: CVE-2023-22463
Redhat
No data.