Stay Secure with the Latest Linux Advisories

security advisorySUSE Linuxremote denial-of-service

SuSE: 2002:046 Moderate: Pine Buffer Overflow Remote Denial-of-Service

While parsing and escaping characters of eMail addresses pine does not allocate enough memory for storing the escaped mailbox part of an address.. ______________________________________________________________________________ SuSE Security Announcement Package: pine Announcement-ID: SuSE-SA:2002:046 Date: Monday, Nov 25th 2002 10:30 MEST Affected products: 7.1, 7.2, 7.3, 8.0, 8.1 SuSE Linux Database Server SuSE eMail Server 3.1 SuSE eMail Server III SuSE Firewall Adminhost VPN SuSE Linux Admin-CD for Firewall SuSE Firewall on CD 2 - VPN SuSE Firewall on CD 2 SuSE Linux Enterprise Server for S/390 SuSE Linux Connectivity Server SuSE Linux Enterprise Server 7 for IA32 SuSE Linux Office Server Vulnerability Type: remote denial-of-service Severity (1-10): 4 SuSE default package: yes (7.1 - 8.0) no (8.1) Cross References: none 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 escapingcharacters 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: 8c32d5571d7488e31f693a884dedb81e patch rpm(s): 467b8b318958b0ead3f30fa7b1f5a9a0 source rpm(s): 9b1ff436719cf9752cda3ddd711e80a7 SuSE-8.0: 01d9e82164a5ce4037b84be1b2ed4228 patch rpm(s): 162c4265909af7805f7aeaf3e12e8763 source rpm(s): d724e02b1ea3783e5bfb01ae9728d7cf SuSE-7.3: 140c58adf7d0b2113d5bbbbb20de67e2 source rpm(s): 100c86e88ce357b0efacf7dfe2ab592c SuSE-7.2: bd44232250b3def07cab81064dad11f2 source rpm(s): e28daa1f2d66135fcf5951c9b2dc19be SuSE-7.1: 9bdd3394336a786b0711b8e98ab4a268 source rpm(s): 630478b751a24e86c52fe645be9365c4 Sparc Platform: SuSE-7.3: 5187b311c27f043178a12ae186d228a6 source rpm(s): 9616303edadfd899785f3ac12d2dc02a AXP Alpha Platform: SuSE-7.1: f5155d79236e3ec15c463f586f731c17 source rpm(s): 75365b21b97c8a2f722d95491f62d305 PPC Power PC Platform: SuSE-7.3: 98955d956701d7c6c3e0522468377044 source rpm(s): d4cdfbf180711ae6e9bab31b87cbb3bd SuSE-7.1: 0b0512af4bdffc654bbd1774c2c8f8a9 source rpm(s): 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 islisted in the announcement. Since the announcement containing the checksums is cryptographically signed (usually using the key This email address is being protected from spambots. You need JavaScript enabled to view it. ), 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 " This email address is being protected from spambots. You need JavaScript enabled to view it. " 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 . - SuSE runstwo security mailing lists to which any interested party may subscribe: This email address is being protected from spambots. You need JavaScript enabled to view it. - general/linux/SuSE security discussion. All SuSE security announcements are sent to this list. To subscribe, send an email to . This email address is being protected from spambots. You need JavaScript enabled to view it. - 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. ==================================================================== SuSE's security contact is or . The public key is listed below. ====================================================================______________________________________________________________________________ The information in this advisory may be distributed or reproduced, provided that the advisory is not modified in any way. In particular, it is desired that the clear-text signature shows proof of the authenticity of the text. SuSE Linux AG makes no warranties of any kind whatsoever with respect to the information contained in this security advisory. Type Bits/KeyID Date User ID pub 2048R/3D25D3D9 1999-03-06 SuSE Security Team pub 1024D/9C800ACA 2000-10-19 SuSE Package Signing Key . Promptly address the remote DoS vulnerability caused by the pine buffer overflow affecting various SuSE releases. Find additional information here!. Pine Buffer Overflow, SUSE Security Update, Email Client Threat. . LinuxSecurity.com Team

Nov 25, 2002 SuSE