Skip to navigation

Security Advisory Updated nss_ldap packages fix buffer overflow

Advisory: RHSA-2002:175-16
Type: Security Advisory
Severity: N/A
Issued on: 2002-08-12
Last updated on: 2002-10-03
Affected Products: Red Hat Linux 6.2
Red Hat Linux 7.0
Red Hat Linux 7.1
Red Hat Linux 7.2
Red Hat Linux 7.3
CVEs (cve.mitre.org): CVE-2002-0374
CVE-2002-0825

Details

Updated nss_ldap packages are now available for Red Hat Linux 6.2, 7, 7.1,
7.2, and 7.3. These updates fix a potential buffer overflow which can occur
when nss_ldap is set to configure itself using information stored in DNS,
a format string bug in logging functions used in pam_ldap, and to properly
handle truncated DNS responses.

nss_ldap is a set of C library extensions that allow X.500 and LDAP
directory servers to be used as a primary source of aliases, ethers,
groups, hosts, networks, protocols, users, RPCs, services, and shadow
passwords (instead of or in addition to using flat files or NIS).

When versions of nss_ldap prior to nss_ldap-198 are configured without a
value for the "host" setting, nss_ldap will attempt to configure itself by
using SRV records stored in DNS. When parsing the results of the DNS
query, nss_ldap does not check that the data returned by the server will
fit into an internal buffer, leaving it vulnerable to a buffer overflow.
The Common Vulnerabilities and Exposures project (cve.mitre.org) has
assigned the name CAN-2002-0825 to this issue.

When versions of nss_ldap prior to nss_ldap-199 are configured without a
value for the "host" setting, nss_ldap will attempt to configure itself by
using SRV records stored in DNS. When parsing the results of the DNS
query, nss_ldap does not check that the data returned has not been
truncated by the resolver libraries to avoid a buffer overflow, and may
attempt to parse more data than is actually available, leaving it
vulnerable to a read buffer overflow.

Versions of pam_ldap prior to version 144 include a format string bug in
the logging function. The packages included in this erratum update pam_ldap
to version 144, fixing this bug. The Common Vulnerabilities and Exposures
project (cve.mitre.org) has assigned the name CAN-2002-0374 to this issue.

All users of nss_ldap should update to these errata packages which are not
vulnerable to the above issues. The errata packages are based on
nss_ldap-189 with the addition of a backported security patch and pam_ldap
version 144.

Thanks to the nss_ldap and pam_ldap team at padl.com for providing
information about these issues.


Solution

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.

Updated packages

Red Hat Linux 6.2

SRPMS:
ftp://updates.redhat.com/rhn/repository/NULL/nss_ldap/189-3.6/SRPMS/nss_ldap-189-3.6.src.rpm
Missing file
    MD5: 2acbcd575035a1afcb9e74694a6b7b39
 
Alpha:
ftp://updates.redhat.com/rhn/repository/NULL/nss_ldap/189-3.6/alpha/nss_ldap-189-3.6.alpha.rpm
Missing file
    MD5: 1a670c4c2a343b26508aa04ae06d2306
 
IA-32:
ftp://updates.redhat.com/rhn/repository/NULL/nss_ldap/189-3.6/i386/nss_ldap-189-3.6.i386.rpm
Missing file
    MD5: 4069002846304df7840cbe81517f8b3d
 
Sparc:
ftp://updates.redhat.com/rhn/repository/NULL/nss_ldap/189-3.6/sparc/nss_ldap-189-3.6.sparc.rpm
Missing file
    MD5: e26b1be702d0bf65f455e17d16844354
 
Red Hat Linux 7.0

SRPMS:
ftp://updates.redhat.com/rhn/repository/NULL/nss_ldap/189-3.7/SRPMS/nss_ldap-189-3.7.src.rpm
Missing file
    MD5: 9b44c5148cd1d3d688a9603f11a4d794
 
Alpha:
ftp://updates.redhat.com/rhn/repository/NULL/nss_ldap/189-3.7/alpha/nss_ldap-189-3.7.alpha.rpm
Missing file
    MD5: 2d245d41c6a27b62670a0e3cbc48e93b
 
IA-32:
ftp://updates.redhat.com/rhn/repository/NULL/nss_ldap/189-3.7/i386/nss_ldap-189-3.7.i386.rpm
Missing file
    MD5: 5c34d52cfa0425e8b3d0e63838729703
 
Red Hat Linux 7.1

SRPMS:
ftp://updates.redhat.com/rhn/repository/NULL/nss_ldap/189-3.7/SRPMS/nss_ldap-189-3.7.src.rpm
Missing file
    MD5: 9b44c5148cd1d3d688a9603f11a4d794
 
Alpha:
ftp://updates.redhat.com/rhn/repository/NULL/nss_ldap/189-3.7/alpha/nss_ldap-189-3.7.alpha.rpm
Missing file
    MD5: 2d245d41c6a27b62670a0e3cbc48e93b
 
IA-32:
ftp://updates.redhat.com/rhn/repository/NULL/nss_ldap/189-3.7/i386/nss_ldap-189-3.7.i386.rpm
Missing file
    MD5: 5c34d52cfa0425e8b3d0e63838729703
 
IA-64:
ftp://updates.redhat.com/rhn/repository/NULL/nss_ldap/189-3.7/ia64/nss_ldap-189-3.7.ia64.rpm
Missing file
    MD5: 27c07eb113adebc7d79d48d8c9df9356
 
Red Hat Linux 7.2

SRPMS:
ftp://updates.redhat.com/rhn/repository/NULL/nss_ldap/189-4/SRPMS/nss_ldap-189-4.src.rpm
Missing file
    MD5: d421772f8f5bd985dc2c288aee729ff6
 
IA-32:
ftp://updates.redhat.com/rhn/repository/NULL/nss_ldap/189-4/i386/nss_ldap-189-4.i386.rpm
Missing file
    MD5: 8dc0d40503cbc09a55a111fc53ec42ba
 
IA-64:
ftp://updates.redhat.com/rhn/repository/NULL/nss_ldap/189-4/ia64/nss_ldap-189-4.ia64.rpm
Missing file
    MD5: acd545a47e2be38ed8c9b94ea9801e4c
 
Red Hat Linux 7.3

SRPMS:
ftp://updates.redhat.com/rhn/repository/NULL/nss_ldap/189-4/SRPMS/nss_ldap-189-4.src.rpm
Missing file
    MD5: d421772f8f5bd985dc2c288aee729ff6
 
IA-32:
ftp://updates.redhat.com/rhn/repository/NULL/nss_ldap/189-4/i386/nss_ldap-189-4.i386.rpm
Missing file
    MD5: 8dc0d40503cbc09a55a111fc53ec42ba
 

References


Keywords

automatic, configuration, dns, MAXPACKET, nss_ldap


These packages are GPG signed by Red Hat for security. Our key and details on how to verify the signature are available from:
https://www.redhat.com/security/team/key/#package

The Red Hat security contact is secalert@redhat.com. More contact details at http://www.redhat.com/security/team/contact/