Updated OpenLDAP packages available for Red Hat Linux 6.2, 7, and 7.1

Updated openldap packages are now available for Red Hat Linux 6.2, 7, and
7.1. These packages include fixes for problems which could allow a
malicious remote user to crash a server.

When subjected to the PROTOS LDAPv3 test suite, versions of
OpenLDAP 1.2 through 1.2.11 and 2.0 through 2.0.7 were found to
have vulnerabilities which could be exploited by causing them
to attempt to decode an improperly encoded request. These
vulnerabilities were fixed in OpenLDAP 1.2.12 and 2.0.8.

Before applying this update, make sure all previously released errata
relevant to your system have been applied.

To update all RPMs for your particular architecture, run:

rpm -Fvh [filenames]

where [filenames] is a list of the RPMs you wish to upgrade. Only those
RPMs which are currently installed will be updated. Those RPMs which are
not installed but included in the list will not be updated. Note that you
can also use wildcards (*.rpm) if your current directory *only* contains
the desired RPMs.

Please note that this update is also available via Red Hat Network. Many
people find this an easier way to apply updates. To use Red Hat Network,
launch the Red Hat Update Agent with the following command:

up2date

This will start an interactive process that will result in the appropriate
RPMs being upgraded on your system.

Users of Red Hat Linux 6.2 should note that the openldap package has been
split into the openldap, openldap-servers, and openldap-clients packages.
Users may need to manually select the openldap-servers and
openldap-clients packages to ensure that they are upgraded properly.

This update also transitions users of Red Hat Linux 7 to OpenLDAP 2.0,
which uses a different on-disk format for storing the LDBM databases
which are used by slapd, the standalone LDAP server. Users who are
running an OpenLDAP server will need to dump out their old databases by
running "ldbmcat -n" and reload them using the "slapadd" command. They
also should ensuring that the "ldap" user continues to have read/write
access to the database files.

http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2001-0977
http://www.cert.org/advisories/CA-2001-18.html

ber