Unauthenticated Remote Code Execution in AutoAgent

Executive Summary

AutoAgent has an unauthenticated remote code execution vulnerability in its TCP server. The server binds to all network interfaces (0.0.0.0) on a published port (default 12347) without requiring authentication. Attackers can connect remotely and execute arbitrary bash commands as root inside the container. The container runs as root and mounts the host workspace directory, allowing attackers to read and write host files.

Useful 0 Not Useful 0

Detection Guidance

Check if AutoAgent's TCP server is running on port 12347 by using netstat or ss commands like 'netstat -tulnp | grep 12347' or 'ss -tulnp | grep 12347'. If the port is open and bound to 0.0.0.0, the service is exposed and vulnerable.

Useful 0 Not Useful 0

Impact Analysis

This vulnerability allows attackers to execute arbitrary commands as root within the container. They can gain access to bind-mounted host workspace directories, potentially reading or modifying sensitive host files. Attackers could also move laterally within the network or escalate privileges to the host system.

Useful 0 Not Useful 0

Compliance Impact

This vulnerability likely violates compliance requirements for data protection and security. It enables unauthorized access to sensitive data stored in bind-mounted directories, which could lead to data breaches. Organizations using AutoAgent may fail to meet GDPR's data protection principles or HIPAA's security requirements for protected health information.

Useful 0 Not Useful 0

Mitigation Strategies

Stop the AutoAgent container immediately. Update to the latest version that binds the TCP server to localhost only and adds authentication. Avoid running containers as root and remove shell=True usage in command execution.

Useful 0 Not Useful 0