Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 221981 - CVE-2006-5867 fetchmail not enforcing TLS for POP3 properly
CVE-2006-5867 fetchmail not enforcing TLS for POP3 properly
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: fetchmail (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Miloslav Trmač
Brock Organ
: Security
Depends On: 223661
  Show dependency treegraph
Reported: 2007-01-09 09:16 EST by Lubomir Kundrak
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version: RHSA-2007-0018
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-01-31 12:20:37 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Statement from mitr about the issues (2.84 KB, text/plain)
2007-01-09 09:16 EST, Lubomir Kundrak
no flags Details

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2007:0018 normal SHIPPED_LIVE Moderate: fetchmail security update 2007-01-31 12:20:07 EST

  None (edit)
Description Lubomir Kundrak 2007-01-09 09:16:31 EST
Description of problem:

fetchmail issued an advisoty fetchmail-SA-2006-02 fixing numerous issues
with TLS support. Two of them raise an opportiounity for an attacker to do
a MiM attack. See the attached e-mail from mitr for more details.
Comment 1 Lubomir Kundrak 2007-01-09 09:16:31 EST
Created attachment 145163 [details]
Statement from mitr about the issues
Comment 5 Red Hat Bugzilla 2007-01-31 12:20:37 EST
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.