T09 · Insecure Skill Coding Practices
- Location
scripts/gate-lock.py:63- Finding
Unrestricted Local File Read Through Gate Artifact Import
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a coherent planning workflow, but one helper can copy any readable local text file into persistent session artifacts if invoked with an unsafe path.
Review this before installing if you work in repositories with secrets or sensitive customer data. Only invoke gate-lock with gate files inside the active aidlc-sessions/<uuid>/gates directory, avoid putting secrets in gate artifacts, and consider patching the helper to reject paths outside the current session before broad use.
scripts/gate-lock.py:63Unrestricted Local File Read Through Gate Artifact Import
The skill is presented as a strict human-gated planning workflow, but the documented behavior includes creating persistent session state and relying on conventions for approvals and deconfliction rather than enforceable controls. If users or operators trust the description, they may assume safety properties that are not actually guaranteed, allowing unauthorized writes, stale-session confusion, or bypass of the claimed human-review process.
The README says users can invoke the skill by asking to 'start AIDLC for non-trivial work,' which is an ambiguous activation condition in markdown. It does not define what counts as 'non-trivial work' or provide exclusion examples, increasing the chance of unintended invocation.
The skill clearly instructs the agent to read and write workspace files and invoke local scripts, but it does not declare an explicit tool scope such as permissions or allowed-tools. That creates a trust and containment gap: a host may permit broader tool use than users expect, and the skill can perform filesystem mutations without a machine-readable restriction boundary.
No suspicious patterns detected.