T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:15- Finding
Excessive Access to Root-Owned OpenClaw Data and Production Service Logs
- Content
View full analysis
` - Logs for incident window: `journalctl -u --since ... --no-pager` - Workspace incident artifacts: `/root/.openclaw/workspace/docs/ops/`, `/root/.openclaw/workspace/memory/` ``` ### Technical Analysis The skill requires host-level service inspection and access to root-owned OpenClaw directories. In particular, `/root/.openclaw/workspace/memory/` may contain persistent agent state, user-provided content, operational context, credentials, tokens, or other sensitive information unrelated to the active incident. Although the document recommends a scoped service account, it does not define enforceable restrictions for: - Exact files that may be read from the memory directory. - Permitted service names for `systemctl` and `journalctl`. - Journal fields that may be collected. - Maximum log time windows. - Secret detection and redaction before data is processed or reported. - Separation between incident-specific evidence and unrelated production information. The declared access therefore creates a broad reconnaissance capability. A compromised agent session, malicious incident prompt, or unsafe integration could induce the skill to gather information outside t ...[truncated 1290 chars]- Remediation
View remediation
