The vulnerability exists in the Android client of OpenClaw, where the application failed to enforce TLS encryption for gateway connections to remote, non-loopback addresses. This allowed for the transmission of sensitive credentials in cleartext over unencrypted ws:// connections. The root cause was a lack of proper validation in multiple functions responsible for parsing, configuring, and establishing these connections. An attacker could exploit this by tricking a user into connecting to a malicious gateway via a crafted discovery beacon or setup code, leading to credential disclosure.
The patch addresses this by introducing a robust check, isLoopbackGatewayHost, to differentiate between local and remote endpoints. This check is now used throughout the connection process to enforce a strict security policy: all non-loopback connections must use TLS (wss://). The key modified functions, ConnectionManager.resolveTlsParamsForEndpoint and GatewayConfigResolver.parseGatewayEndpoint, now reject or upgrade connections to enforce this policy, effectively closing the transport-security gap.