Users login

Create an account »


Users login

Home » Hacking News » SuSE-SA:2002:047-OpenLDAP2


by Nikola Strahija on December 6th, 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

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:

patch rpm(s):
source rpm(s):

source rpm(s):

source rpm(s):

source rpm(s):

Sparc Platform:

source rpm(s):

AXP Alpha Platform:

source rpm(s):

PPC Power PC Platform:

source rpm(s):

source rpm(s):


2) Pending vulnerabilities in SuSE Distributions and Workarounds:

- traceroute-nanog
Due to recent postings on [email protected] 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
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.
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 .

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

[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:

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.


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

Contact us »