T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:64- Finding
Unnecessary Cross-Skill Access to Persistent User Memory
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 64–83
Vulnerability Type: Cross-Skill persistent-memory access beyond the minimum required scope
Risk Level: MediumEvidence
The following is an English translation of the relevant Skill instructions:
markdown 1. `MEMORY.md` in this directory — use first (stores the user's divination preferences) 2. `fortune-hub/MEMORY.md` in the same repository, if present — supplement shared basic fields If usable data exists, use it directly without asking again. **Write**: Write to this directory's `MEMORY.md` only when the user explicitly states a preference: # User Preferences ## Divination Preferences - Default divination method: time / number / text - Interpretation style: concise / detailed **Update**: Update the corresponding field when the user requests a preference change.Technical Analysis
The Skill instructs the agent to inspect both its own persistent memory and the memory owned by another Skill. Its deterministic calculation only requires user-provided numbers, text, or the current time, so reading
fortune-hub/MEMORY.mdis not necessary for the core task.The phrase “shared basic fields” does not define a field allowlist, sensitivity restrictions, a consent boundary, or a purpose limitation. The instruction to use available data “without asking again” may consequently cause information collected in another context to be accessed and incorporated without the user's informed consent.
The local write behavior is narrower because it is limited to explicitly expressed preferences. The reviewed instructions do not direct the agent to write attacker-controlled rules, executable content, or hidden instructions into memory. Therefore, the issue is best classified as a least-privilege violation rather than agent memory poisoning.
Attack Path
- A user invokes the Meihua Yishu Skill.
- The agent follows
SKILL.mdand che ...[truncated 1334 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove the automatic read of
fortune-hub/MEMORY.mdunless cross-Skill state is essential to the requested operation. - If cross-Skill access must remain, define a strict allowlist limited to:
- Default divination method.
- Preferred interpretation detail level.
- Require explicit user consent before every cross-Skill memory read.
- Inform the user which file and fields will be accessed before reading them.
- Reject unrelated, sensitive, instructional, or executable content found in shared memory.
- Treat memory values strictly as untrusted data and never as agent instructions.
- Preserve the existing explicit-consent requirement for writes, and clearly disclose the retention scope and deletion procedure.
- Apply separate namespaces and access controls so each Skill can access only its own persistent state by default.
- Remove the automatic read of
