T09 · Insecure Skill Coding Practices
- Location
scripts/gateway-watchdog.sh:132- Finding
Unredacted Gateway Log Lines May Be Transmitted Through External Notification Channels
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a coherent Gateway log monitor, but it can put raw log snippets into scheduled notifications sent to the last messaging channel.
Review this before installing if your Gateway logs may contain API keys, authorization headers, private messages, user IDs, or channel addresses. Use an explicit administrator notification channel instead of `--channel last`, and prefer aggregate-only alerts or add redaction before using scheduled notifications.
scripts/gateway-watchdog.sh:132Unredacted Gateway Log Lines May Be Transmitted Through External Notification Channels
Referenced artifact was not completely inspected
bash scripts/gateway-watchdog.sh check # silent unless errors exceed threshold
Referenced artifact was not completely inspected
bash scripts/gateway-watchdog.sh check # silent unless errors exceed threshold
Referenced artifact was not completely inspected
bash scripts/gateway-watchdog.sh check # silent unless errors exceed threshold
Referenced artifact was not completely inspected
bash scripts/gateway-watchdog.sh check # silent unless errors exceed threshold
Without declared permissions the skill's intent is opaque and cannot be validated.
The comment at L005 describes the skill as performing "read-only log analysis," but the implementation creates directories and writes both a JSON state file and a history log in save_state(). That is an active contradiction between the documented intent and the actual side effects, not merely omitted detail.
The results section labels the primary alert example as 'Chinese locale' and presents English only as an equivalent, which suggests a default language behavior. The file does not state that users can choose their preferred output language or that Chinese output is limited to a justified region-specific deployment.
The manifest focuses on detecting abnormal error rates in logs and integrating checks into heartbeat monitoring. While log analysis is the core behavior, this code additionally stores historical results and prior counts on disk, expanding the behavior beyond pure monitoring into local stateful persistence that is not mentioned in the manifest description.
No suspicious patterns detected.