other
- Location
SKILL.md:102- Finding
Overly Broad Host and Security-Sensitive Reconnaissance
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 102-129
Vulnerability Type: Excessive Environment Reconnaissance
Risk Level: MediumVulnerable Code Snippet
markdown ### 7) Credentials & Secret Storage 1. Check for plaintext secrets locations: - `~/.openclaw/` directories - `.env` files, token dumps, backups 2. Identify world‑readable or group‑readable secret files: - `find ~/.openclaw -type f -perm -o+r -maxdepth 4 2>/dev/null | head -n 50` 3. Report only **paths**, never contents. ### 8) File Permissions & Privilege Escalation Risks 1. Check for risky permissions on key dirs: - `ls -ld ~/.openclaw` - `ls -l ~/.openclaw | head -n 50` 2. Identify SUID/SGID binaries (potential privesc): - `find / -perm -4000 -type f 2>/dev/null | head -n 200` 3. Flag if OpenClaw runs as root or with unnecessary sudo. ### 9) Process & Persistence Indicators 1. Check for unexpected cron jobs: - `crontab -l` - `ls -la /etc/cron.* 2>/dev/null` 2. Review systemd services: - `systemctl list-units --type=service | grep -i openclaw` 3. Flag unknown services related to OpenClaw or skills. ### 10) Logs & Audit Trails 1. Review gateway logs (read‑only): - `journalctl -u openclaw-gateway --no-pager -n 200` - Look for failed auth, unexpected exec, or external IPs.Technical Analysis
The skill declares itself a read-only OpenClaw security auditor, but its workflow directs the agent to perform broad inspection of security-sensitive host state. In particular, the filesystem-root SUID scan is not restricted to OpenClaw, while cron enumeration and journal access can disclose unrelated operational details.
These commands do not directly modify the host or obtain elevated privileges. They execute with the permissions of the invoking account. Nevertheless, they can reveal:
- Locations and permissions of credential-related files.
...[truncated 2220 chars]
- Remediation
View remediation
Remediation Suggestions
- Make broad host inspection opt-in and require explicit user approval before examining cron configuration, system-wide privileged binaries, or logs.
- Scope filesystem checks to documented OpenClaw directories rather than using
find /. - Replace the system-wide SUID scan with an explanation that it is an optional host-hardening check unrelated to the default OpenClaw audit.
- Restrict persistence checks to OpenClaw-specific units and entries where possible.
- Use journal filters that minimize collected fields and redact IP addresses, usernames, tokens, command arguments, and other sensitive values.
- State that the audit must run as an unprivileged service account and must not request
sudosolely to increase inspection coverage. - Collect only summarized findings rather than raw command output, and define secure deletion or retention requirements for audit artifacts.
- Separate the workflow into a default OpenClaw-only audit and an explicitly authorized extended host-security audit.
