T06 · System Persistence
- Location
SKILL.md:162- Finding
Recurring Scheduled Task Creates Cross-Session Persistence
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 162-167
Vulnerability Type: Scheduled-task persistence
Risk Level: Highbash openclaw cron add --name "Memory Deep Consolidation (Dream)" --every 12h --session isolated --timeout-seconds 600 --message "Check and execute memory deep consolidation (dream-rem)..." --announceTechnical Analysis
The installation instructions direct the user to register a recurring OpenClaw cron task. The task runs every 12 hours in an isolated session and invokes the skill without requiring approval for each execution.
This scheduled task survives the original skill run and repeatedly exercises the skill's declared file-read, file-write, and file-edit capabilities. The workflow permits updates and deletions across
topics/,MEMORY.md, andmemory/heartbeat-state.json. Consequently, the scheduler provides a persistent execution mechanism with access to long-term memory data.Although the scheduler supports the skill's advertised memory-consolidation function and must be installed manually, it still constitutes cross-session persistence under the audit classification.
Attack Path
- A user installs the skill and follows the documented post-installation instructions.
- The user executes the supplied
openclaw cron addcommand. - OpenClaw registers a persistent task that launches the skill every 12 hours.
- Each scheduled invocation scans daily memory files and may rewrite or delete topic content and index entries.
- Incorrect, compromised, or overly aggressive consolidation instructions can therefore cause recurring unattended modification or deletion of persistent memory.
Impact Assessment
The persistent task does not directly grant operating-system administrator privileges. Its scope is limited to the permissions available to the scheduled OpenClaw session. Within that scope, it can repeatedly:
- Read daily logs and topic memory files.
- R ...[truncated 361 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove automatic scheduled-task installation from the standard setup path.
- Require explicit, informed opt-in before creating any recurring task.
- Display the exact schedule, accessible files, modification scope, and removal command before installation.
- Default scheduled executions to a read-only dry-run that produces a proposed change set.
- Require interactive confirmation before writing, replacing, or deleting persistent memory.
- Create versioned backups before each consolidation and provide a documented rollback procedure.
- Restrict the scheduled session to the minimum required directories and permissions.
- Record an audit log containing every file read, changed, created, or deleted.
- Provide a command for inspecting and removing the cron task.
- Consider replacing indefinite recurrence with a one-time task that must be explicitly renewed.
