T02 · Agent Memory Poisoning
- Location
run.sh:11- Finding
Untrusted Web Content Is Persisted in Agent Memory
- Content
View full analysis
"$SUMMARY_FILE" echo "" >> "$SUMMARY_FILE" echo "## Topic Overview" >> "$SUMMARY_FILE" echo "$TOPIC_OVERVIEW" >> "$SUMMARY_FILE" echo "" >> "$SUMMARY_FILE" echo "## Key Events" >> "$SUMMARY_FILE" echo "$KEY_EVENTS" >> "$SUMMARY_FILE" echo "" >> "$SUMMARY_FILE" echo "## Potential Impact" >> "$SUMMARY_FILE" echo "$IMPACT" >> "$SUMMARY_FILE" echo "" >> "$SUMMARY_FILE" echo "## Information Sources" >> "$SUMMARY_FILE" echo "$SOURCES" >> "$SUMMARY_FILE" ``` The corresponding persistence behavior is documented in `SKILL.md:48`: ```markdown - Caches summary to `memory/YYYY-MM-DD-ai-summary.md` for future reference ``` ### Technical Analysis The result titles and URLs returned by `web_search` are externally controlled or attacker-influenceable data. The script extracts these fields and writes them directly into a file under the Agent's `memory/` directory without content validation, provenance enforcement, length restrictions, or explicit untrusted-data boundaries. Using `jq` provides JSON encoding and reduces the likelihood of direct shell interpretation, but it does not neutralize natu ...[truncated 1766 chars]- Remediation
View remediation
