T09 · Insecure Skill Coding Practices
- Location
scripts/run.py:110- Finding
Unrestricted API Endpoint Can Expose Credentials and Sensitive Medical Data
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill’s medical Q&A purpose is coherent, but it needs Review because it can send medical questions and an API key to any caller-supplied endpoint, including unsafe destinations.
Install only if you control the invocation and endpoint configuration. Do not submit identifiable patient data unless the chosen model provider is approved for that data, avoid overriding --api-url except to a trusted HTTPS endpoint, and prefer a safer secret channel than putting API keys directly in shell commands.
scripts/run.py:110Unrestricted API Endpoint Can Expose Credentials and Sensitive Medical Data
scripts/run.py:215API Credential Accepted Through a Command-Line Argument
The skill documentation exposes code-backed capabilities that can read files, write files, and make network requests, but it does not declare any explicit tool scope or permissions boundary. In a medical QA/prescription-review context, this is risky because the skill may process sensitive healthcare content, and undeclared I/O or outbound network access increases the chance of unintended data access or exfiltration.
The markdown states the skill should output answers strictly in the format required by the prompt, and the entire skill description and examples are presented as Chinese-only usage for a general-purpose Q&A skill. There is no indication that users may choose another language or that the Chinese-only constraint is justified as a region-specific requirement.
The file-level description and all user-facing CLI/help text are written only in Chinese, and the system prompt is also fixed in Chinese. This imposes a specific language/locale expectation without presenting an explicit language choice or documenting a justified region-specific constraint.
The code transmits raw user-supplied medical questions to an external HTTPS API, and those questions may contain sensitive health or personal information. In a medical context, undisclosed off-host transmission materially increases privacy, compliance, and data-governance risk, especially because the tool accepts arbitrary stdin/files and forwards content verbatim.