config/filter.d/postfix.conf in the postfix filter in Fail2ban before 0.8.11 allows remote attackers to trigger the blocking of an arbitrary IP address via a crafted e-mail address that matches an improperly designed regular expression.

- Use anchored failregex for filters to avoid possible     DoS. Manually picked up from the current status of 0.8     branch (as of 0.8.13-29-g09b2016) :

  - CVE-2013-7176: postfix.conf - anchored on the front,     expects 'postfix/smtpd' prefix in the log line

  - CVE-2013-7177: cyrus-imap.conf - anchored on the front,     and refactored to have a single failregex

  - couriersmtp.conf - anchored on both sides

  - exim.conf - front-anchored versions picked up from     exim.conf and exim-spam.conf

  - lighttpd-fastcgi.conf - front-anchored picked up from     suhosin.conf (copied from the Wheezy version)

  - Catch also failed logins via secured (imaps/pop3s) for     cyrus-imap. Regression was introduced while     strengthening failregex in 0.8.11 (bd175f) Debian bug     #755173

  - cyrus-imap: catch 'user not found' attempts

NOTE: Tenable Network Security has extracted the preceding description block directly from the DLA security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

Two vulnerabilities were discovered in Fail2ban, a solution to ban hosts that cause multiple authentication errors. When using Fail2ban to monitor Postfix or Cyrus IMAP logs, improper input validation in log parsing could enable a remote attacker to trigger an IP ban on arbitrary addresses, resulting in denial of service.

The fail2ban tool was updated to version 0.8.12 to fix various security issues and also brings bugfixes and features.

Security issues fixed: A remote unauthenticated attacker may cause arbitrary IP addresses to be blocked by Fail2ban causing legitimate users to be blocked from accessing services protected by Fail2ban.
CVE-2013-7177 (cyrus-imap) and CVE-2013-7176 (postfix)

  - Use new flushlogs syntax after logrotate

  - Update to version 0.8.12

  - Log rotation can now occur with the command 'flushlogs'     rather than reloading fail2ban or keeping the logtarget     settings consistent in jail.conf/local and     /etc/logrotate.d/fail2ban. (dep#697333, rh#891798).

  - Added ignorecommand option for allowing dynamic     determination as to ignore and IP or not.

  - Remove indentation of name and loglevel while logging to     SYSLOG to resolve syslog(-ng) parsing problems.
    (dep#730202). Log lines now also report '[PID]' after     the name portion too.

  - Epoch dates can now be enclosed within []

  - New actions: badips, firewallcmd-ipset, ufw,     blocklist_de

  - New filters: solid-pop3d, nsd, openwebmail, horde,     freeswitch, squid, ejabberd, openwebmail, groupoffice

  - Filter improvements :

  - apache-noscript now includes php cgi scripts

  - exim-spam filter to match spamassassin log entry for     option SAdevnull.

  - Added to sshd filter expression for 'Received disconnect     from : 3: Auth fail'

  - Improved ACL-handling for Asterisk

  - Added improper command pipelining to postfix filter.

  - General fixes :

  - Added lots of jail.conf entries for missing filters that     creaped in over the last year.

  - synchat changed to use push method which verifies     whether all data was send. This ensures that all data is     sent before closing the connection.

  - Fixed python 2.4 compatibility (as sub-second in date     patterns weren't 2.4 compatible)

  - Complain/email actions fixed to only include relevant     IPs to reporting

  - Filter fixes :

  - Added HTTP referrer bit of the apache access log to the     apache filters.

  - Apache 2.4 perfork regexes fixed

  - Kernel syslog expression can have leading spaces

  - allow for ',milliseconds' in the custom date format of     proftpd.log

  - recidive jail to block all protocols

  - smtps not a IANA standard so may be missing from     /etc/services. Due to (still) common use 465 has been     used as the explicit port number

  - Filter dovecot reordered session and TLS items in regex     with wider scope for session characters

  - Ugly Fixes (Potentially incompatible changes) :

  - Unfortunately at the end of last release when the action     firewall-cmd-direct-new was added it was too long and     had a broken action check. The action was renamed to     firewallcmd-new to fit within jail name name length.
    (gh#fail2ban/fail2ban#395).

  - Last release added mysqld-syslog-iptables as a jail     configuration. This jailname was too long and it has     been renamed to mysqld-syslog.

  - Fixed formating of github references in changelog

  - reformatted spec-file



  - Update to version 0.8.11

  - In light of CVE-2013-2178 that triggered our last     release we have put a significant effort into tightening     all of the regexs of our filters to avoid another     similar vulnerability. We haven't examined all of these     for a potential DoS scenario however it is possible that     another DoS vulnerability exists that is fixed by this     release. A large number of filters have been updated to     include more failure regexs supporting previously     unbanned failures and support newer application versions     too. We have test cases for most of these now however if     you have other examples that demonstrate that a filter     is insufficient we welcome your feedback. During the     tightening of the regexs to avoid DoS vulnerabilities     there is the possibility that we have inadvertently,     despite our best intentions, incorrectly allowed a     failure to continue.

    Addresses a possible DoS. Closes     gh#fail2ban/fail2ban#248, bnc#824710 within [Init].
    Closes gh#fail2ban/fail2ban#232

  - Updates to asterisk filter. Closes     gh#fail2ban/fail2ban#227, gh#fail2ban/fail2ban#230.

  - Updates to asterisk to include AUTH_UNKNOWN_DOMAIN.
    Closes gh#fail2ban/fail2ban#244. on Fedora. Closes     gh#fail2ban/fail2ban#112. Thanks to Camusensei for the     bug report. insight. Closes gh#fail2ban/fail2ban#103.

  - [f2156604] pyinotify -- monitor IN_MOVED_TO events.
    Closes gh#fail2ban/fail2ban#184. Thanks to Jon Foster     for report and troubleshooting. Orion Poplawski

  - [39667ff6] Avoid leaking file descriptors. Closes     gh#fail2ban/fail2ban#167. Closes     gh#fail2ban/fail2ban#147, gh#fail2ban/fail2ban#148.

  - [b6a68f51] Fix delaction on server side. Closes     gh#fail2ban/fail2ban#124. the fail2ban-client. Closes     gh#fail2ban/fail2ban#134. gh#fail2ban/fail2ban#70.
    Thanks to iGeorgeX for the idea.

  - [96eb8986] ' and ' should also be escaped in action tags     Closes gh#fail2ban/fail2ban#109 beilber for the idea.
    Closes gh#fail2ban/fail2ban#114. fail2ban is running.
    Closes gh#fail2ban/fail2ban#166.

  - [29d0df5] Add mysqld filter. Closes     gh#fail2ban/fail2ban#152.

  - [bba3fd8] Add Sogo filter. Closes     gh#fail2ban/fail2ban#117.

  - [be06b1b] Add action for iptables-ipsets. Closes     gh#fail2ban/fail2ban#102.

  - [f336d9f] Add filter for webmin. Closes     gh#fail2ban/fail2ban#99. consistently. Closes     gh#fail2ban/fail2ban#172.

  - [b36835f] Add get cinfo to fail2ban-client. Closes     gh#fail2ban/fail2ban#124. Closes     gh#fail2ban/fail2ban#142. Closes     gh#fail2ban/fail2ban#126. Bug report by Michael     Heuberger.

  - [3aeb1a9] Add jail.conf manual page. Closes     gh#fail2ban/fail2ban#143. banning due to misconfigured     DNS. Close gh#fail2ban/fail2ban#64

  - [0935566,5becaf8] Various python 2.4 and 2.5     compatibility fixes. Close gh#fail2ban/fail2ban#83 in     the console. Close gh#fail2ban/fail2ban#91 the log file     to take 'banip' or 'unbanip' in effect. Close     gh#fail2ban/fail2ban#81, gh#fail2ban/fail2ban#86

  - [f52ba99] downgraded 'already banned' from WARN to INFO     level. Closes gh#fail2ban/fail2ban#79 for this     gh#fail2ban/fail2ban#87) message stays non-unicode.
    Close gh#fail2ban/fail2ban#32 friend to developers stuck     with Windows (Closes gh#fail2ban/fail2ban#66) repeated     offenders. Close gh#fail2ban/fail2ban#19 Close     gh#fail2ban/fail2ban#47 (Closes: #669063)

The remote host is affected by the vulnerability described in GLSA-201406-03 (Fail2ban: Multiple vulnerabilities)

    Multiple vulnerabilities have been discovered in Fail2ban. Please review       the CVE identifiers referenced below for details.
  Impact :

    A remote attacker could send a crafted URL to a website which, when       parsed by Fail2ban, would deny a specific IP address. Also, errors in       regular expressions within certain filters can cause arbitrary IP       addresses to be banned. Furthermore, a local attacker could perform       symlink attacks to overwrite arbitrary files with the privileges of the       user running the application.
  Workaround :

    There is no known workaround at this time.

ID	Name	Product	Family	Severity
82169	Debian DLA-21-1 : fail2ban security update	Nessus	Debian Local Security Checks	medium
76583	Debian DSA-2979-1 : fail2ban - security update	Nessus	Debian Local Security Checks	medium
75283	openSUSE Security Update : fail2ban (openSUSE-SU-2014:0348-1)	Nessus	SuSE Local Security Checks	medium
74260	GLSA-201406-03 : Fail2ban: Multiple vulnerabilities	Nessus	Gentoo Local Security Checks	medium

Detections

Analytics

CVE-2013-7176

high

Tenable Plugins

medium

medium

medium

medium