T09 · Insecure Skill Coding Practices
Warning
- Location
- skill.json:36
- Finding
- Mandatory Public Hosting May Expose Sensitive Deliverables## Vulnerability Details **File Location**: `skill.json`, line 36 **Vulnerability Type**: Insecure handling and disclosure of potentially sensitive deliverables **Risk Level**: Medium ### Vulnerable Configuration ```json "resources": "The absolute public URL to the formal deliverables. You must upload your generated files to a public repository or storage service and provide the valid link here. DO NOT paste raw text and DO NOT hallucinate fake URLs." ``` ### Technical Analysis The `deliver` command requires generated files to be uploaded to a **public** repository or storage service. It does not require classification of the deliverables, secret scanning, removal of personal data, or explicit user authorization before publication. Public hosting is broader than necessary for the declared purpose of delivering completed work. A private authenticated upload, access-controlled link, or direct submission mechanism could provide the Hive platform with the deliverables without making them available to arbitrary third parties. The network behavior in `index.ts` does not itself demonstrate unrelated credential exfiltration: the documented `HIVE_API_KEY` is sent in the `x-hive-api-key` header to the fixed HTTPS origin `https://uphive.xyz`. The identified risk instead arises from the configuration instruction requiring public disclosure of deliverable files. ### Attack Path 1. A client task causes the agent to generate deliverables containing proprietary source code, credentials, personal data, internal analysis, or other confidential material. 2. The agent follows the `resources` parameter instruction and uploads those files to a public repository or public storage service. 3. The agent submits the resulting public URL through the `deliver` command. 4. Unauthorized parties discover or receive the URL through repository browsing, search indexing, access logs, platform disclosure, or link forwarding. 5. Those parties retrieve and retain the exposed material, pote ...[truncated 801 chars]
- Remediation
- ## Remediation Suggestions 1. Remove the requirement that every deliverable be publicly hosted. 2. Support private repositories, authenticated uploads, time-limited signed URLs, and access-controlled sharing. 3. Require explicit, informed user approval before publishing any deliverable to a public location. 4. Add pre-publication scanning for API keys, passwords, private keys, tokens, personal data, and common confidential-file patterns. 5. Default to the least-public delivery mechanism and clearly identify when a destination is Internet-accessible. 6. Minimize link lifetime and access scope, and provide a revocation mechanism. 7. Document that proprietary, personal, regulated, or credential-bearing content must not be published publicly. 8. Where supported, submit deliverables directly to the authenticated Hive API instead of requiring an external public host.