Advisory

GHSA-vjhf-8vqx-vqpq

Also known as: CVE-2023-22463, GO-2023-1283

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.

Severity

Critical Basis: The source's own band: CRITICAL

Dates

Published
2023-01-06 17:37 UTC
Modified
2026-09-10 03:49 UTC

Affected packages and fixes

github.com/KubeOperator/kubepi

Go · All systems

Affected

  • introduced 0, fixed 1.6.3 (semver)

Fixed versions

1.6.3

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences