Approved changes feed: RSS · Atom
cpe:2.3:a:1panel_dev:kubepi:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | 1Panel Dev (438285da-68c9-5e98-b453-2574eecb2851) |
|---|---|
| Product | Kubepi (5ec8328d-aed7-5bca-b164-578edb362796) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-36111 |
vulnerable | 2026-06-08 06:39:43.658339 |
KubePi's JWT token validation has a defect
MEDIUM (6.3)
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.
Published: 2024-07-25T13:26:13.257Z
Updated: 2024-08-02T03:30:12.864Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.