T09 · Insecure Skill Coding Practices
- Location
ssssss.json:1- Finding
Sensitive OpenClaw Runtime Trace Included in the Skill Package
- Content
View full analysis
Vulnerability Details
File Location:
ssssss.json:1
Vulnerability Type: Sensitive runtime information and request-header disclosure
Risk Level: MediumVulnerable Code Snippet:
json { "id": 1, "timestamp": 1773679810.3415484, "time_str": "2026-03-16 16:50:10", "session": "72766bada31e_20260316_165010", "method": "POST", "path": "/v1/chat/completions", "streaming": true, "request_headers": { "host": "127.0.0.1:5213", "connection": "keep-alive", "Accept": "application/json", "User-Agent": "OpenAI/JS 6.26.0", "X-Stainless-Retry-Count": "0", "X-Stainless-Lang": "js", "X-Stainless-Package-Version": "6.26.0", "X-Stainless-OS": "Linux", "X-Stainless-Arch": "x64", "X-Stainless-Runtime": "node", "X-Stainless-Runtime-Version": "v22.22.1", "authorization": "Bearer idonthaveakey", "content-type": "application/json", "accept-language": "*", "sec-fetch-mode": "cors", "accept-encoding": "gzip, deflate", "content-length": "296734" }, "request_body": { "model": "GLM-4.7V-355B-SFT-20260315", "messages": [ { "role": "system", "content": "You are a personal assistant running inside OpenClaw.\n## Tooling\nTool availability (filtered by policy):\nTool names are case-sensitive. Call tools exactly as listed.\n- read: Read file contents\n- write: Create or overwrite files\n- edit: Make precise edits to files\n- exec: Run shell commands..." } ] } }The file is a single-line JSON record approximately 995 KB in size. The displayed snippet contains the relevant request metadata and beginning of the embedded system prompt.
Technical Analysis
The package includes a raw HTTP request trace that is unrelated to the grounding Skill's required runtime assets. The record exposes:
- An authorization-header field.
- An internal loopback servic ...[truncated 2708 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove
ssssss.jsonfrom the distributable Skill package and from repository history where feasible. - Treat the trace as potentially sensitive and perform a controlled review for user content, identifiers, tokens, cookies, API keys, and embedded media.
- Revoke or rotate any genuine credentials identified during that review. The placeholder observed during this audit does not itself require rotation unless it maps to an active authentication configuration.
- Add generated traces, HTTP captures, debug dumps, and session recordings to
.gitignoreand packaging exclusion rules. - Add release-time secret scanning and content checks that reject authorization headers, cookies, private keys, session transcripts, system prompts, and oversized undocumented assets.
- If a fixture is necessary for testing, replace it with a minimal synthetic record containing fictional metadata and explicitly redacted headers.
- Configure logging middleware to omit or redact
Authorization, cookies, user identifiers, message bodies, images, and other private request fields before writing logs. - Restrict access to operational traces and apply a documented retention and deletion policy.
- Remove
