CVE-2024-36111

{"id": "CVE-2024-36111", "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 6.3, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L", "integrityImpact": "LOW", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "LOW", "privilegesRequired": "LOW", "confidentialityImpact": "LOW"}, "impactScore": 3.4, "exploitabilityScore": 2.8}]}, "published": "2024-07-25T14:15:12.650", "references": [{"url": "https://github.com/1Panel-dev/KubePi/security/advisories/GHSA-8q5r-cvcw-4wx7", "source": "security-advisories@github.com"}, {"url": "https://github.com/1Panel-dev/KubePi/security/advisories/GHSA-8q5r-cvcw-4wx7", "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-1259"}]}], "descriptions": [{"lang": "en", "value": "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."}, {"lang": "es", "value": "KubePi es un panel K8. A partir de la versi\u00f3n 1.6.3 y anteriores a la versi\u00f3n 1.8.0, existe un defecto en la verificaci\u00f3n del token JWT de KubePi. La clave JWT en el archivo de configuraci\u00f3n predeterminado est\u00e1 vac\u00eda. Aunque se generar\u00e1 una cadena aleatoria de 32 bits para sobrescribir la clave en el archivo de configuraci\u00f3n cuando se detecta que la clave est\u00e1 vac\u00eda en la l\u00f3gica de lectura del archivo de configuraci\u00f3n, la clave est\u00e1 vac\u00eda durante la verificaci\u00f3n real. El uso de una clave vac\u00eda para generar un token JWT puede omitir la verificaci\u00f3n de inicio de sesi\u00f3n y tomar el control directamente del back-end. La versi\u00f3n 1.8.0 contiene un parche para este problema."}], "lastModified": "2024-11-21T09:21:38.497", "sourceIdentifier": "security-advisories@github.com"}