T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:26- Finding
Default Diagnostic Workflow Requests Excessive Privileged System Access
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
Cron Doctor is a coherent cron troubleshooting skill, but its default workflow asks the agent to inspect system-wide cron files and logs with elevated access before clear user approval.
Review this skill before installing. If used, keep diagnostics user-scoped first with `crontab -l`, do not grant sudo or broad log access unless you specifically need a system-wide cron audit, and review or redact sensitive paths, usernames, command arguments, and secrets before saving the generated report.
SKILL.md:26Default Diagnostic Workflow Requests Excessive Privileged System Access
The trigger list includes broad natural-language phrases such as 'job not running' and 'backup failed', which can cause the skill to activate in contexts broader than intended. Overbroad activation increases the chance the agent will run diagnostic commands or recommend actions on the wrong task or host context without clear user intent.
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
# List user's crontab
crontab -l
# List system crontabs
sudo cat /etc/crontab
The skill explicitly instructs use of 'sudo cat /etc/crontab', which encourages privileged command execution. In an agent setting, unnecessary escalation expands the blast radius of mistakes and can normalize prompting for or using elevated access even when user-level diagnostics would suffice.
crontab -l
sudo cat /etc/crontab ls -la /etc/cron.d/
The skill instructs the agent to write a report to ~/workspace/reports/cron-health-YYYY-MM-DD.md without warning the user that local files will be created or modified. Even though the write target is limited, silent filesystem modification violates least surprise and can overwrite or create artifacts the user did not explicitly authorize.
No suspicious patterns detected.