T02 · Agent Memory Poisoning
- Location
src/memory-sync.js:7- Finding
Untrusted Conversation Content Can Poison Persistent Agent Memory
- Content
View full analysis
10 && content.length < 300) { decisions.push(content); } } } return [...new Set(decisions)]; } function syncToMemory(date, decisions) { if (!decisions.length) return 0; const memoryFile = getMemoryFile(); if (!fs.existsSync(memoryFile)) { fs.writeFileSync(memoryFile, '# MEMORY.md - Long-Term Memory\n\n_Curated memories._\n\n'); } let content; try { content = fs.readFileSync(memoryFile, 'utf-8'); } catch { content = '# MEMORY.md - Long-Term Memory\n\n'; } const header = '## Auto-Captured'; const entries = decisions.map(d => `- **[${date}]** ${d}`).join('\n'); if (content.includes(header)) { const idx = content.indexOf(header); content = content.slice(0, idx + header.length) + '\n' + entries + '\n' + content.slice(idx + header.length); } else { content += `\n${header}\n\n${entries}\n`; } fs.writeFileSync(memoryFile, content); return decisions.length; } ``` The explicit synchronization command supplies raw message content directly to these functions: ```javascript case 'sync': { // Sync decisions from recent uncompacted messages const messages = require('../src/messages').getUncompactedMessages(sess ...[truncated 2666 chars]- Remediation
View remediation
