T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:11- Finding
Unscoped Access to Persistent Agent Memory
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 11–13
Vulnerability Type:T05: Unauthorized Access and Privilege Escalation
Risk Level: Mediummarkdown - Start with `memory_search` for saved tracker paths, report paths, labels, reminder style, and owner/escalation conventions. - If `memory_search` returns a likely hit, follow with `memory_get` on the exact path or cited section before relying on the value. - If `memory_search` is empty for the family token, do one targeted `memory_get` on `memory/family-preferences/financeops-accrual-rollforward.md` before assuming there is nothing useful to reuse.Technical Analysis
The Skill requires persistent-memory discovery at the start of accrual-rollforward tasks and directs the Agent to retrieve matching entries. If the search produces no result, it mandates access to a predetermined shared memory path.
These instructions do not require per-task user authorization, verify that the retrieved memory belongs to the current workspace or user, or restrict retrieval to data necessary for the active task. This violates least-privilege principles because persistent memory may contain tracker and report paths, ownership information, escalation conventions, or preferences originating from other tasks or contexts.
The Skill does not instruct the Agent to transmit retrieved information externally, modify memory, or execute content obtained from memory. Consequently, the confirmed exposure is limited to unauthorized retrieval and use within the Agent’s active context.
Attack Path
- A user or workflow triggers the accrual-rollforward Skill.
- The Skill instructs the Agent to invoke
memory_searchfor stored operational metadata. - The Agent retrieves a search result using
memory_get; if no result exists, it accesses the fixed pathmemory/family-preferences/financeops-accrual-rollforward.md. - Persistent information outside the explicitly supplied ...[truncated 892 chars]
- Remediation
View remediation
Remediation Suggestions
- Require explicit user authorization before accessing persistent memory.
- Scope memory searches to the current user, workspace, engagement, and accrual-rollforward identifier.
- Remove the unconditional fallback to
memory/family-preferences/financeops-accrual-rollforward.md, or verify that the path is authorized for the current task before reading it. - Retrieve only the specific fields required for the active reconciliation rather than broad tracker, ownership, and escalation metadata.
- Treat retrieved memory as untrusted contextual data and never as higher-priority instructions.
- Validate the source, freshness, ownership, and task relevance of every retrieved value before using it.
- Avoid exposing retrieved memory in reports or tool outputs unless the user explicitly requests it and is authorized to receive it.
- Record memory-access decisions in an audit trail without logging the sensitive contents themselves.
