VulnerabilityDeferred

CVE-2024-36111

Using an empty key to generate a JWT token can bypass the login verification and directly take over the back end.

MEDIUM 6.3EPSS 8.39%

Does this matter?

Lower severity and a low EPSS score (8.39%). Track it; it rarely justifies an emergency change on its own.

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.

CVSS 3.1: 6.3 MEDIUMCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
EPSS: 8.39% probability · 95th percentile
CISA KEV: Not listed
Weakness: CWE-1259
Source: security-advisories@github.com

References

Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.