T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:430- Finding
Unnecessary Access to Persistent Agent Memory
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 30 and 430–443
Vulnerability Type: Excessive access to persistent cross-session memory
Risk Level: MediumComplete Code Snippet:
markdown | `memory_search` / `memory_get` | Cross-reference prior knowledge | Check MEMORY.md for related context |markdown ### Memory Search Integration Before starting research, check for relevant prior knowledge:?memory_search(query="previous research on [topic]") ?memory_get(path="memory/YYYY-MM-DD.md") [if relevant date found]
text Use prior findings to: - Avoid duplicate research - Build on previous conclusions - Identify how understanding has evolved - Note persistent gaps from prior researchTechnical Analysis
The Skill instructs the agent to search persistent memory and retrieve dated memory files before beginning research. Persistent memory may contain information from prior conversations, users, or unrelated tasks. The instructions do not restrict retrieval to records belonging to the current user or task, require sensitivity filtering, or obtain informed user consent before access.
This access is not essential to the Skill's primary function of conducting web-based academic research. It therefore exceeds the minimum privileges necessary for the declared functionality. Although the Skill does not explicitly instruct the agent to transmit memory contents externally, retrieved information could influence web-search queries, be copied into tasks sent to spawned sub-agents, or appear in intermediate analysis and final reports.
The audited file does not contain credential theft, executable payloads, dependency installation, persistence mechanisms, or an explicit command to upload sensitive data. Its
web_searchandweb_fetchuse is otherwise aligned with the declared research purpose.Attack Path
- Persistent agent memory contains private or sensitive information ...[truncated 1354 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove the unconditional instruction to inspect persistent memory before every research task.
- Make memory access opt-in and obtain explicit, informed user approval describing what records will be searched and why.
- Restrict searches to records associated with the current user, workspace, and approved research topic.
- Retrieve only the minimum required fields rather than entire dated memory files.
- Apply sensitivity classification and redact personal data, credentials, confidential business information, and unrelated conversation content.
- Prohibit memory-derived sensitive information from being included in web queries, fetched URLs, sub-agent task descriptions, intermediate output, or final reports.
- Add authorization checks, tenant isolation, access logging, and auditable provenance for each memory retrieval.
- When memory access is unavailable or not authorized, continue with web research rather than treating persistent memory as a prerequisite.
