T09 · Insecure Skill Coding Practices
- Location
scripts/inspect_remote_access.sh:35- Finding
Sensitive OpenClaw Configuration and Pairing Data Are Printed Without Redaction
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill does what it says, but it handles gateway credentials and diagnostic data too openly for a remote-access setup tool.
Review before installing. Use this only on a host where you are comfortable changing OpenClaw and Tailscale state, keep an out-of-band admin path available, avoid sharing inspector output unless you have redacted tokens and pairing data, and check permissions on openclaw.json and any .bak files after running it.
scripts/inspect_remote_access.sh:35Sensitive OpenClaw Configuration and Pairing Data Are Printed Without Redaction
scripts/apply_gateway_config.py:12Gateway Authentication Token Is Exposed Through Process Arguments
scripts/apply_gateway_config.py:46Credential-Bearing Configuration File Is Created Without Enforcing Restrictive Permissions
The skill claims to provide a full remote-access repair workflow, but the implemented behavior appears narrower and may not actually perform several promised safety-critical checks and repairs. That mismatch can cause operators or autonomous agents to trust the skill to validate access, repair DNS/origin issues, or safely modify OpenClaw config when it may only partially reconfigure Tailscale Serve, leading to insecure exposure, incomplete remediation, or service disruption.
This markdown file documents actions that change openclaw.json, restart openclaw-gateway, and recreate Tailscale Serve, which can affect connectivity and system availability. Although the steps are operationally clear, the README does not provide a direct user warning that these actions modify live system/network configuration and may temporarily disrupt access.
The skill performs sensitive actions involving file reads/writes, network access, and service reconfiguration, but it does not declare any explicit tool scope or allowed-tools boundary. In an agent environment, that increases the chance the runtime grants broader capabilities than intended, making unintended system changes or data exposure more likely.
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
Then:
sudo systemctl restart systemd-resolved
journalctl -u tailscaled -n 50 --no-pager
The script persists the gateway token directly into the JSON config file on disk and also creates timestamped backups of that file, multiplying the number of copies of the secret. If the config or backup files are readable by other local users, included in support bundles, committed to source control, or exfiltrated from disk, the token can be reused to access the gateway.
The script prints the contents of the OpenClaw config file and pending pairing requests directly to stdout, which can expose sensitive information such as device metadata, service configuration, internal URLs, tokens, or pairing state. In a remote-access troubleshooting skill, this output is likely to be shared with an operator, logged in terminal history, or copied into support channels, increasing the chance of unintended disclosure.
The file prominently presents a locale-specific alternate document link labeled only in Chinese, which can create a language/locale bias in the skill's natural-language presentation. The README does not explicitly offer language choice or explain locale targeting, so this may conflict with the policy against forcing a specific language without opt-in.
No suspicious patterns detected.