T02 · Agent Memory Poisoning
- Location
SKILL.md:105- Finding
Untrusted Review Data Persisted in Agent Memory
- Content
View full analysis
/memory/slowmist-security-log.md` **Record format**: # [Date] Security Review Record ## [Review Type] — [Source Identifier] - Time: [ISO 8601] - Rating: [LOW/MEDIUM/HIGH/REJECT] - Key findings: [One-line summary] - Status: [Approved/Rejected/Pending] **Purpose**: - Avoid reviewing the same source repeatedly; review again when content changes - Track user decisions concerning particular ratings - Cite the previous review when the same source is encountered later **Rules**: - Append after each review; do not overwrite - For a new request involving the same source, check the record, cite it, and state how many days have passed - If the content has changed, perform a complete review ``` ### Technical Analysis The skill recommends writing review-derived data into Claude project memory and consulting that persistent record during later reviews. Fields such as the source identifier and key-findings summary can be derived from attacker-controlled URLs, documents, repository metadata, package names, or other external content. No instruction requires these fields to be escaped, length-limited, normalized, stored as strictly typed data, or separated from executable agent instructions. Because the destination is a Markdown file under the Agent's memory directory, crafted content could be persisted in a format that resembles headings, directives, or prompt instructions. If that memory file is subsequently loaded into an Agent context, the injected text could influence lat ...[truncated 2297 chars]- Remediation
View remediation
