SuSE: SA-2002:047 Moderate: OpenLDAP2 Buffer Overflow Remote Threat

Warning: Undefined array key "advisoryid" in /var/www/www.linuxsecurity.com-443/html/tmp/regularlabs/custom_php/3604884_1edcd913e2b52798c5b9126b8927230e on line 19

______________________________________________________________________________

 SuSE Security Announcement

 Package: OpenLDAP2
 Announcement-ID: SuSE-SA:2002:047
 Date: Fri Dec 6 11:11:11 MET 2002
 Affected products: 7.1, 7.2, 7.3, 8.0,
 SuSE eMail Server III, 3.1,
 SuSE Linux Connectivity Server,
 SuSE Linux Enterprise Server 7,
 SuSE Linux Office Server
 Vulnerability Type: remote command execution
 Severity (1-10): 6
 SuSE default package: no
 Cross References: -

 Content of this advisory:
 1) security vulnerability resolved: Buffer overflows in openldap2.
 problem description, discussion, solution and upgrade information
 2) pending vulnerabilities, solutions, workarounds:
 - traceroute-nanog
 - gnuplot
 3) standard appendix (further information)

______________________________________________________________________________

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

 OpenLDAP is the Open Source implementation of the Lightweight Directory
 Access Protocol (LDAP) and is used in network environments for distributing
 certain information such as X.509 certificates or login information.

 The SuSE Security Team reviewed critical parts of that package and found
 several buffer overflows and other bugs remote attackers could exploit
 to gain access on systems running vulnerable LDAP servers.
 In addition to these bugs, various local exploitable bugs within the
 OpenLDAP2 libraries (openldap2-devel package) have been fixed.

 Since there is no workaround possible except shutting down the LDAP server,
 we strongly recommend an update.
 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.

 To be sure the update takes effect you have to restart the LDAP server
 by executing the following command as root:

 /etc/rc.d/ldap restart

 i386 Intel Platform:

 SuSE-8.0:

 0facbec09078e1a849b629a335d25dcf

 90b2aff137bd510930835b7a7cb7bc1e
 patch rpm(s):

 aac122b6dda874c97d2e3f8e43a33897

 e032d25cd37167b956a41b45e7c1bc60
 source rpm(s):

 773c24a1654055b692dbfe6c1ce436f2

 SuSE-7.3:

 0c3078060330559ae49d67cdb0def908

 4d09ba68655344abc273f7cb67fee482
 source rpm(s):

 58706b1104fec0d6a6533e5f6decb8cd

 SuSE-7.2:

 28f575d89d8fbb9c269b158d12b599a6

 7edf8a034f6de9ec15fd0d0e683e25e3
 source rpm(s):

 1aac2bc81f82065513845a0e923433bf

 SuSE-7.1:

 901b6452a24470b5cf39223e4b4a611d
 source rpm(s):

 d5d0a0a397f919b2f5d644c517dd56a5

 Sparc Platform:

 SuSE-7.3:

 4639159e2de3a53115b4a7a918a79864

 609773f10ce2ea8953f4fc8772f4af23
 source rpm(s):

 70758c3e7c36f10a53980eaeb6bddea3

 AXP Alpha Platform:

 SuSE-7.1:

 3d6bf0861070044c54ed52e8777192b6
 source rpm(s):

 3e0867844268b399d6ac2b9788d017f4

 PPC Power PC Platform:

 SuSE-7.3:

 fa2268bf1629c69db048371b67a1e177

 e5f6ea2f05c6f5904834e8083ef8502b
 source rpm(s):

 5c88d479f0f54b6b933f11a63e8d0c42

 SuSE-7.1:

 b6630f01be5e342cba2167a1f69583bf
 source rpm(s):

 5664341323793814db38b162d4cf07dc

______________________________________________________________________________

2) Pending vulnerabilities in SuSE Distributions and Workarounds:

 - traceroute-nanog
 Due to recent postings on bugtraq@ new
 traceroute-nanog packages are currently being built and
 will be released as soon as possible.

 - gnuplot
 An error in a patch for french documentation added by SuSE leads to a
 buffer overflow in gnuplot that can be exploited to gain root
 privileges by a local attacker. gnuplot is installed setuid root on
 SuSE Linux before (excluding) 8.0 to be able to display graphics with
 the SVGA library. We have provided update packages at the usual
 location that fix the vulnerability.

______________________________________________________________________________

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 security@suse.de),
 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 "build@suse.de" 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 runs two security mailing lists to which any interested party may
 subscribe:

 suse-security@suse.com
 - general/linux/SuSE security discussion.
 All SuSE security announcements are sent to this list.
 To subscribe, send an email to
 <suse-security-subscribe@suse.com>.

 suse-security-announce@suse.com
 - SuSE's announce-only mailing list.
 Only SuSE's security announcements are sent to this list.
 To subscribe, send an email to
 <suse-security-announce-subscribe@suse.com>.

 For general information or the frequently asked questions (faq)
 send mail to:
 <suse-security-info@suse.com> or
 <suse-security-faq@suse.com> respectively.

 ==================================================================== SuSE's security contact is <security@suse.com> or <security@suse.de>.
 The <security@suse.de> 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 <security@suse.de>
pub 1024D/9C800ACA 2000-10-19 SuSE Package Signing Key <build@suse.de>