Skip to content
Fencer Intel
medium 4.3

CVE-2010-1167 json

fetchmail 4.6.3 through 6.3.16, when debug mode is enabled, does not properly handle invalid characters in a multi-character locale, which…

published 16y ago modified 4mo ago also EUVD-2010-1197

cvss
4.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.2%
EPSS 2.2% chance of exploitation in 30 days, percentile 82%
public exploits
0
none known

Summary

fetchmail 4.6.3 through 6.3.16, when debug mode is enabled, does not properly handle invalid characters in a multi-character locale, which allows remote attackers to cause a denial of service (memory consumption and application crash) via a crafted (1) message header or (2) POP3 UIDL list.

Patch / fix

  • fetchmail Debian 14, Debian 13, Debian 12 6.3.16-2

debian advisories DEBIAN-CVE-2010-1167

  • fetchmail openSUSE Tumbleweed 6.3.26-13.4

opensuse advisories openSUSE-SU-2024:10194-1

Is CVE-2010-1167 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2010-1167 updated cvss 2.6

fetchmail: denial of service in debug mode with multichar locales

  • Red Hat Enterprise Linux 4 fetchmail Red Hat Enterprise Linux 5 fetchmail
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux 6 fetchmail
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.20% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:N/A:P

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.