Summary
The jwt authentication function of kubepi <= v1.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.
Details
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.
var JwtSigKey = []byte("signature_hmac_secret_shared_key")
var jwtMaxAge = 10 * time.Minute
type Handler struct {
userService user.Service
roleService role.Service
clusterService cluster.Service
rolebindingService rolebinding.Service
ldapService ldap.Service
jwtSigner *jwt.Signer
}Affected Version
<= v1.6.2
Patches
The vulnerability has been fixed in v1.6.3.
1Panel-dev/KubePi@3be58b8 : JWT key can be specified in app.yml, if leave it blank a random key will be used.
Workarounds
It is recommended to upgrade the version to v1.6.3.
For more information
If you have any questions or comments about this advisory, please open an issue.
References
Summary
The jwt authentication function of kubepi <= v1.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.
Details
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.Affected Version
<= v1.6.2
Patches
The vulnerability has been fixed in v1.6.3.
1Panel-dev/KubePi@3be58b8 : JWT key can be specified in app.yml, if leave it blank a random key will be used.
Workarounds
It is recommended to upgrade the version to v1.6.3.
For more information
If you have any questions or comments about this advisory, please open an issue.
References