T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:110- Finding
Overbroad Persistent Memory and Session Transcript Access
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 110-140
Vulnerability Type: Excessive access to persistent agent memory and historical session data
Risk Level: MediumThe Skill recommends enabling memory flushing and searches across both persistent memory and historical session transcripts:
markdown ## Recommended Config Enable memory flush before compaction and session memory search so your agent remembers context across sessions: ```json { "agents": { "defaults": { "compaction": { "memoryFlush": { "enabled": true } }, "memorySearch": { "enabled": true, "sources": ["memory", "sessions"], "experimental": { "sessionMemory": true } } } } }What this does:
- memoryFlush — Agent gets a chance to save important context before compaction wipes the conversation
- memorySearch + sessionMemory — Agent can search past session transcripts, not just MEMORY.md files
Apply with:
openclaw config patch <json>text ### Technical Analysis The recommended configuration expands the agent's data-access and retention scope beyond the Skill's primary purpose of supplying behavioral best practices. Enabling `memoryFlush` allows context to be retained across compaction boundaries, while configuring `memorySearch` with both `"memory"` and `"sessions"` permits retrieval from historical session transcripts. Historical sessions can contain private prompts, credentials, access tokens, proprietary information, or data unrelated to the current task. Applying this configuration at the default agent level may grant multiple future sessions access to a broader body of information than they require, violating least-privilege and data-minimization principles. The project does not automatically apply the configuration, execute code, or transmit retrieved information ext ...[truncated 1351 chars]- Remediation
View remediation
Remediation Suggestions
- Remove the persistent-memory configuration from the default installation guidance unless it is essential to the Skill's stated function.
- Make memory and session-history access explicitly opt-in and require informed user approval before applying configuration changes.
- Scope memory search to a dedicated workspace or task-specific store rather than all default-agent sessions.
- Disable historical session search by default and enable only the minimum source required for a specific task.
- Document retention periods, deletion procedures, access boundaries, and the types of information that may be indexed.
- Add filtering to prevent credentials, tokens, private keys, and other secrets from being written to persistent memory.
- Require authorization checks before one session can search data originating from another session or user.
- Provide a rollback command and instructions for deleting previously retained or indexed session data.
- Warn users not to enable the feature in shared or multi-user environments without tenant-level isolation and encryption.
- If memory access remains recommended, use a narrowly scoped example configuration rather than modifying global agent defaults.
