CVE-2023-22463
CRITICALEPSS 99th pctlDescription
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.
How to fix
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Exploit Intelligence
Very high risk: more likely to be exploited than 99% of all known CVEs.
References
Related Vulnerabilities
Other CWE-798 (Hard-coded Credentials) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2022-26138 | Critical | 9.8 | 98% | KEV | - |
| CVE-2024-3272 | Critical | 9.8 | 98% | KEV | - |
| CVE-2019-15975 | Critical | 9.8 | 96% | - | Fix |
| CVE-2025-30406 | Critical | 9.0 | 94% | KEV | Fix |
| CVE-2024-28987 | Critical | 9.1 | 93% | KEV | Fix |
| CVE-2019-15976 | Critical | 9.8 | 93% | - | Fix |
Common questions
How do I fix CVE-2023-22463?
Upgrade kubepi to 1.6.3 or later.
Is CVE-2023-22463 being actively exploited?
Not that we know of. CVE-2023-22463 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 69.7% is the estimated probability that it will be exploited in the next 30 days. That is higher than 99% of all scored CVEs.
How severe is CVE-2023-22463?
CVE-2023-22463 has a CVSS v3 base score of 9.8, rated critical. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2023-22463 affect?
Published advisories record a fix for kubepi (NVD). Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2023-22463
Markdown
[](https://tridentstack.com/cve/CVE-2023-22463)HTML
<a href="https://tridentstack.com/cve/CVE-2023-22463"><img src="https://tridentstack.com/cve/badge/CVE-2023-22463.svg" alt="CVE-2023-22463"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2024-11-21.