GHSA-vjhf-8vqx-vqpq

Suggest an improvement
Source
https://github.com/advisories/GHSA-vjhf-8vqx-vqpq
Import Source
https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2023/01/GHSA-vjhf-8vqx-vqpq/GHSA-vjhf-8vqx-vqpq.json
JSON Data
https://api.osv.dev/v1/vulns/GHSA-vjhf-8vqx-vqpq
Aliases
Published
2023-01-06T17:37:58Z
Modified
2023-11-08T04:11:35.736421Z
Severity
  • 9.8 (Critical) CVSS_V3 - CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H CVSS Calculator
Summary
KubePi allows malicious actor to login with a forged JWT token via Hardcoded Jwtsigkeys
Details

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.

https://github.com/KubeOperator/KubePi/commit/3be58b8df5bc05d2343c30371dd5fcf6a9fbbf8b : 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

Affected packages

Go / github.com/KubeOperator/kubepi

Package

Name
github.com/KubeOperator/kubepi
View open source insights on deps.dev
Purl
pkg:golang/github.com/KubeOperator/kubepi

Affected ranges

Type
SEMVER
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
1.6.3

Database specific

{
    "last_known_affected_version_range": "<= 1.6.2"
}