T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:88- Finding
World-Readable Permissions Applied to Agent Memory Files
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 88-89
Vulnerability Type: Excessive file permissions exposing potentially sensitive memory
Risk Level: MediumVulnerable Code:
bash chmod 644 ~/.openclaw/workspace/memory/*.md chmod 644 ~/.openclaw/workspace/MEMORY.mdTechnical Analysis
The documented repair procedure assigns mode
644to the Agent's memory files. This gives the owner read/write access but grants read access to every other local account.Agent memory may contain conversation history, personal information, operational context, internal instructions, or other sensitive data. World-readable permissions violate least-privilege principles and are unnecessary when the intended repair is merely to restore access for the Agent's owning account.
Attack Path
- A user invokes the Skill to troubleshoot a memory-access problem.
- The Agent follows the documented commands and changes the memory files to mode
644. - Another account with local access to the host locates the OpenClaw workspace.
- That account reads
MEMORY.mdor files undermemory/using the newly granted group/other read permissions. - Sensitive Agent state or user information is disclosed without authorization.
Impact Assessment
Exploitation requires access through another local account or process operating under a different identity. It does not grant write access or root privileges, but it can expose all content stored in the affected memory files. The disclosure scope includes every matching Markdown file in the memory directory and the primary
MEMORY.mdfile.- Remediation
View remediation
Remediation Suggestions
- Use owner-only permissions, such as
chmod 600, rather than644. - Verify file ownership with
statorls -lbefore changing permissions. - Restore the expected owner with a narrowly scoped
chownoperation when ownership is the actual problem. - Avoid wildcard permission changes until the affected files have been enumerated and reviewed.
- Document that memory files may contain sensitive data and must not be readable by unrelated local users.
- Add a post-remediation check confirming that files are owned by the OpenClaw account and are not accessible to group or other users.
- Use owner-only permissions, such as
