Users login

Create an account »

JOIN XATRIX

Users login

Home » Hacking News » SuSE Security Announcement: fetchmail (SuSE-SA:2003:001)

SuSE Security Announcement: fetchmail (SuSE-SA:2003:001)

by Nikola Strahija on January 3rd, 2003 Content of this advisory: 1) security vulnerability resolved: - heap buffer overflow while expanding email addresses problem description, discussion, solution and upgrade information 2) pending vulnerabilities, solutions, workarounds: - none 3) standard appendix (further information)


1) problem description, brief discussion, solution, upgrade information

fetchmail is used to download emails from POP-, IMAP-, ETRN- or ODMR-
servers.
Stefan Esser of e-matters reported a bug in fetchmail's mail address
expanding code which can lead to remote system compromise.
When fetchmail expands email addresses in mail headers it doesn not
allocated enough memory. An attacker can send a malicious formatted mail
header to exhaust the memory allocated by fetchmail to overwrite parts of
the heap. This can be exploited to execute arbitrary code.

There is no temporary fix known. Please install the new packages from
our FTP servers.

Please download the update package for your distribution and verify its
integrity by the methods listed in section 3) of this announcement.
Then, install the package using the command "rpm -Fhv file.rpm" to apply
the update.
Our maintenance customers are being notified individually. The packages
are being offered to install from the maintenance web.


Intel i386 Platform:

SuSE-8.1:
ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/fetchmail-5.9.13-54.i586.rpm
9a8a8d20e57dd5552fc35c1d17d8f5b2
patch rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/fetchmail-5.9.13-54.i586.patch.rpm
9bfc1e8511d3be0da42cc32b06ffef47
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/fetchmail-5.9.13-54.src.rpm
8e1310dfe46748320b1c92813a1e9294

SuSE-8.0:
ftp://ftp.suse.com/pub/suse/i386/update/8.0/n1/fetchmail-5.9.0-279.i386.rpm
3be7d683cabd44a5f83b1c0f50a1b1e9
patch rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.0/n1/fetchmail-5.9.0-279.i386.patch.rpm
38c7c2cca1db2e524b1e4f29ef1e8606
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/fetchmail-5.9.0-279.src.rpm
d63b65fa7ddba8f93ffc47fa3fc84fe4

SuSE-7.3:
ftp://ftp.suse.com/pub/suse/i386/update/7.3/n1/fetchmail-5.9.0-280.i386.rpm
32e4614b5cdf6afea748036e70d80bab
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/fetchmail-5.9.0-280.src.rpm
299b9512dbe87c8e16f14d28288115d3

SuSE-7.2:
ftp://ftp.suse.com/pub/suse/i386/update/7.2/n1/fetchmail-5.8.0-78.i386.rpm
f3267936cae7fc659007291ac15f42b4
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/fetchmail-5.8.0-78.src.rpm
318d9781b715741cc9d27b102544d30a

SuSE-7.1:
ftp://ftp.suse.com/pub/suse/i386/update/7.1/n1/fetchmail-5.6.5-40.i386.rpm
311076babc7c2a75b13f24a446327ced
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/fetchmail-5.6.5-40.src.rpm
55c64a56f10aa2904955188b1a40a34a



Sparc Platform:

SuSE-7.3:
ftp://ftp.suse.com/pub/suse/sparc/update/7.3/n1/fetchmail-5.9.0-66.sparc.rpm
5a2abaab7029167944512b8aab306770
source rpm(s):
ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/fetchmail-5.9.0-66.src.rpm
95725d5f8aa677641ea1b041222ed8be



AXP Alpha Platform:

SuSE-7.1:
ftp://ftp.suse.com/pub/suse/axp/update/7.1/n1/fetchmail-5.6.5-30.alpha.rpm
ad4833f9e2a4e6bf31336f2dc363d3e1
source rpm(s):
ftp://ftp.suse.com/pub/suse/axp/update/7.1/zq1/fetchmail-5.6.5-30.src.rpm
ac786b49dcbf71357b4894c0b4fd4b55



PPC Power PC Platform:

SuSE-7.3:
ftp://ftp.suse.com/pub/suse/ppc/update/7.3/n1/fetchmail-5.9.0-205.ppc.rpm
6ea104ac2cd3f00a511de286f571ea54
source rpm(s):
ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/fetchmail-5.9.0-205.src.rpm
94def5a2d8752920375ddaf8b056c3ca

SuSE-7.1:
ftp://ftp.suse.com/pub/suse/ppc/update/7.1/n1/fetchmail-5.6.5-29.ppc.rpm
053e1842b7830489f21573c7e5dc25c4
source rpm(s):
ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/fetchmail-5.6.5-29.src.rpm
f3220918ec06565d7c588a72dc2514bb


______________________________________________________________________________

2) Pending vulnerabilities in SuSE Distributions and Workarounds:

- none

______________________________________________________________________________

3) standard appendix: authenticity verification, additional information

- Package authenticity verification:

SuSE update packages are available on many mirror ftp servers all over
the world. While this service is being considered valuable and important
to the free and open source software community, many users wish to be
sure about the origin of the package and its content before installing
the package. There are two verification methods that can be used
independently from each other to prove the authenticity of a downloaded
file or rpm package:
1) md5sums as provided in the (cryptographically signed) announcement.
2) using the internal gpg signatures of the rpm package.

1) execute the command
md5sum
after you downloaded the file from a SuSE ftp server or its mirrors.
Then, compare the resulting md5sum with the one that is listed in the
announcement. Since the announcement containing the checksums is
cryptographically signed (usually using the key [email protected]),
the checksums show proof of the authenticity of the package.
We disrecommend to subscribe to security lists which cause the
email message containing the announcement to be modified so that
the signature does not match after transport through the mailing
list software.
Downsides: You must be able to verify the authenticity of the
announcement in the first place. If RPM packages are being rebuilt
and a new version of a package is published on the ftp server, all
md5 sums for the files are useless.

2) rpm package signatures provide an easy way to verify the authenticity
of an rpm package. Use the command
rpm -v --checksig
to verify the signature of the package, where is the
filename of the rpm package that you have downloaded. Of course,
package authenticity verification can only target an un-installed rpm
package file.
Prerequisites:
a) gpg is installed
b) The package is signed using a certain key. The public part of this
key must be installed by the gpg program in the directory
~/.gnupg/ under the user's home directory who performs the
signature verification (usually root). You can import the key
that is used by SuSE in rpm packages for SuSE Linux by saving
this announcement to a file ("announcement.txt") and
running the command (do "su -" to be root):
gpg --batch; gpg < announcement.txt | gpg --import
SuSE Linux distributions version 7.1 and thereafter install the
key "[email protected]" upon installation or upgrade, provided that
the package gpg is installed. The file containing the public key
is placed at the top-level directory of the first CD (pubring.gpg)
and at ftp://ftp.suse.com/pub/suse/pubring.gpg-build.suse.de .


- SuSE runs two security mailing lists to which any interested party may
subscribe:

[email protected]
- general/linux/SuSE security discussion.
All SuSE security announcements are sent to this list.
To subscribe, send an email to
.

[email protected]
- SuSE's announce-only mailing list.
Only SuSE's security announcements are sent to this list.
To subscribe, send an email to
.

For general information or the frequently asked questions (faq)
send mail to:
or
respectively.


Newsletter signup

Signup to our monthly newsletter and stay in touch with IT news!

Free E-books

We've got ebooks! But they're not online. :( Please give us a few days to bring downloads back.

Contact

Have something to say or just wanna drop us a line? Please keep this in mind: to spam, we reply with spam.

Contact us »