Users login

Create an account »

JOIN XATRIX

Users login

Home » Hacking News » SuSE-SA:2002:046-pine

SuSE-SA:2002:046-pine

by Nikola Strahija on November 25th, 2002 Content of this advisory: 1) security vulnerability resolved: - heap buffer overflow while parsing mail address problem description, discussion, solution and upgrade information 2) pending vulnerabilities, solutions, workarounds: - sparc distribution - WindowMaker 3) standard appendix (further information)


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

Pine, Program for Internet News and Email, is a well known and widely
used eMail client.
While parsing and escaping characters of eMail addresses pine does not
allocate enough memory for storing the escaped mailbox part of an
address. This results in a buffer overflow on the heap that will make
pine crash. The offending eMail can just be deleted manually or by using
another mail user agent.

A possible temporary workaround is to filter the respective header
lines by a mail delivery agent (such as procmail).

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/pine-4.44-224.i586.rpm
8c32d5571d7488e31f693a884dedb81e
patch rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/pine-4.44-224.i586.patch.rpm
467b8b318958b0ead3f30fa7b1f5a9a0
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/pine-4.44-224.src.rpm
9b1ff436719cf9752cda3ddd711e80a7

SuSE-8.0:
ftp://ftp.suse.com/pub/suse/i386/update/8.0/n1/pine-4.44-222.i386.rpm
01d9e82164a5ce4037b84be1b2ed4228
patch rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.0/n1/pine-4.44-222.i386.patch.rpm
162c4265909af7805f7aeaf3e12e8763
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/pine-4.44-222.src.rpm
d724e02b1ea3783e5bfb01ae9728d7cf

SuSE-7.3:
ftp://ftp.suse.com/pub/suse/i386/update/7.3/n1/pine-4.33-266.i386.rpm
140c58adf7d0b2113d5bbbbb20de67e2
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/pine-4.33-266.src.rpm
100c86e88ce357b0efacf7dfe2ab592c

SuSE-7.2:
ftp://ftp.suse.com/pub/suse/i386/update/7.2/n1/pine-4.33-266.i386.rpm
bd44232250b3def07cab81064dad11f2
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/pine-4.33-266.src.rpm
e28daa1f2d66135fcf5951c9b2dc19be

SuSE-7.1:
ftp://ftp.suse.com/pub/suse/i386/update/7.1/n1/pine-4.33-263.i386.rpm
9bdd3394336a786b0711b8e98ab4a268
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/pine-4.33-263.src.rpm
630478b751a24e86c52fe645be9365c4



Sparc Platform:

SuSE-7.3:
ftp://ftp.suse.com/pub/suse/sparc/update/7.3/n1/pine-4.33-97.sparc.rpm
5187b311c27f043178a12ae186d228a6
source rpm(s):
ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/pine-4.33-97.src.rpm
9616303edadfd899785f3ac12d2dc02a



AXP Alpha Platform:

SuSE-7.1:
ftp://ftp.suse.com/pub/suse/axp/update/7.1/n1/pine-4.33-85.alpha.rpm
f5155d79236e3ec15c463f586f731c17
source rpm(s):
ftp://ftp.suse.com/pub/suse/axp/update/7.1/zq1/pine-4.33-85.src.rpm
75365b21b97c8a2f722d95491f62d305




PPC Power PC Platform:

SuSE-7.3:
ftp://ftp.suse.com/pub/suse/ppc/update/7.3/n1/pine-4.33-143.ppc.rpm
98955d956701d7c6c3e0522468377044
source rpm(s):
ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/pine-4.33-143.src.rpm
d4cdfbf180711ae6e9bab31b87cbb3bd

SuSE-7.1:
ftp://ftp.suse.com/pub/suse/ppc/update/7.1/n1/pine-4.33-141.ppc.rpm
0b0512af4bdffc654bbd1774c2c8f8a9
source rpm(s):
ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/pine-4.33-141.src.rpm
0ee371a8935abe58aa53221606960bbe


______________________________________________________________________________

2) Pending vulnerabilities in SuSE Distributions and Workarounds:

- sparc distribution
We have moved the update directories for the SuSE SPARC distributions
7.0 and 7.1 as well as the distribution directory for 7.1 to the
discontinued/ tree on ftp.suse.com. We urge all of the sparc users to
upgrade to the SuSE-7.3-sparc distribution, the latest in the row for
the sparc platform. Resource limitations keep us from timely providing
update packages for the older sparc distribution.

- WindowMaker
A bug was found in the image processing code of windowmaker.
It could allow attackers to execute arbitrary code as the user
running windowmaker by tricking the user into viewing special
crafted malicious image files. New packages are currently being
built and will be available soon.

______________________________________________________________________________

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 »