CVE-2024-36111
KubePi's JWT token validation has a defect
- State
- Published
- Severity
- 6.3 Medium
- Published
- Jul 25, 2024
- Updated
- Aug 2, 2024
- Reserved
- May 20, 2024
Description
KubePi is a K8s panel. Starting in version 1.6.3 and prior to version 1.8.0, there is a defect in the KubePi JWT token verification. The JWT key in the default configuration file is empty. Although a random 32-bit string will be generated to overwrite the key in the configuration file when the key is detected to be empty in the configuration file reading logic, the key is empty during actual verification. Using an empty key to generate a JWT token can bypass the login verification and directly take over the back end. Version 1.8.0 contains a patch for this issue.
Scores
| CVSS | Score | Vector | Source |
|---|---|---|---|
| 3.1 | 6.3 Medium | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L | GitHub_M |
Weaknesses
- CWE-1259 Improper Restriction of Security Token Assignment
Affected Products
| Product | Versions |
|---|---|
KubePi1Panel-dev |
|
References
Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.