CVE-2024-36111: KubePi's JWT token validation has a defect
1Panel-dev · KubePi
Affected: 1Panel-dev KubePi · Exploitation: possible (1 to 10%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 95% of scored CVEs
DescriptionCVE.org
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 products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- 1Panel-dev · KubePi>= 1.6.3, < 1.8.0
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Possible (1 to 10%). EPSS between 1% and 10%.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- 1Panel-dev
- Published
- July 2024
CoverageNo articles yet
No CyberSIXT article names CVE-2024-36111 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.