CyberRota Analysis
AI-GeneratedAffected versions of MISP utilize Redis for managing authentication failure logs, but a flaw in the logging logic prevents the system from recording failed attempts when Redis is unavailable. This results in a lack of visibility into potential unauthorized access attempts during Redis outages, which could hinder incident response efforts. Organizations using MISP versions 2.5.45 or earlier should prioritize addressing this vulnerability to ensure continuous monitoring of authentication activities.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
Affected versions of MISP use Redis to throttle repeated authentication-failure log entries. The intent is to avoid excessive duplicate logs while still recording failed authentication activity. However, User->setupRedis() returns false when Redis cannot be reached. The vulnerable _shouldLog() logic only returned true when a Redis instance existed and no throttle key was present. Therefore, when Redis was unavailable, the function did not allow the log write at all, effectively silencing authentication-failure logging for the duration of the outage. Version affected: ≤2.5.45