T09 · Insecure Skill Coding Practices
- Location
scripts/ir_timeline_report.py:75- Finding
CSV Formula Injection in Generated Timeline Reports
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a coherent defensive incident-reporting helper, with some report-output safety flaws users should understand before use.
This skill is reasonable for local defensive IR reporting. Before installing or using it, treat incident data as untrusted, prefer JSON output for sensitive reports, avoid opening generated CSV files directly in spreadsheet software, render Markdown with raw HTML and remote loading disabled, and choose output paths carefully because existing files can be overwritten even with --dry-run.
scripts/ir_timeline_report.py:75CSV Formula Injection in Generated Timeline Reports
scripts/ir_timeline_report.py:59Unescaped Markdown and HTML Injection in Generated Reports
scripts/ir_timeline_report.py:122Dry-Run Mode Performs Filesystem Writes and Can Overwrite Output
Referenced artifact was not completely inspected
- Run `scripts/ir_timeline_report.py` to generate a deterministic timeline report.
The skill instructs use of a bundled Python script and reference files, which implies file read/write behavior, but it does not declare any explicit tool scope such as permissions or allowed-tools. This weakens least-privilege controls and can cause the agent runtime to grant or infer broader filesystem access than reviewers or operators expect, increasing the chance of unintended data exposure or artifact overwrites.
The script advertises a --dry-run mode but still creates directories and writes the output artifact unconditionally in render(). That mismatch can cause unintended filesystem changes, overwriting files or polluting working directories in automation pipelines that expect a no-side-effects preview mode.
No suspicious patterns detected.