Skip to content
Noroxi
CVE-2013-7177· NVD / CVE Program· CNA certcc

config/filter.d/cyrus-imap.conf in the cyrus-imap filter in Fail2ban before 0.8.11 allows remote attackers to trigger the blocking of an arb

Noroxi assessment

Priority: Monitor (action score 21/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 3.2% (FIRST EPSS); higher than 87.9% of all records.
  • No special conditions are required; it is repeatable.
  • Fixed version: fail2ban (Debian:12) 0.8.11-1; fail2ban (Debian:6.0) 0.8.4-3+squeeze3; fail2ban (Debian:7) 0.8.6-3wheezy3.

Low priority for now. Upgrade to fail2ban (Debian:12) 0.8.11-1; fail2ban (Debian:6.0) 0.8.4-3+squeeze3; fail2ban (Debian:7) 0.8.6-3wheezy3 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

config/filter.d/cyrus-imap.conf in the cyrus-imap 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.

MediumCVSS 5.0 · v2.0—No exploit Fix available
Published
Feb 1, 2014
Updated
Jun 16, 2026
EPSS
3.2% · 88th percentile

Report tools

JSON

Action score

21

Monitor

Low priority for now.

CVSS
20 / 40 · 5.0 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 3.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2013-7177

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Port scanning: 5 full scans a day (members only)
  • Uptime monitoring: 1 site, instant email when it goes down
  • Verify your domain: subdomains and takeover risk scanned every week
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for fail2ban records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
fail2banfail2ban

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • fail2ban fail2banup to 0.8.10 inclusive
  • fail2ban fail2ban0.1.0
  • fail2ban fail2ban0.1.1
  • fail2ban fail2ban0.1.2
  • fail2ban fail2ban0.3.0
  • fail2ban fail2ban0.3.1
  • fail2ban fail2ban0.4.0
  • fail2ban fail2ban0.4.1
  • fail2ban fail2ban0.5.0
  • fail2ban fail2ban0.5.1
  • fail2ban fail2ban0.5.2
  • fail2ban fail2ban0.5.3
  • fail2ban fail2ban0.5.4
  • fail2ban fail2ban0.5.5
  • fail2ban fail2ban0.6.0
  • fail2ban fail2ban0.6.1
  • fail2ban fail2ban0.7.0
  • fail2ban fail2ban0.7.1
  • fail2ban fail2ban0.7.2
  • fail2ban fail2ban0.7.3

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12fail2banbefore 0.8.11-10.8.11-1
Debian:6.0fail2banbefore 0.8.4-3+squeeze30.8.4-3+squeeze3
Debian:7fail2banbefore 0.8.6-3wheezy30.8.6-3wheezy3
openSUSE:Tumbleweedfail2banbefore 0.9.5-1.10.9.5-1.1

Same product

fail2ban: all records

Other highest-scoring records for the same primary product.

  • CVE-2021-32749Possible RCE vulnerability in mailing action using mailutils (mail-whois)
    33Monitor
  • CVE-2012-5642server/action.py in Fail2ban before 0.8.8 does not properly handle the content of the matches tag, which might allow remote attackers to tri
    31Monitor
  • CVE-2007-4321fail2ban 0.8 and earlier does not properly parse sshd log files, which allows remote attackers to add arbitrary hosts to the /etc/hosts.deny
    29Monitor
  • CVE-2026-109786In fail2ban 0.10.5 through 1.1.1 before ddd879d, the sshd filter (config/filter.d/sshd.conf) accepts an "on <token>" suffix after the host a
    21Monitor
  • CVE-2013-7176config/filter.d/postfix.conf in the postfix filter in Fail2ban before 0.8.11 allows remote attackers to trigger the blocking of an arbitrary
    21Monitor
  • CVE-2013-2178The apache-auth.conf, apache-nohome.conf, apache-noscript.conf, and apache-overflows.conf files in Fail2ban before 0.8.10 do not properly va
    21Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:fail2ban0.8.11-1 · Debian:12Package registry (OSV)
opensuse:fail2ban0.9.5-1.1 · openSUSE:TumbleweedPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
P · the service can be disrupted
Attack complexity
Low
Confidentiality impact
None
Integrity impact
None
Availability impact
P

Weakness class (CWE)

CWE-20 · Improper Input Validation

CVSS vector

AV:N/AC:L/Au:N/C:N/I:N/A:P

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records