Bug 163816 - CAN-2005-2335 fetchmail overflow from malicious pop3 server
CAN-2005-2335 fetchmail overflow from malicious pop3 server
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: fetchmail (Show other bugs)
All Linux
medium Severity high
: ---
: ---
Assigned To: Miloslav Trmač
Brock Organ
: Security
Depends On:
  Show dependency treegraph
Reported: 2005-07-21 08:41 EDT by Mark J. Cox
Modified: 2007-11-30 17:07 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-07-25 15:43:31 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Proposed patch from SUSE (1.01 KB, patch)
2005-07-21 08:41 EDT, Mark J. Cox
no flags Details | Diff

  None (edit)
Description Mark J. Cox 2005-07-21 08:41:05 EDT
We were alerted today to a Debian bug report showing a flaw where a malicious
POP3 server could overflow a stack buffer in fetchmail.

Draft advisory at http://fetchmail.berlios.de/fetchmail-SA-2005-01.txt

More details at end of http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=212762

Most likely also affects RHEL3 and RHEL2.1 (although code in RHEL2.1 is
substantially different).
Comment 1 Mark J. Cox 2005-07-21 08:41:05 EDT
Created attachment 117020 [details]
Proposed patch from SUSE
Comment 3 Tomas Mraz 2005-07-21 09:24:38 EDT
Yep, this bug applies to RHEL2.1 as well. File pop3.c line 540.
Comment 4 Mark J. Cox 2005-07-25 03:52:41 EDT
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.

Comment 6 Charlie Brady 2005-07-27 23:03:36 EDT
Summary is wrong, CVE number is CAN-2005-2355, not CAN-2005-2335.
Comment 7 Charlie Brady 2005-07-27 23:06:41 EDT
Sorry, I was wrong.  CAN-2005-2335 *is* correct. FC3 advisory was incorrect.

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