T09 · Insecure Skill Coding Practices
- Location
SKILL.md:66- Finding
Unsafe Handling of Temporary and Progress Files
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:66-69
Vulnerability Type: Unspecified temporary-file storage and lifecycle
Risk Level: LowVulnerable Instruction
markdown ### 7. Process Annotations and Memory Consolidation - During long tasks, every key finding must be written to a temporary file. - After each step, record a one-sentence summary in a progress file.The snippet is an English translation of the instructions at the specified location.
Technical Analysis
The Skill requires the Agent to write findings to temporary and progress files but does not specify a secure directory, restrictive file permissions, safe filename generation, content-minimization rules, retention limits, or cleanup procedures.
These files can contain sensitive information gathered during source-code reviews, including vulnerability details, proprietary implementation information, local paths, configuration data, and excerpts derived from private project material. If the Agent uses a shared temporary directory, predictable filename, permissive default mode, or persistent workspace location, another local process or user may be able to read the resulting artifacts.
The project does not contain code that deliberately exfiltrates these files, creates system persistence, or elevates privileges. Exploitation therefore depends on the runtime environment and the Agent's implementation of the instruction.
Attack Path
- A user asks the Agent to analyze a private repository or other sensitive material.
- Following
SKILL.md:66-69, the Agent records each key finding and progress summary in unspecified files. - The Agent creates those files in a shared or persistent location using default or overly permissive access controls.
- Sensitive findings remain available after the task or become accessible to another local user or process.
- The local principal reads the residual files and obtains information deri ...[truncated 579 chars]
- Remediation
View remediation
Remediation Suggestions
- Make progress-file creation optional and require explicit user approval before writing analysis artifacts.
- Store files only in a task-scoped private directory outside shared temporary locations.
- Create directories and files with owner-only permissions, such as directory mode
0700and file mode0600. - Generate unpredictable filenames using secure temporary-file APIs rather than fixed or user-controlled names.
- Record only minimal progress metadata; do not copy secrets, credentials, source contents, personal data, or complete vulnerability evidence into temporary files.
- Define a strict retention period and delete all temporary artifacts when the task ends, including during error handling or cancellation.
- Clearly distinguish temporary task notes from persistent Agent memory and prohibit cross-session retention by default.
- If durable records are required, disclose their exact location, contents, access controls, and retention policy to the user before creation.
