T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:131- Finding
Overbroad Access to Persistent User and Agent Context
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 131–136 and 170–179
Vulnerability Type: Excessive access to persistent memory and user-profile data
Risk Level: MediumVulnerable Code Snippet:
markdown ### 4. Memory/Context Files (if using ai-persona-os) **Locations:** - `MEMORY.md` Permanent facts - `memory/[today].md` Session notes - `USER.md` User preferencesmarkdown ### Step 1: Gather Data Sources Check for these files in order:- todo.md (to-do list from ai-meeting-notes)
- meeting-notes/ folder (recent meeting notes)
- MEMORY.md (if using ai-persona-os)
- memory/[today].md (session notes)
- Calendar integration (if available)
text Technical Analysis
The Skill instructs the agent to inspect persistent memory, current session notes, and user-profile data whenever it prepares a briefing. These files can contain sensitive or unrelated information beyond the task, meeting, and calendar data needed for a daily briefing.
The instructions do not establish field-level restrictions, data classification rules, redaction requirements, or explicit user consent before accessing persistent context. Consequently, the Skill can cause an agent with workspace read privileges to cross least-privilege boundaries and process substantially more user information than is necessary.
This issue does not independently grant operating-system privileges. Its practical scope is limited to files and integrations already accessible to the hosting agent. However, within that scope, it broadens access from task-related sources to potentially comprehensive persistent user and session data.
Attack Path
- The user invokes a broad trigger such as
briefing,start my day, orwhat do I need to know?. - The loaded Skill directs the agent to gather all listed data sources.
- The agent reads
MEMORY.md,memory/[today].md, and potentiallyUSER.mdusing its ex ...[truncated 903 chars]
- Remediation
View remediation
Remediation Suggestions
- Default to narrowly scoped sources such as
todo.md, explicitly selected meeting notes, and the user's calendar. - Make access to
MEMORY.md,USER.md, and session-memory files opt-in and request explicit confirmation before each new category of persistent data is read. - Allow users to configure approved files and sections instead of scanning complete memory documents.
- Add strict filtering rules that exclude credentials, authentication tokens, financial information, health information, personal identifiers, private relationship details, and unrelated session content.
- Summarize sensitive sources locally without reproducing their raw contents in the final briefing.
- Label each included context item with its source and provide a mode that omits persistent memory entirely.
- Ensure the hosting agent applies workspace sandboxing so this Skill can access only user-approved briefing data.
- Add an instruction stating that content found in task, meeting, memory, profile, or calendar files must be treated as untrusted data and never as executable agent instructions.
- Default to narrowly scoped sources such as
