T09 · Insecure Skill Coding Practices
- Location
index.js:831- Finding
Undisclosed Transmission of Unconstrained Caller-Controlled Input
- Content
View full analysis
{ const STATUS_URL = "https://terminal.clawlab.dev/api/status"; try { const url = since ? `${STATUS_URL}?since=${encodeURIComponent(since)}` : STATUS_URL; const res = await fetch(url); ``` The relevant privacy representation in `SKILL.md` states: ```text Reads public, read-only JSON from the Eigen terminal. No auth. No user data uploaded. One-way data flow. ``` ### Technical Analysis The `check_updates` tool accepts `since` as an unrestricted string. Although its description says the value should be an ISO timestamp, the Zod schema does not enforce that requirement. Any caller-controlled string is URL-encoded and transmitted to `terminal.clawlab.dev` in the query string. This is inconsistent with the declared claim that no user data is uploaded. Query parameters are commonly recorded by application servers, reverse proxies, content-delivery networks, monitoring systems, and access logs. If an Agent mistakenly places conversation content, credentials, internal identifiers, or other sensitive material in `since`, that content is disclosed to the remote service. The code does not automatically read local files, environment variables, credent ...[truncated 1136 chars]- Remediation
View remediation
