CVE-2024-36111 KubePi's JWT token validation has a defect
Attackers can bypass login and take over the backend by exploiting a defect where JWT verification uses an empty key despite configuration updates.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2024-36111?
CVE-2024-36111 is a medium-severity authentication bypass vulnerability in 1Panel-dev KubePi, published on 25 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim.
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.
Weakness: CWE-1259
Which versions are affected by CVE-2024-36111?
How do I fix CVE-2024-36111?
No fix has been published for CVE-2024-36111 yet. Limit exposure of the affected software until one is available.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is CVE-2024-36111 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-36111 exists.
Sources
Also known as GHSA-8q5r-cvcw-4wx7.