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.
References
Link | Resource |
---|---|
https://github.com/KubeOperator/KubePi/blob/da784f5532ea2495b92708cacb32703bff3a45a3/internal/api/v1/session/session.go#L35 | Third Party Advisory |
https://github.com/KubeOperator/KubePi/commit/3be58b8df5bc05d2343c30371dd5fcf6a9fbbf8b | Patch Third Party Advisory |
https://github.com/KubeOperator/KubePi/releases/tag/v1.6.3 | Release Notes Third Party Advisory |
https://github.com/KubeOperator/KubePi/security/advisories/GHSA-vjhf-8vqx-vqpq | Exploit Patch Third Party Advisory |
Configurations
History
No history.
Information
Published : 2023-01-04 16:15
Updated : 2024-02-28 19:51
NVD link : CVE-2023-22463
Mitre link : CVE-2023-22463
CVE.ORG link : CVE-2023-22463
JSON object : View
Products Affected
fit2cloud
- kubepi
CWE
CWE-798
Use of Hard-coded Credentials