other
- Location
SKILL.md:15- Finding
Agent Memory Metadata Reconnaissance
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 15-24
Vulnerability Type:other: Agent memory metadata reconnaissance
Risk Level: MediumVulnerable Code Snippet:
markdown 3. Shows recent memory notes (last 3 files). ## Basic steps ```bash cd <workspace> echo "== top level ==" && ls -la echo "== git ==" && git status -s 2>/dev/null || echo "no git repo" echo "== recent memory ==" && ls -t memory/*.md 2>/dev/null | head -3Technical Analysis
The Skill instructs the agent to enumerate the three most recently modified Markdown files in the workspace's
memory/directory. Although it does not read file contents, it discloses filenames and their recency ordering through standard output.Memory filenames can contain sensitive metadata such as customer names, project identifiers, incident references, task descriptions, or user information. Enumerating this data is not required to perform the Skill's Git-status and deliverable-health checks. The behavior therefore introduces unnecessary access to agent memory metadata and expands the information exposed to the caller.
Attack Path
- An agent loads and follows the WS QuickStatus instructions.
- The agent changes into a workspace containing Markdown files under
memory/. - The command sorts those files by modification time and selects the latest three.
- Their paths or filenames are printed to standard output.
- A caller able to view the Skill output learns sensitive memory-note metadata and can use it to identify potentially valuable files for subsequent targeted access.
This path exposes metadata only; the audited command does not read memory-file contents or transmit results to an external service.
Impact Assessment
The issue can disclose the names and relative recency of up to three agent memory files available to the current process. It does not grant additional operati ...[truncated 294 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove memory-file enumeration from the default workspace-health workflow.
- If memory inspection is genuinely required, make it an explicit opt-in operation and obtain user approval before accessing the directory.
- Return only a count, such as the number of recent notes, rather than exposing filenames.
- If identifiers must be displayed, redact or hash filenames and avoid exposing modification-order information.
- Restrict the check to a dedicated, non-sensitive status index instead of scanning the agent's general memory directory.
- Clearly document the information that will be accessed and displayed before executing the check.
