engramx
Affected
- introduced
0, fixed2.0.2(semver)
Fixed versions
2.0.2
Fix
- Fixed version
2.0.2npm install [email protected]
Advisory
Also known as: None
engram: HTTP server CORS wildcard + auth-off-by-default enables CSRF graph exfiltration and persistent indirect prompt injection
Summary
The local HTTP server started by engram server (binding 127.0.0.1:7337 by default) was exposed to any browser origin with no authentication unless ENGRAM_API_TOKEN was explicitly set. Combined with Access-Control-Allow-Origin: * on every response and a body parser that did not require Content-Type: application/json, this allowed a malicious web page the developer visited to:
GET /query and GET /stats (function names, file layout, recorded decisions/mistakes).POST /learn, which wrote mistake/decision nodes that were later surfaced as system-reminders to the user's AI coding agent on every future session and file edit.Severity: High — confidentiality + persistent indirect prompt injection against the user's coding agent.
Affected versions
engramx >= 1.0.0, < 2.0.2 — any version that shipped the HTTP server.
Patched in
Workarounds (if you cannot upgrade)
engram server or engram ui.ENGRAM_API_TOKEN to a long random value and terminate the server before browsing the web.Remediation (applied in 2.0.2)
~/.engram/http-server.token (0600).ENGRAM_ALLOWED_ORIGINS.Content-Type: application/json enforced on mutations — blocks the text/plain CSRF vector./ui?token= bootstrap with Sec-Fetch-Site gate — prevents cross-origin oracle probing.Credit
Discovered and responsibly disclosed by @gabiudrescu in engram issue #7.
High Basis: The source's own band: HIGH
0, fixed 2.0.2 (semver)2.0.2
2.0.2npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0