T09 · Insecure Skill Coding Practices
- Location
references/skip-patterns.md:49- Finding
Unsafe Guidance Encourages Plaintext Disclosure of Sensitive Credentials
- Content
View full analysis
Vulnerability Details
File Location:
references/skip-patterns.md:49
Vulnerability Type: Plaintext sensitive-data exposure through unsafe user guidance
Risk Level: MediumVulnerable Code Snippet
markdown - **Sensitive list is non-overridable.** `.env`, `*.pem`, `*.key`, and credential files are always skipped even when explicitly passed. If a caller needs those contents, they paste them in directly rather than routing through this skill.Technical Analysis
The skill correctly prevents filesystem scanning of sensitive files such as environment files, private keys, and credential files. However, its documented fallback tells callers to paste those contents directly into the conversation.
This guidance circumvents the denylist's security purpose. Pasted secrets can enter model context, conversation logs, telemetry, or downstream processing. The issue does not constitute an automatic SSH-key operation, credential read, or exfiltration mechanism; it is an insecure usage instruction that may cause users to disclose sensitive material manually.
An attacker or untrusted document could exploit this behavior socially by claiming that omitted credential contents are necessary for analysis and directing the user to follow the documented fallback.
Attack Path
- A caller requests analysis involving a sensitive file such as
.env, an SSH private key, or a credential file. - The skill correctly excludes that file under its non-overridable denylist.
- The caller follows the documented instruction to paste the file contents directly.
- Plaintext tokens, passwords, cloud credentials, certificates, or private keys enter the agent's conversational context.
- Those secrets may subsequently be retained in logs, included in downstream processing, or exposed to any system or person with access to the conversation.
Impact Assessment
Successful exploitation requires the caller to follow the unsafe instruction; the skill does not inde ...[truncated 549 chars]
- A caller requests analysis involving a sensitive file such as
- Remediation
View remediation
Remediation Suggestions
- Remove the instruction to paste sensitive files or credentials into the conversation.
- Replace it with explicit guidance to provide only a sanitized copy or narrowly scoped redacted excerpt.
- Warn callers never to submit private keys, passwords, access tokens, session cookies, recovery codes, or complete credential files.
- Require secret values to be replaced with conspicuous placeholders such as
REDACTED_API_TOKEN. - Preserve only non-secret structure when needed for analysis, for example variable names without values.
- Add a pre-processing rule that rejects or warns on likely private-key blocks, token formats, and unredacted credential assignments in user-provided text.
- Ensure sensitive text is not forwarded to subagents, findings files, reports, logs, or persistent memory.
- Document a secure alternative workflow, such as creating a temporary sanitized copy outside the sensitive path and scanning only that copy after user verification.
