T09 · Insecure Skill Coding Practices
- Location
SKILL.md:177- Finding
Unrestricted Third-Party Processing of Task Content
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 177-190
Vulnerability Type: Uncontrolled transmission of task content to an external AI service
Risk Level: MediumVulnerable Code
python SKILLBOSS_API_KEY = os.environ["SKILLBOSS_API_KEY"] def pilot(body: dict) -> dict: r = requests.post( "https://api.heybossai.com/v1/pilot", headers={"Authorization": f"Bearer {SKILLBOSS_API_KEY}", "Content-Type": "application/json"}, json=body, timeout=60, ) return r.json() # LLM reasoning / analysis result = pilot({"type": "chat", "inputs": {"messages": [{"role": "user", "content": "Analyze this data..."}]}, "prefer": "balanced"}) text = result["result"]["choices"][0]["message"]["content"]Technical Analysis
The Skill instructs sub-agents requiring AI capabilities to submit task content to
https://api.heybossai.com/v1/pilot. The request body can contain prompts and data derived from files supplied to an agent. No controls require agents to classify the information, redact secrets, minimize the request, obtain task-specific approval, or prefer local processing.The bearer token is transmitted to its intended API endpoint over HTTPS and is not, by itself, evidence of credential exfiltration. The security issue is that arbitrary task content may be sent to a third party without safeguards. Such content could include proprietary source code, internal documents, customer information, credentials, or other regulated data.
Remote AI processing can support the declared functionality, but it is not necessary for the core local orchestration workflow. Making it a broadly recommended backend therefore exceeds minimum privilege unless external transmission is explicitly authorized for the specific task.
Attack Path
- A user supplies confidential content as part of an orchestration task.
- The orchestrator places that content, or instructions de ...[truncated 1026 chars]
- Remediation
View remediation
Remediation Suggestions
- Make remote AI processing opt-in for each task rather than the default recommendation.
- Clearly notify the user of the destination service and categories of data that will be transmitted.
- Require explicit approval before sending file contents, source code, personal information, or internal documents.
- Add a local-only execution mode for orchestration and analysis.
- Introduce secret detection and redaction for API keys, passwords, private keys, access tokens, connection strings, and personal data.
- Minimize requests by transmitting only the specific fields required for the operation rather than complete files or datasets.
- Define request-size and data-classification policies and reject prohibited content.
- Document the external provider's retention, training, residency, logging, and deletion policies.
- Check HTTP status codes, validate response schemas, and handle errors without logging request bodies or credentials.
- Restrict outbound connections to approved endpoints through an enforceable network allowlist.