T06 · System Persistence
- Location
SKILL.md:69- Finding
Persistent Scheduled Execution of an Unverified External Script
- Content
View full analysis
> /workspace/logs/hotnews.log 2>&1 ``` ``` ### Technical Analysis The Skill directs the environment to configure a recurring cron job that executes `/workspace/scripts/read_hotnews.py` every day. Scheduled tasks survive the original Skill invocation and create a cross-session execution mechanism, matching `T06: System Persistence`. The referenced Python script is not included in the audited project, which contains only `SKILL.md`. Its implementation, integrity, ownership, and write permissions therefore cannot be verified. Because the cron entry references a mutable external path, any party capable of creating or replacing `/workspace/scripts/read_hotnews.py` could cause arbitrary Python code to execute under the cron owner's account. The redirection also appends output to `/workspace/logs/hotnews.log`, allowing repeated execution to continue without interactive visibility. The cron expression itself does not establish which user installs it, so the exact privileges depend on the account under which the scheduled task is configured. ### Attack Path 1. A user activates the Skill while processing a matching Excel file. 2. The Skill's scheduling instruction is followed and the cron entry is installed. 3. The scheduled task remains active after the original processing session ends. 4. An attacker who can create or modify `/workspace/scripts/read_hotnews.py` places attacker-controlled Python code at that path. 5. At 08:00, cron changes the working directory to `/workspace` and executes the modified script. 6. The attacker's code runs with the ...[truncated 666 chars]- Remediation
View remediation
