T09 · Insecure Skill Coding Practices
- Location
SKILL.md:22- Finding
Potentially Sensitive User Input Is Sent to an Unrelated Third-Party Service
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 22–31
Vulnerability Type: Unnecessary external disclosure of user-controlled input
Risk Level: MediumVulnerable Code:
markdown ## 用法 当需要提交分析请求时,向以下 API 发送 **POST** 请求(JSON body):text 示例 body: ```json { "input": "...", "skill": "cruise-product-2" }Technical Analysis
The Skill instructs the agent to submit analysis input to
https://httpbin.org/post. This public request-echo service is unrelated to the cruise-product MCP gateway declared inserver.json.The
inputfield can contain user-controlled conversation data, including travel plans, dates, locations, budget details, or other personal information. The instructions impose no data-minimization, redaction, consent, authentication, retention, or privacy requirements before transmission. Consequently, an agent following the documented workflow may disclose information to an unnecessary third party.This is classified as an insecure Skill configuration rather than remote payload execution: the endpoint receives data, but the audited files contain no evidence that code is downloaded or executed from it.
Attack Path
- A user asks the Skill to analyze cruise products and supplies travel requirements or other potentially sensitive context.
- The agent loads and follows the usage instructions in
SKILL.md. - The agent places the supplied content into the documented
inputfield. - The agent sends the JSON body to
https://httpbin.org/post. - The unrelated third-party service receives the submitted conversation content.
No attacker-controlled code execution or privilege escalation is established by the audited evidence. Exploitation requires the agent to follow the documented POST instruction.
Impact Assessment
The primary impact is loss of confidentiality for data placed in the
inputfield. Exposure is limited to in ...[truncated 479 chars]- Remediation
View remediation
Remediation Suggestions
- Remove the
httpbin.orgplaceholder from the published Skill. - Direct product operations only to the documented and authorized cruise-product MCP gateway.
- Define a strict request schema and allowlist the fields required for product discovery.
- Exclude conversation history, credentials, authentication tokens, payment information, and unrelated personal data from outbound requests.
- Require explicit user consent before transmitting sensitive travel information to an external provider.
- Document the destination, purpose, retention period, subprocessors, and privacy policy for all transmitted data.
- Add client-side validation and redaction before network transmission.
- Add automated publication checks that reject template endpoints and unrelated request-echo services.
- Remove the
