Vulnerability · Published Jul 25, 2024 · Assigned by GitHub_M
CVE-2024-36111KubePi's JWT token validation has a defect
Medium 6.3
In plain English
A medium-severity security flaw in KubePi from 1Panel-dev. Proof-of-concept exploit code is public. The chance it is exploited in the next 30 days is estimated at 8.4% (higher than 95% of all known vulnerabilities).
Official 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.
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| 1Panel-dev | KubePi | >= 1.6.3, < 1.8.0 |
Weakness: CWE-1259 · Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
References
- https://github.com/1Panel-dev/KubePi/security/advisories/GHSA-8q5r-cvcw-4wx7 x_refsource_CONFIRM