chatcc-agent version 0.8.24 runs a daemon connecting to Tencent Cloud IM as a WebSocket client. It processes inbound peer messages of types 'terminal_command', 'terminal_input', and 'terminal_pty_*' as instructions to spawn or write to a local shell or PTY on the host. The function _handleAdvancedCommand invokes pty.spawn with the remote command string, and handleInput forwards peer-supplied bytes to the process's stdin. This creates a network-accessible remote-controlled command execution channel on the host machine. Although access is gated by JWT and paired-client authentication, the remote shell capability exists by design. The npm install script only performs local compilation and does not retrieve or execute remote code.

An attacker who can authenticate via the JWT or paired-client mechanism can execute arbitrary commands on the host machine running chatcc-agent 0.8.24. This provides full remote shell access, which could lead to complete system compromise. The risk depends on the security of the authentication mechanism and exposure of the WebSocket interface.

No official patch or fix is currently documented. Users should carefully evaluate the trustworthiness of the chatcc-agent package and its deployment environment. Restrict network access to the WebSocket interface and ensure strong authentication controls are in place. Monitor for unauthorized access attempts. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.