T09 · Insecure Skill Coding Practices
- Location
scripts/escalate.sh:10- Finding
Bearer Token and Escalation Data Exposed Through Configurable Plaintext HTTP Destination
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a disclosed escalation helper, but it forwards potentially sensitive troubleshooting context and a bearer token through an under-scoped webhook path to a fixed Telegram destination.
Install only if this skill is meant for your organization’s escalation workflow. Configure and verify the gateway, token, supervisor, channel, and recipient before use; keep the gateway on trusted loopback or require TLS for any non-local destination; and do not include passwords, API keys, tokens, personal data, or raw customer logs in escalation arguments.
scripts/escalate.sh:10Bearer Token and Escalation Data Exposed Through Configurable Plaintext HTTP Destination
scripts/escalate.sh:13JSON Injection Through Unescaped Environment-Controlled Routing Fields
scripts/escalate.sh:13Sensitive Escalation Context Is Automatically Delivered to a Fixed Telegram Recipient
The skill instructs the agent to execute a shell script but does not declare any explicit tool scope or permissions. This increases the chance of unintended shell access or overbroad execution in environments that rely on metadata-based permission gating, making the skill harder to audit and safely sandbox.
The skill says the supervisor receives the complete context and that the response is delivered over Telegram, but it gives no warning or filtering guidance for secrets, tokens, personal data, or client-sensitive material. In an escalation workflow, operators are likely to paste raw errors, credentials, email contents, or customer data, creating a real risk of data leakage to external systems and chat channels.
The script’s natural-language comments, usage strings, and user-facing error text are exclusively in French, such as the usage/help and missing-token message. This imposes a specific language/locale on users without offering a choice or documenting a justified region-specific constraint, matching the language-policy violation criteria.
The script transmits user-supplied problem details and attempt history to an external webhook endpoint, which can expose potentially sensitive operational data. The risk is increased because the request uses plain HTTP rather than HTTPS, so the bearer token and message contents could be intercepted or modified if the connection is not strictly local and trusted.
JSON_MESSAGE=$(printf '%s' "$MESSAGE" | python3 -c 'import json,sys; print(json.dumps(sys.stdin.read()))')
# Appel webhook
RESPONSE=$(curl -s -w "\n%{http_code}" -X POST \
"http://${GATEWAY_HOST}:${GATEWAY_PORT}/hooks/agent" \
-H "Authorization: Bearer ${HOOKS_TOKEN}" \
-H "Content-Type: application/json" \
The manifest description and operational instructions are entirely in French, which effectively forces a specific language for users of the skill. The file does not indicate that French is optional, user-selected, or required for a documented region-specific reason.