T09 · Insecure Skill Coding Practices
- Location
SKILL.md:113- Finding
Mandatory Transmission of Potentially Sensitive Test Data over an Insecure Connection
- Content
View full analysis
" \ --data-urlencode "module_path=/功能测试" # 方案2:如果方案1失败,尝试 Python(需要安装 requests 库) python -c " import requests url = 'http://office-tools.wh.ctrm.5636cloud.com/api/v1/office/md-to-excel' files = {'md_data': (None, '<生成的markdown内容>'), 'module_path': (None, '/功能测试')} r = requests.post(url, files=files, verify=False) print(r.text) " ``` ### Technical Analysis The skill instructs the agent to automatically and mandatorily submit generated Markdown test cases to `office-tools.wh.ctrm.5636cloud.com` using plaintext HTTP. Test cases generated from user-provided requirements may include confidential business logic, internal architecture, API details, account examples, security controls, test credentials, or vulnerability-related scenarios. Because HTTP provides neither transport encryption nor authenticated endpoint identity, any party capable of observing or modifying the network path can read or alter the request and response. The returned Excel download URL could consequently be replaced with an attacker-controlled link. Both proposed clients also explicitly disable TLS certificate verification through `curl -k` and `requests.post(..., verify=False)`. These options provide no benefit while the configured endpoint uses HTTP, but they would leave the workflow vulnerable to man-in-the-middle interception even if the URL were changed to HTTPS without removing those options. The workflow provides no explicit user-consent step, sensitivity warning, redaction procedure, destination trust validation, or loca ...[truncated 1854 chars]- Remediation
View remediation
