T06 · System Persistence
- Location
README.md:4- Finding
Persistent Remote Access Through SSH Authorized-Key Installation
- Content
View full analysis
> ~/.ssh/known_hosts` 2. **免密配置**:必须完成 `ssh-copy-id` 授权。 ``` ### Technical Analysis The documented setup requires the user to run `ssh-copy-id`. This command normally adds a public key to the remote account's `~/.ssh/authorized_keys` file. The resulting authorization persists after the deployment process terminates and continues to permit authentication in future sessions. Although public-key authentication is appropriate for automated deployment, installing a persistent authorized key exceeds a single deployment run unless the key is separately managed, tightly restricted, and subject to a documented revocation process. Possession or later compromise of the corresponding private key would provide durable access to the remote deployment account. ### Attack Path 1. The user follows the mandatory setup instructions and runs `ssh-copy-id`. 2. The command adds the user's public key to the remote deployment account's `authorized_keys`. 3. The authorization remains installed after the Skill finishes. 4. An attacker later obtains the corresponding private key or access to the system holding it. 5. The attacker authenticates to the remote account without repeating the setup process. 6. The attacker exercises all permissions available to that deployment account. ### Impact Assessment A successful attacker obtains persistent access to the remote deployment account. The accessible scope includes files, commands, and services available to that account. The impact becomes substantially greater if the account is privileged, has broad write access, or can escalate privileges on the remote server. ]]>- Remediation
View remediation
