CVE-2024-36111

KubePi's JWT token validation has a defect

Published Jul 25, 2024 CVSS 3.1 · 6.3 Medium EPSS 8.4% KEV · Not listed
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.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History

No history.

Weaknesses

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Aug 2, 2024, 3:30 AM
Reserved
May 20, 2024, 9:07 PM
Status
Deferred
Published
Jul 25, 2024, 2:15 PM
Modified
Jun 17, 2026, 7:36 AM