CVE-2023-37917

9.1 CRITICAL

📋 TL;DR

This vulnerability in KubePi allows any authenticated user to elevate privileges to administrator by modifying the 'isadmin' parameter when creating or updating users. All KubePi deployments running vulnerable versions are affected, enabling complete administrative takeover of the Kubernetes management panel.

💻 Affected Systems

Products:
  • KubePi
Versions: Versions before 1.6.5
Operating Systems: All platforms running KubePi
Default Config Vulnerable: ⚠️ Yes
Notes: All deployments with user management functionality enabled are vulnerable. The vulnerability requires authenticated access but any user account can exploit it.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete compromise of the KubePi instance, allowing attackers to manage all Kubernetes resources, deploy malicious containers, exfiltrate sensitive data, and potentially pivot to the underlying Kubernetes cluster.

🟠

Likely Case

Unauthorized users gain administrative access to KubePi, enabling them to create/delete users, modify configurations, and access all Kubernetes resources managed through the panel.

🟢

If Mitigated

With proper network segmentation and access controls, impact is limited to the KubePi application itself, though administrative control still poses significant risk.

🌐 Internet-Facing: HIGH
🏢 Internal Only: HIGH

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: LIKELY
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploitation requires authenticated access but is trivial - simply modifying a parameter in user creation/update requests. No special tools or knowledge required.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 1.6.5

Vendor Advisory: https://github.com/1Panel-dev/KubePi/security/advisories/GHSA-757p-vx43-fp9r

Restart Required: Yes

Instructions:

1. Backup current KubePi configuration and data. 2. Stop KubePi service. 3. Update to version 1.6.5 using your deployment method (Docker, Kubernetes, or binary). 4. Restart KubePi service. 5. Verify functionality and that the fix is applied.

🔧 Temporary Workarounds

No official workarounds

all

The vendor advisory states there are no known workarounds for this vulnerability

🧯 If You Can't Patch

  • Isolate KubePi instance from production Kubernetes clusters and restrict network access
  • Disable user management functionality if possible and use only admin accounts

🔍 How to Verify

Check if Vulnerable:

Check KubePi version via web interface or API. If version is below 1.6.5, the system is vulnerable.

Check Version:

Check KubePi web interface dashboard or use API endpoint /api/v1/system/version

Verify Fix Applied:

After upgrading to 1.6.5, attempt to create a user with 'isadmin' parameter set to true using a non-admin account. This should fail with permission error.

📡 Detection & Monitoring

Log Indicators:

  • User creation/update requests with 'isadmin' parameter from non-admin users
  • Sudden privilege escalation events
  • Multiple admin user creation attempts

Network Indicators:

  • POST/PUT requests to user management endpoints with modified parameters
  • Unusual API calls from previously low-privilege accounts

SIEM Query:

source="kubepi" AND (uri_path="/api/v1/users" OR uri_path="/api/v1/user") AND (http_method="POST" OR http_method="PUT") AND request_body CONTAINS "isadmin"

🔗 References

📤 Share & Export