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

What is CVE-2023-22463?

CVE-2023-22463 is a critical vulnerability in KubeOperator KubePi, published on 4 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

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.

Weakness: CWE-798

Which versions are affected by CVE-2023-22463?

3 open source packages ship an affected version, including github.com/KubeOperator/kubepi. It affects 1 product.

Products include Fit2cloud Kubepi.

How do I fix CVE-2023-22463?

Upgrade github.com/KubeOperator/kubepi to 1.6.3 or later.

Is CVE-2023-22463 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-22463 exists.

Public exploit code: 1 Nuclei template.

Other vulnerabilities in KubeOperator KubePi

• CVE-2023-37917 Privilege Escalation in kubepi Critical 9.1
• CVE-2023-22479 KubePi vulnerable to session fixation attack High 7.5
• CVE-2023-22478 KubePi is vulnerable to missing authorization High 7.3
• CVE-2023-37916 Leak password hash of any user Medium 6.5

Sources

• CVE record
• NVD
• OSV
• GitHub advisory
• How this page is made

Also known as GHSA-vjhf-8vqx-vqpq, GO-2023-1283.