T09 · Insecure Skill Coding Practices
- Location
src/interchange.js:94- Finding
Raw Task Telemetry Is Published in a Shareable Operations Report
- Content
View full analysis
`- ${e.command}: ${e.error || 'unknown error'}`).join('\n')} `; await writeMd(path.join(INTERCHANGE_DIR, 'ops', 'health.md'), meta, content); ``` The underlying values are selected without redaction in `src/reports.js:48-50`: ```js const recentErrors = db.prepare(` SELECT command, error, timestamp FROM task_events WHERE status != 'success' AND timestamp > datetime('now', '-7 days') ORDER BY timestamp DESC LIMIT 5 `).all(); ``` ### Technical Analysis The Skill documentation states that `interchange/monitoring/ops/health.md` is shareable and contains status indicators only, while detailed information is reserved for the private `state` layer. The implementation violates this boundary by publishing raw task command and error strings in the operations-layer report. Task commands and errors commonly contain file paths, user identifiers, request fragments, prompts, infrastructure names, exception details, or accidentally logged credentials. Neither the collector nor the report generator redacts these values before writing them to the shareable file. Although no network transmission is implemented, the README explicitly describes interchange reports as available for ...[truncated 1378 chars]- Remediation
View remediation
