CVE-2024-36111

See a problem?
Please try reporting it to the source first.

Source

https://cve.org/CVERecord?id=CVE-2024-36111

Import Source

https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-36111.json

JSON Data

https://api.osv.dev/v1/vulns/CVE-2024-36111

Aliases

GHSA-8q5r-cvcw-4wx7

Published

2024-07-25T13:26:13Z

Modified

2026-08-12T03:51:21Z

Severity

6.3 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L CVSS Calculator

Summary

KubePi's JWT token validation has a defect

Details

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.

Database specific

{
    "cna_assigner": "GitHub_M",
    "cwe_ids": [
        "CWE-1259"
    ],
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/36xxx/CVE-2024-36111.json"
}

References

Affected packages

Git / github.com/1panel-dev/kubepi

Affected ranges

Type

GIT

Repo

https://github.com/1panel-dev/kubepi

Events

Introduced

eead48749050a1bc47c710acb8267211a387a85d

Fixed

808aa4f532151a10abd83f60481de3a7a018d3db

Database specific

Show details

{
    "extracted_events": [
        {
            "introduced": "1.6.3"
        },
        {
            "fixed": "1.8.0"
        }
    ],
    "source": "AFFECTED_FIELD"
}

Affected versions

v1.*

v1.6.3

v1.6.4

v1.6.5

v1.7.0

Database specific

source

"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-36111.json"