T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:32- Finding
Unrestricted Destructive System-Recovery Operations
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 32–36, 49–56, 101–105, 111–120
Vulnerability Type: Broadly authorized cleanup, rollback, garbage collection, and process-restart operations without least-privilege safeguards
Risk Level: HighRelevant Skill Directives
The following is an English rendering of the complete relevant directives:
markdown ### 3. Redundancy Cleanup - Duplicate file detection - Temporary file cleanup - Resource release When the system encounters an exception or the user requests a health check: User: Clean up redundant files → Activate Auto Healer → Perform cleanup ### Rollback Strategy Version records: Retain the most recent N versions One-click rollback: Support rapid rollback Data consistency: Ensure data remains complete after rollback ### Memory Leak Detection - Monitor memory usage trends - Automatically trigger garbage collection after exceeding a threshold - Record leak patterns ### Process Exception Detection - Heartbeat monitoring - Restart unresponsive processes - Resource exhaustion protectionTechnical Analysis
The Skill authorizes an agent to perform state-changing system operations, including deleting duplicate or temporary files, releasing resources, rolling back versions, triggering garbage collection, and restarting processes. It does not define:
- Permitted filesystem roots or file allowlists.
- Criteria for determining whether a file is temporary or duplicated.
- Protection against symbolic-link traversal or deletion outside an approved workspace.
- Process ownership checks or an allowlist of restartable services.
- Required user confirmation before each mutation.
- Dry-run behavior or presentation of exact targets.
- Backup, transaction, or restoration requirements before cleanup.
- Privilege restrictions for filesystem and process-management tools.
- Concrete thresholds and validation rules for automatic garbage collection.
- Controls preventing rollback to an unsafe o ...[truncated 2070 chars]
- Remediation
View remediation
Remediation Suggestions
- Make diagnosis read-only by default and separate diagnosis from remediation.
- Require explicit user approval immediately before each deletion, rollback, garbage-collection action, resource release, or process restart.
- Present an exact target list and anticipated impact before requesting approval.
- Restrict cleanup to configured, canonicalized workspace directories and explicitly approved temporary directories.
- Reject targets outside approved roots and prevent symbolic-link, hard-link, and path-traversal escapes.
- Define reliable file-classification criteria, retention periods, exclusions, and size or age thresholds.
- Use a dry-run mode by default and move files to a recoverable quarantine area instead of permanently deleting them.
- Create verified backups or snapshots before rollback and destructive cleanup.
- Permit process restarts only for an explicit allowlist, after validating process ownership, identity, dependencies, and restart limits.
- Run the Skill without elevated privileges and expose only the minimum tools required for the approved task.
- Require bounded resource thresholds, rate limits, cooldown periods, and circuit breakers for automatic recovery.
- Record targets, approvals, actions, outcomes, and restoration information in an audit log.
- Validate rollback compatibility and data integrity both before and after restoration.
- Stop and request operator intervention when target classification is ambiguous or when recovery affects shared or production resources.
