T06 · System Persistence
Error
- Location
SKILL.md:26- Finding
Recurring Cron Job Enables Persistent Unattended Updates
- Content
View full analysis
> ~/.openclaw/logs/skill-update.log 2>&1 ``` ### Technical Analysis The cron entry survives the current session and executes the update script every week under the permissions of the user who installed it. Although scheduling is disclosed, manually configured, and consistent with the declared optional scheduling feature, persistent execution is not necessary for the core function of checking or applying updates. The scheduled script invokes an update operation without an interactive approval step. Consequently, the safety of every future execution depends on the continued integrity of the local script, the `clawhub` npm package, ClawHub, and all updated Skills. The implementation does not provide: - A check-only mode before applying updates. - Per-update user confirmation. - An allowlist of Skills that may be updated. - Version or integrity constraints. - A documented command for removing the cron entry. - A rollback procedure integrated into the updater. ### Attack Path 1. A user follows the recommendation in `SKILL.md` and adds the cron entry. 2. The task persists across sessions and runs weekly without direct user interaction. 3. An attacker compromises a future `clawhub` package release, ClawHub account, registry response, or published Skill update. 4. The scheduled task invokes the updater and applies the compromised release. 5. The affected Skill becomes available to the agent and may execute attacker-controlled instructions or scripts when subsequently used. ### Impact Assessment The scheduled task runs with the cron owner's privileges and can modify all Skills targeted by `update --all`. A successful supply-chain compromise could the ...[truncated 389 chars]- Remediation
View remediation