T09 · Insecure Skill Coding Practices
- Location
references/context-propagation.md:169- Finding
Unrestricted Downstream URL Enables Server-Side Request Forgery
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This is a documentation-only Go middleware skill with some security-sensitive examples users should adapt carefully, but it does not contain hidden execution, persistence, or deceptive behavior.
Safe to install as a Go middleware reference skill. Before copying the examples into production, review outbound request destinations, avoid forwarding request metadata to untrusted services, and sanitize logs so tokens, credentials, personal data, internal paths, and raw panic details are not broadly retained or exported.
references/context-propagation.md:169Unrestricted Downstream URL Enables Server-Side Request Forgery
references/error-handling-middleware.md:141Full Internal Error Messages May Expose Sensitive Data Through Logs
references/error-handling-middleware.md:174Panic Values and Stack Traces May Leak Sensitive Runtime Information
This markdown skill describes logging middleware and records request path, status, duration, and request IDs, while earlier sections also discuss propagating authenticated users and tenant IDs in context. The document does not include a user warning or caution about avoiding sensitive data, which is relevant for markdown files that describe behaviors affecting privacy.
This markdown file includes an example that forwards a request-derived identifier in an outbound HTTP header to downstream services. Under the markdown-file criteria for missing user warnings, behavior that affects privacy or data sharing should be disclosed, but this section presents the propagation as a best practice without any warning about exposing identifiers across service boundaries.
No suspicious patterns detected.