CVE-2023-22463

KubePi allows malicious actor to login with a forged JWT token via Hardcoded Jwtsigkeys

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
}

Credentials are embedded in source code or a binary, making them accessible to anyone who can read the artifact. Typical impact: unauthorized access using the static credential.

CVE-2023-22463 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.6.3); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

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.

1. What is CVE-2023-22463? CVE-2023-22463 is a critical-severity use of hard-coded credentials vulnerability in github.com/KubeOperator/kubepi (go), affecting versions <= 1.6.2. It is fixed in 1.6.3. Credentials are embedded in source code or a binary, making them accessible to anyone who can read the artifact.
2. How severe is CVE-2023-22463? CVE-2023-22463 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/KubeOperator/kubepi are affected by CVE-2023-22463? github.com/KubeOperator/kubepi (go) versions <= 1.6.2 is affected.
4. Is there a fix for CVE-2023-22463? Yes. CVE-2023-22463 is fixed in 1.6.3. Upgrade to this version or later.
5. Is CVE-2023-22463 exploitable, and should I be worried? Whether CVE-2023-22463 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2023-22463 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2023-22463? Upgrade github.com/KubeOperator/kubepi to 1.6.3 or later.

Other vulnerabilities in github.com/KubeOperator/kubepi