Executive brief
MISP, an open-source threat intelligence platform, can record incorrect access log data when HTTP requests terminate with an exception. The bug causes the system to log metrics like request duration, database query count, and memory usage twice—once correctly and once incorrectly—with the second corrupted entry overwriting the first. This leads to inaccurate audit trails and performance metrics, potentially masking security issues or creating false incident reports.
Technical details
This is a logic flaw in exception handling within MISP's CakeErrorController. When an exception occurs, CakeErrorController extends AppController and re-executes the application startup path, causing the __accessMonitor() hook to call AccessLog::logRequest() twice for a single HTTP request. The second call occurs during error-controller execution and overwrites the database row created by the first pass with incorrect metrics (duration, SQL counts, memory). The bug went undetected because the model instance retained the INSERT ID from the first save, causing the second operation to issue an UPDATE rather than create an obvious duplicate row. A fix was committed in 2026 that prevents the error controller from updating the access-log entry.
Affected products
- MISP MISP ≤2.5.45
Timeline
- 2026-09-15: disclosed
- 2026-09-15: patched: Commit 0dae5c0 addresses the double-logging issue