CVE-2024-36111
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.
Scoring
- Severity
- MEDIUM
- CVSS base score
- 6.3
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
- EPSS probability
- 8.39%
- CWE
- CWE-1259
- Published
- 2024-07-25
- Last modified
- 2026-03-13
Affected products
- 1Panel-dev KubePi
Weakness type
Related vulnerabilities
- CVE-2026-58429 — Public-Only Personal access tokens scope bypass in Organization and Permission Endpoints
- CVE-2026-54593 — Pterodactyl's improper JWT scoping allows subuser to upload files when not explicitly granted `file.create` permissions
- CVE-2026-25700 — Apache Answer: AdminToken not invalidated after admin deactivation
- CVE-2026-40264 — OpenBao's Token Store Allows Cross-Namespace Renewal, Revocation
- CVE-2024-45448 — Page table protection configuration vulnerability in the trusted firmware module...
- CVE-2024-41948 — biscuit-java vulnerable to public key confusion in third party block
- CVE-2022-23541 — jsonwebtoken's insecure implementation of key retrieval function could lead to Forgeable Public/Private Tokens from RSA to HMAC
- CVE-2022-23551 — AAD Pod Identity obtaining token with backslash