T06 · System Persistence
- Location
references/schedule-config.md:11- Finding
Persistent Cron Jobs Execute an Unbundled External Reminder Script
- Content
View full analysis
\ --message "" ``` ### Technical Analysis The Skill directs the Agent to modify the user's `crontab`, creating scheduled tasks that survive the current Skill invocation and execute every day. This constitutes system persistence. Recurring reminders are part of the declared functionality, so scheduling has a legitimate product purpose. However, direct modification of system cron exceeds the minimum privilege necessary when an application-scoped or Agent-managed scheduler could provide the same feature without establishing operating-system-level persistence. The cron entries execute `/root/.openclaw/scripts/cet4-reminder.sh`, but that script is not included in the audited project. Its behavior and integrity therefore cannot be verified. Any process able to create or replace the referenced script could cause cron to execute different commands automatically at the configured times. The use of a `/root` path also suggests execution in a highly privileged environment, although the project does not establish which account ultimately owns the cron entries. There is also a CET-4/CET-6 mismatch: the Skill declares CET-6 functionality while the cron configuration searches for and executes a CET-4 reminder. This can cause incorrect duplicate detection, accidental reuse of unrelated tasks, or execution of a script belonging to another Sk ...[truncated 1515 chars]- Remediation
View remediation
