mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-08 20:42:43 +00:00
Marc-André Bombeck
e31c66e959
Three leaks of the same class - data leaving the process unprotected. addMeta and addExternalCall wrote their values verbatim while setError and setHttp scrubbed, so the builder's redaction contract held for two entry points out of four. The finished event is serialised whole to stdout and the log store, which made meta a trusted sink by accident: a Telegram request timeout put the bot token there, and the AI provider chain fed upstream error bodies through it. Both now scrub, at any depth. Scrubbing cannot help with the second half. A gateway that echoes the request it rejected echoes the prompt, and on that path the prompt carries the health snapshot; no pattern separates that from any other text. Upstream bodies are therefore classified rather than quoted - the diagnostic question is which rejection occurred and whether it repeats, which a classification answers without the content. The idempotency replay cache stored response bodies unencrypted. The create paths echo their own decrypted payload, so cycle notes, mood text and allergy reactions sat in cleartext for 24 hours in a column that lands in every backup; the existing guard missed it because it matches secret shapes and health data is not secret-shaped. Bodies are encrypted now, and when encryption is unavailable the response is not cached at all rather than written in the clear. chore(release): v1.30.18
