T09 · Insecure Skill Coding Practices
- Location
scripts/redmine.py:16- Finding
Redmine API key may be exposed through insecure transport or cross-origin redirects
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This Redmine skill appears purpose-built, but it needs review because it can use an API key to read and change project data without tight request safeguards.
Install only if you trust the Redmine server URL and can use a least-privilege API key. Configure an HTTPS Redmine URL, avoid broad production credentials, and manually review any create or update action before letting the agent run it.
scripts/redmine.py:16Redmine API key may be exposed through insecure transport or cross-origin redirects
Credentials or environment variables flow to a network sink. This is a high-confidence indicator of credential exfiltration.
req = Request(full_url, data=body, headers=headers, method=method)
try:
with urlopen(req) as resp:
if resp.status == 204:
return None
return json.loads(resp.read().decode())
The skill uses environment-provided credentials and makes network requests to an external Redmine instance, but it does not declare an explicit tool scope such as allowed-tools or permissions. That creates an authorization ambiguity where the skill may be invoked with broader capabilities than users expect, increasing the chance of unintended credential use or outbound access.
The trigger description includes broad terms like project, issue, 任务, and 工单, which are common in many unrelated conversations. This can cause the skill to activate unintentionally and perform sensitive Redmine lookups or state-changing actions in contexts where the user did not clearly request Redmine access.
The documentation instructs users to configure an API key and demonstrates create/update operations, but it does not warn that these credentials are sensitive or that the skill can modify remote project data. In practice, this increases the risk of accidental disclosure of the API key and unintended changes to production issue-tracking systems.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl -s -X POST -H "X-Redmine-API-Key: $REDMINE_API_KEY" \
-H "Content-Type: application/json" \
"$REDMINE_URL/issues.json" \
-d '{
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl -s -X PUT -H "X-Redmine-API-Key: $REDMINE_API_KEY" \
-H "Content-Type: application/json" \
"$REDMINE_URL/issues/ISSUE_ID.json" \
-d '{
Natural-language strings such as the module description, help text, and error messages are consistently presented only in Chinese. This forces a specific language experience without offering opt-in, fallback, or documenting that the tool is intentionally limited to a Chinese-speaking context.
This code performs state-changing API calls to create and update issues, which can alter shared project data. Although the commands are named for their purpose, the file provides no confirmation prompt or explicit caution that these actions will modify remote records before execution.
The entire skill reference content is written in Chinese and does not indicate that other languages are supported or that Chinese is optional. Under the stated policy, forcing a specific language without user opt-in is a natural-language policy violation.