CVE-2023-22463

KubePi is a k8s panel. The jwt authentication function of KubePi through version 1.6.2 uses hard-coded Jwtsigkeys, resulting in the same Jwtsigkeys for all online projects. This means that an attacker can forge any jwt token to take over the administrator account of any online project. Furthermore, they may use the administrator to take over the k8s cluster of the target enterprise. `session.go`, the use of hard-coded JwtSigKey, allows an attacker to use this value to forge jwt tokens arbitrarily. The JwtSigKey is confidential and should not be hard-coded in the code. The vulnerability has been fixed in 1.6.3. In the patch, JWT key is specified in app.yml. If the user leaves it blank, a random key will be used. There are no workarounds aside from upgrading.
Configurations

Configuration 1 (hide)

cpe:2.3:a:fit2cloud:kubepi:*:*:*:*:*:*:*:*

History

21 Nov 2024, 07:44

Type Values Removed Values Added
References () https://github.com/KubeOperator/KubePi/blob/da784f5532ea2495b92708cacb32703bff3a45a3/internal/api/v1/session/session.go#L35 - Third Party Advisory () https://github.com/KubeOperator/KubePi/blob/da784f5532ea2495b92708cacb32703bff3a45a3/internal/api/v1/session/session.go#L35 - Third Party Advisory
References () https://github.com/KubeOperator/KubePi/commit/3be58b8df5bc05d2343c30371dd5fcf6a9fbbf8b - Patch, Third Party Advisory () https://github.com/KubeOperator/KubePi/commit/3be58b8df5bc05d2343c30371dd5fcf6a9fbbf8b - Patch, Third Party Advisory
References () https://github.com/KubeOperator/KubePi/releases/tag/v1.6.3 - Release Notes, Third Party Advisory () https://github.com/KubeOperator/KubePi/releases/tag/v1.6.3 - Release Notes, Third Party Advisory
References () https://github.com/KubeOperator/KubePi/security/advisories/GHSA-vjhf-8vqx-vqpq - Exploit, Patch, Third Party Advisory () https://github.com/KubeOperator/KubePi/security/advisories/GHSA-vjhf-8vqx-vqpq - Exploit, Patch, Third Party Advisory
Summary
  • (es) KubePi es un panel de k8s. La función de autenticación jwt de KubePi hasta la versión 1.6.2 utiliza Jwtsigkeys codificadas, lo que da como resultado las mismas Jwtsigkeys para todos los proyectos en línea. Esto significa que un atacante puede falsificar cualquier token jwt para hacerse cargo de la cuenta de administrador de cualquier proyecto en línea. Además, pueden utilizar el administrador para hacerse cargo del clúster k8s de la empresa de destino. `session.go`, el uso de JwtSigKey codificado, permite a un atacante usar este valor para falsificar tokens jwt de forma arbitraria. La JwtSigKey es confidencial y no debe estar codificada en el código. La vulnerabilidad se ha solucionado en 1.6.3. En el parche, la clave JWT se especifica en app.yml. Si el usuario lo deja en blanco, se utilizará una clave aleatoria. No existen workarounds aparte de la actualización.

Information

Published : 2023-01-04 16:15

Updated : 2024-11-21 07:44


NVD link : CVE-2023-22463

Mitre link : CVE-2023-22463

CVE.ORG link : CVE-2023-22463


JSON object : View

Products Affected

fit2cloud

  • kubepi
CWE
CWE-798

Use of Hard-coded Credentials