T05 · Unauthorized Access and Privilege Escalation
Error
- Location
references/commands.md:10- Finding
SSH setup defaults to persistent root-level remote access
- Content
View full analysis
[user] [port] ``` ```markdown | Argument | Required | Default | Description | |----------|----------|---------|-------------| | `` | Yes | - | IP or hostname | | `[user]` | No | `root` | SSH username | | `[port]` | No | `22` | SSH port | ``` ```bash claw2claw setup 192.168.1.100 claw2claw setup 192.168.1.100 admin claw2claw setup 192.168.1.100 admin 2222 claw2claw setup myserver.example.com ``` ```markdown ### What Happens 1. Tests SSH connectivity 2. Adds SSH key to remote if needed 3. Saves config to `~/.claw2claw.conf` ``` `SKILL.md:35`: ```bash claw2claw setup 192.168.1.100 --user root ``` `SKILL.md:77-81`: ```bash REMOTE_HOST="192.168.1.100" # Remote IP/hostname REMOTE_USER="root" # SSH user REMOTE_PORT="22" # SSH port SSH_KEY="/path/to/key" # Custom SSH key RSYNC_BWLIMIT=1000 # KB/s limit ``` `references/examples.md:65-74`: ```markdown ## Multi-Agent Setup **Agent A:** ```bash claw2claw setup --user root ``` **Agent B:** ```bash claw2claw setup --user root ``` ``` ### Technical Analysis The documented `setup` workflow defaults to the `root` SSH account and states that it adds an SSH key to the remote system. The examples also recommend reciprocal root setup between two agents. This creates persistent, key-based administrative access even though ordinary file transfer generally requires access only to designated source and destination directories. This exceeds the minimum privileges necessary for the declared file-transfer functionality. A dedicated, unprivileged transfer account with narro ...[truncated 1895 chars]- Remediation
View remediation