PatchTheCVEfail2ban vulnerabilities
Recent CVEs affecting fail2ban products. 6 tracked.
fail2ban has 6 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 6. Most recent: 2021-07-16. Highest priority: CVE-2021-32749 (score 49/100).
- CVE-2021-32749 MEDIUM 6.1 UPGRADE MITIGATE fail2ban is a daemon to ban hosts that cause multiple authentication errors
- CVE-2013-7177 MEDIUM 5.0 UPGRADE config/filter.d/cyrus-imap.conf in the cyrus-imap filter in Fail2ban before 0.8.11 allows remote attackers to
- CVE-2013-7176 MEDIUM 5.0 UPGRADE config/filter.d/postfix.conf in the postfix filter in Fail2ban before 0.8.11 allows remote attackers to trigge
- CVE-2013-2178 MEDIUM 5.0 UPGRADE The apache-auth.conf, apache-nohome.conf, apache-noscript.conf, and apache-overflows.conf files in Fail2ban be
- CVE-2012-5642 HIGH 7.5 UPGRADE server/action.py in Fail2ban before 0.8.8 does not properly handle the content of the matches tag, which might
- CVE-2009-5023 MEDIUM 4.7 UPGRADE The (1) dshield.conf, (2) mail-buffered.conf, (3) mynetwatchman.conf, and (4) mynetwatchman.conf actions in ac
FAQ
How do I fix fail2ban vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is fail2ban being exploited right now?
None of the tracked fail2ban CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which fail2ban CVE should I patch first?
CVE-2021-32749 currently ranks highest (49/100): fail2ban is a daemon to ban hosts that cause multiple authentication errors.