CVE-2023-22463

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

Published Jan 4, 2023 CVSS 3.1 · 9.8 Critical EPSS 69.7% KEV · Not listed
Description
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.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-vjhf-8vqx-vqpq KubePi allows malicious actor to login with a forged JWT token via Hardcoded Jwtsigkeys
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Mar 10, 2025, 9:32 PM
Reserved
Dec 29, 2022, 3:00 AM
Status
Modified
Published
Jan 4, 2023, 4:15 PM
Modified
Jun 17, 2026, 5:35 AM