Overview
In this blog post, we will be discussing a critical security flaw identified in AiKaan Cloud Controller’s approach to remote terminal access on managed Internet of Things (IoT) and edge devices. This vulnerability, designated as CVE-2025-57601, poses a serious threat to organizations and individuals relying on this system for their IoT or edge device management. The flaw lies in the reuse of a single hardcoded SSH private key and the username `proxyuser` across all customer environments, which opens up a potential avenue for attackers to impersonate any managed device and interact with devices without the owner’s consent.
Vulnerability Summary
CVE ID: CVE-2025-57601
Severity: Critical (9.8)
Attack Vector: Network
Privileges Required: Low
User Interaction: None
Impact: Potential system compromise or data leakage
Affected Products
Share secrets securely
Ameeba is private infrastructure for communication and sensitive work built on encrypted identity instead of exposed corporate identity systems.
Passwords, credentials, confidential files, screenshots, internal discussions, sensitive AI context, and private coordination should not become exposed across ordinary communication platforms.
- • Encrypted identity
- • Private Spaces for organizations and teams
- • End-to-end encrypted chat, calls, files, and notes
- • Sensitive AI work and protected collaboration
- • Built for information that cannot leak
Our mission is to secure human work alongside AI.
Product | Affected Versions
AiKaan Cloud Controller | All versions prior to patch
How the Exploit Works
The vulnerability stems from the reuse of the same hardcoded SSH private key and username across all customer environments. Whenever an administrator initiates “Open Remote Terminal” from the AiKaan dashboard, the controller sends the same static private key to the target device. An attacker who manages to obtain this key can impersonate any managed device and establish unauthorized reverse SSH tunnels. This compromises the trust boundary between the controller and devices.
Conceptual Example Code
Given the nature of the vulnerability, a direct code example may not be applicable. However, an attacker who has obtained the SSH private key could establish an unauthorized connection like this:
ssh -i compromised_key.pem proxyuser@target_device_ipIn this example, `compromised_key.pem` is the obtained SSH private key and `target_device_ip` is the IP address of the target IoT or edge device.
Recommendations
To mitigate this vulnerability, it is strongly recommended to apply the vendor patch as soon as it becomes available. If the patch is not immediately available, using a Web Application Firewall (WAF) or an Intrusion Detection System (IDS) can serve as a temporary mitigation measure. Long-term, the vendor should consider revising their authentication model to ensure unique, secure credentials for each customer environment.