CVE-2012-5642
Fail2ban vulnerability
server/action.py in Fail2ban before 0.8.8 does not properly handle the content of the matches tag, which might allow remote attackers to trigger unsafe behavior in a custom action file via unspecified symbols in this content.
Affected products
Fail2ban. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Fail2ban runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/fail2ban/fail2ban/commit/83109bc · Patch
- lists.opensuse.org/opensuse-updates/2013-04/msg00001.html
- lists.opensuse.org/opensuse-updates/2013-04/msg00002.html
- sourceforge.net/mailarchive/message.php?msg_id=30193056
- www.mandriva.com/security/advisories?name=MDVSA-2013:078
- www.openwall.com/lists/oss-security/2012/12/17/2
- bugs.gentoo.org/show_bug.cgi?id=447572
- bugzilla.redhat.com/show_bug.cgi?id=887914
- nvd.nist.gov/vuln/detail/CVE-2012-5642
- cve.org/CVERecord?id=CVE-2012-5642
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.