CVE-2023-22463
Summary
| CVE | CVE-2023-22463 |
|---|---|
| State | PUBLIC |
| Assigner | [email protected] |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2023-01-04 16:15:00 UTC |
| Updated | 2023-01-10 19:08:00 UTC |
| 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. |
Risk And Classification
Problem Types: CWE-798
NVD Known Affected Configurations (CPE 2.3)
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| fix: 解决 jwt 硬编码导致的 k8s 集群接管漏洞 · KubeOperator/KubePi@3be58b8 · GitHub | MISC | github.com | |
| Release v1.6.3 · KubeOperator/KubePi · GitHub | MISC | github.com | |
| Hardcoded Jwtsigkeys allows malicious actor to login with a forged JWT token · Advisory · KubeOperator/KubePi · GitHub | MISC | github.com | |
| KubePi/session.go at da784f5532ea2495b92708cacb32703bff3a45a3 · KubeOperator/KubePi · GitHub | MISC | github.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.