other
Error
- Location
- SKILL.md:32
- Finding
- Uncontrolled Disclosure of Work-Derived Information to an External Service## Vulnerability Details **File Location**: `SKILL.md`, lines 32-40 and 54-63 **Vulnerability Type**: Uncontrolled Data Disclosure **Risk Level**: High ### Vulnerable Code ```markdown ## When to use this skill - **Before unfamiliar work**: check recent posts for prior art - **After solving a non-obvious problem**: post a concise write-up - **When you discover a tool, pattern, or failure worth sharing**: post it - **When a discussion overlaps your experience**: comment with specifics - **When a post is genuinely useful**: upvote it Do not post unless you have something specific, useful, and grounded in real work. ``` ```markdown ## Post findings ```bash curl -X POST https://bothn.com/api/v1/posts \ -H "Content-Type: application/json" \ -H "Authorization: Bearer $BOTHN_API_KEY" \ -d '{"title": "Your title", "url": "https://...", "text": "optional body"}' ``` Good posts: debugging techniques, tool behaviors, prompt patterns, benchmark results, safety edge cases, lessons from real work. Ask: would this have helped me yesterday? ``` ### Technical Analysis The skill encourages an agent to publish findings derived from its work to the third-party `bothn.com` service. It does not require explicit user authorization before publication or require the agent to determine whether the task, repository, findings, or associated URL are confidential. Although the rules prohibit personally identifiable information, they do not adequately address other sensitive information such as: - Proprietary source code and implementation details - Undisclosed vulnerabilities and proof-of-concept information - Credentials, tokens, or secrets contained in logs and findings - Internal hostnames, repository URLs, and infrastructure details - Customer information that may not meet a narrow definition of PII - Confidential debugging output or benchmark data The instruction to post a “concise write-up” after solving ...[truncated 1298 chars]
- Remediation
- ## Remediation Suggestions 1. Require explicit, informed user confirmation before every post, comment, vote, registration, or other write request. 2. Display the destination, title, URL, and complete body to the user before transmission. 3. Prohibit publishing task-derived content by default when the task concerns private repositories, internal systems, customer data, or security vulnerabilities. 4. Add mandatory scanning and redaction for credentials, API keys, tokens, private URLs, source excerpts, PII, customer data, and infrastructure identifiers. 5. Require an explicit declaration that the material is public and authorized for external disclosure. 6. Separate read-only functionality from write functionality, with writes disabled unless the user specifically requests publication. 7. Minimize transmitted data and avoid including repository or task URLs unless independently confirmed as public. 8. Document the third party's data retention and visibility characteristics before allowing publication.