CVE-2012-5642: High severity fail2ban vulnerability

Published Dec 17, 2012
·
Updated

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.

Other sources

The release notes for fail2ban 0.8.8 [1],[2] indicate:

[83109bc] IMPORTANT: escape the content of <matches> (if used in custom action files) since its value could contain arbitrary symbols. Thanks for discovery go to the NBS System security team

This could cause issues on the system running fail2ban as it scans log files, depending on what content is matched. There isn't much more detail about this issue than what is described above, so I think it may largely depend on the type of regexp used (what it matches) and the contents of the log file being scanned (whether or not an attacher could insert something that could be used in a malicious way).

The upstream git commit [3].

[1] https://raw.github.com/fail2ban/fail2ban/master/ChangeLog [2] http://sourceforge.net/mailarchive/message.php?msgid=30193056 [3] https://github.com/fail2ban/fail2ban/commit/83109bc

— Red Hat

Affected Software

34 affected components
fail2ban fail2ban<=0.8.7.1
fail2ban fail2ban=0.1.0
fail2ban fail2ban=0.1.1
fail2ban fail2ban=0.1.2
fail2ban fail2ban=0.3.0
fail2ban fail2ban=0.3.1
fail2ban fail2ban=0.4.0
fail2ban fail2ban=0.4.1
fail2ban fail2ban=0.5.0
fail2ban fail2ban=0.5.1
fail2ban fail2ban=0.5.2
fail2ban fail2ban=0.5.3
fail2ban fail2ban=0.5.4
fail2ban fail2ban=0.5.5
fail2ban fail2ban=0.6.0
fail2ban fail2ban=0.6.1
fail2ban fail2ban=0.7.0
fail2ban fail2ban=0.7.1
fail2ban fail2ban=0.7.2
fail2ban fail2ban=0.7.3
fail2ban fail2ban=0.7.4
fail2ban fail2ban=0.7.5
fail2ban fail2ban=0.7.6
fail2ban fail2ban=0.7.7
fail2ban fail2ban=0.7.8
fail2ban fail2ban=0.7.9
fail2ban fail2ban=0.8.0
fail2ban fail2ban=0.8.1
fail2ban fail2ban=0.8.2
fail2ban fail2ban=0.8.3
fail2ban fail2ban=0.8.4
fail2ban fail2ban=0.8.5
fail2ban fail2ban=0.8.6
fail2ban fail2ban=0.8.7

Event History

Dec 17, 2012
Data Sourced
via Red Hat·03:38 PM
DescriptionSeverityAffected Software
Dec 31, 2012
CVE Published
via MITRE·11:00 AM
Data Sourced
via MITRE·11:00 AM
Description

Frequently Asked Questions

1

What is the severity of CVE-2012-5642?

CVE-2012-5642 is classified as a moderate severity vulnerability that could potentially allow remote attackers to trigger unsafe behavior in a custom action file.

2

How do I fix CVE-2012-5642?

To fix CVE-2012-5642, upgrade to Fail2ban version 0.8.8 or later, where the vulnerability has been addressed.

3

What versions of Fail2ban are affected by CVE-2012-5642?

CVE-2012-5642 affects Fail2ban versions prior to 0.8.8, including all versions up to 0.8.7.1.

4

What kind of attacks can be executed using CVE-2012-5642?

Attackers can exploit CVE-2012-5642 to manipulate the content of the matches tag leading to unsafe actions specified in custom action files.

5

Is there any workaround for CVE-2012-5642?

There are no official workarounds for CVE-2012-5642, and users are strongly advised to upgrade to the patched version.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203