other
- Location
SKILL.md:28- Finding
Unprotected Transmission of User Content to a Third-Party API
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 28-55
Vulnerability Type: Unprotected Third-Party Data Disclosure
Risk Level: Mediumbash API_URL="https://test-gig-c-api.1haozc.com/api/wx/kjj/v1/customer/skill/call" USER_TEXT="$1" curl -s -X POST "$API_URL" \ -H "Content-Type: application/json; charset=UTF-8" \ -d "{\"content\":\"$USER_TEXT\"}"Technical Analysis
The skill sends the complete user-provided text to a nonstandard external API. Although the external request is documented and uses HTTPS, the skill does not require explicit user consent immediately before transmission, warn users against submitting sensitive information, redact sensitive values, or document the remote service's data retention and privacy guarantees.
Summarization inputs may contain personal information, credentials, confidential business documents, source code, or other proprietary material. All such content is placed in the
contentfield and disclosed to the remote service without data minimization.Attack Path
- A user asks the skill to summarize text containing confidential or personal information.
- The complete input is assigned to
USER_TEXT. - The skill constructs an HTTP request containing the complete input.
curltransmits the request totest-gig-c-api.1haozc.com.- The remote service receives the content and may process, log, or retain it according to policies not specified by the skill.
Impact Assessment
No local system privileges are obtained through this behavior. However, the operator of the remote endpoint can receive the complete submitted content. The disclosure scope is limited to data users provide for processing, but that data may include credentials, personal data, proprietary source code, internal documents, or regulated information. Subsequent use and retention cannot be assessed from the reviewed file.
- Remediation
View remediation
Remediation Suggestions
- Obtain explicit, informed user consent before transmitting content to the external service.
- Clearly identify the destination domain and explain that the complete input will leave the local environment.
- Warn users not to submit passwords, API keys, authentication tokens, personal information, regulated data, or confidential documents.
- Detect and redact common sensitive values before transmission.
- Minimize the transmitted data and send only the content required for the requested operation.
- Document the remote provider's ownership, retention period, logging practices, deletion process, and privacy policy.
- Prefer a trusted, contractually controlled, or locally hosted summarization endpoint for sensitive workloads.
- Provide a local-processing alternative when the user declines external transmission.
