T09 · Insecure Skill Coding Practices
- Location
tools/ClearID3v12.cs:21- Finding
Unrestricted File Modification Through a Predictable, Unvalidated File List
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill has a legitimate MP3-tag-cleaning purpose, but its implementation can overwrite or corrupt user files without enough scoping, validation, backup, or recovery.
Review this skill carefully before installing. It should only be used on backed-up MP3 copies or a disposable test folder, because malformed inputs or an incorrect file list could permanently alter or corrupt files. The fixed temp paths and missing compiled executable also mean users should verify exactly what will run in their environment.
tools/ClearID3v12.cs:21Unrestricted File Modification Through a Predictable, Unvalidated File List
tools/ClearID3v12.cs:99Malformed or Unsupported ID3 Data Can Cause Silent File Corruption
tools/ClearID3v12.cs:22Recursive Deletion of a Fixed Shared Temporary Directory
The tool copies modified content back over the original MP3 path with overwrite enabled, permanently changing user files and removing metadata without confirmation, backup retention, or atomic rollback. In an agent or automation context, this can cause irreversible data loss across many files if the input list is wrong or the parser behaves incorrectly.
The function writes reconstructed bytes directly to the target file path after parsing and rewriting binary data, with no integrity checks, backup, or recovery path. If parsing is incorrect or the file is malformed, the original media file can be truncated or corrupted, making this a real destructive-file-handling issue.
This markdown file contains user-facing instructions and behavior descriptions only in Chinese, which effectively forces a specific language for use of the skill. The policy for SQP-3 flags language or locale constraints when the skill does not explicitly offer a user choice or opt-in.
The program recursively deletes the entire temporary working directory and recreates it, but there is no confirmation prompt, warning message, or explanatory comment disclosing this destructive action to the user. Because recursive deletion can remove existing data in that path, users are not explicitly informed before the operation occurs.