other
- Location
SKILL.md:38- Finding
File Upload Behavior Contradicts Privacy Disclosure
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:38-39, 339-350; corroborated byclawhub.json:238, 365-366andLISTING.txt:123-125
Vulnerability Type: Misleading Privacy Disclosure
Risk Level: MediumVulnerable Code Snippets
SKILL.md:38-39:markdown - **What data is sent**: Only card data (titles, descriptions, comments, status changes) and board metadata. No user PII, agent secrets, source code, or environment variables are ever transmitted. - **What data is NOT sent**: No user credentials, private keys, environment variables, file contents, agent configuration, or personal information of any kind.SKILL.md:339-350:markdown ### 11. Upload a file Upload a file to get a hosted URL, then attach it to a card or comment. File uploads are subject to per-tier limits on file size and total upload count (URL-based attachments are not limited). **POST** `https://dashboard.simplysemantics.com/hub/upload` Headers: ```text x-api-key: ${SEMANTIC_HUB_API_KEY} Content-Type: multipart/form-dataBody (multipart form):
file— the file to upload
text `clawhub.json:238`: ```json "description": "Upload a file and get a hosted URL. Subject to per-tier limits on file size and upload count. Use the returned URL to attach to a card or comment."clawhub.json:365-366:json "dataSent": "Only card data (titles, descriptions, comments, status) and board metadata. No user PII, agent secrets, source code, or environment variables are ever transmitted by the agent.", "dataNotSent": "No user credentials, private keys, environment variables, file contents, or personal information of any kind."LISTING.txt:123-125:text POST /hub/upload Upload a file (multipart/form-data, field: file) Returns: { filename, url, size }Technical Analysis
The privacy disclosure categorically states that file contents are never transmitted. However, the documented upload workflow instructs the agent to submit a selected f ...[truncated 2301 chars]
- Remediation
View remediation
Remediation Suggestions
- Replace the categorical claim that file contents are never transmitted with an accurate disclosure stating that user-selected files are transmitted to and stored by Semantic Hub when the upload feature is used.
- Disclose all relevant transmitted data, including file contents, original filenames, sizes, MIME types, and request metadata.
- Document file retention and deletion behavior, storage location, encryption protections, hosted-URL accessibility, and which users can view attachments.
- Require explicit user confirmation immediately before uploading a local file, especially where its contents have not been reviewed for sensitive information.
- Warn users not to upload credentials, private keys, access tokens, confidential source code, or logs containing secrets.
- Provide a preview or summary of the destination, filename, and intended card or comment before transmission.
- Apply server-side file-size and content-type allowlists, malware scanning, randomized object identifiers, authenticated download authorization, and tenant isolation.
- Ensure hosted attachment URLs are access-controlled and expire where appropriate rather than functioning as indefinitely accessible bearer URLs.
- Provide attachment deletion and data-erasure mechanisms and describe them accurately in the privacy policy.
- Synchronize the privacy language across
SKILL.md,clawhub.json, andLISTING.txtso all package metadata consistently reflects actual upload behavior.
