T09 · Insecure Skill Coding Practices
- Location
SKILL.md:103- Finding
API Credential Transmitted in a URL Query Parameter
- Content
View full analysis
`. 3. The complete request URL is retained by the agent platform, a proxy, the API service, or monitoring infrastructure. 4. An attacker or unauthorized operator with access to those records extracts the API key. 5. The attacker submits requests using the exposed key until it is revoked or expires. ### Impact Assessment An exposed credential could enable unauthorized use of the victim's InvestLog account, including consumption of paid query quotas and possible account-related charges. The access obtained is limited to the privileges granted to the compromised API key; the reviewed file provides no evidence that the key grants local system ...[truncated 65 chars]- Remediation
View remediation
``` 2. Update the API and Skill documentation so API keys are never embedded in URLs. 3. Ensure the agent platform, proxy, and API service redact authentication headers from logs and diagnostic output. 4. Avoid displaying credentials in tool-call transcripts or generated responses. 5. Rotate any API keys that may already have been used in query parameters. 6. Apply expiration, quota limits, and revocation controls to issued credentials. ]]>
