Skip to content
Fencer Vulns
high 7.5

CVE-2006-5170 json

pam_ldap in nss_ldap on Red Hat Enterprise Linux 4, Fedora Core 3 and earlier, and possibly other distributions does not return an error co…

published 2006-10-04 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-5155

cvss
7.5
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
4.1%
EPSS 4.1% chance of exploitation in 30 days, percentile 90%
public exploits
0
none known

Summary

pam_ldap in nss_ldap on Red Hat Enterprise Linux 4, Fedora Core 3 and earlier, and possibly other distributions does not return an error condition when an LDAP directory server responds with a PasswordPolicyResponse control response, which causes the pam_authenticate function to return a success code even if authentication has failed, as originally reported for xscreensaver.

Patch / fix

  • libpam-ldap Debian 11 180-1.2

debian advisories DEBIAN-CVE-2006-5170

  • nss_ldap RHEL 4 226-17

red hat advisories RHSA-2006:0719

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2006-5170 updated

security flaw

  • Red Hat Enterprise Linux AS version 4 nss_ldap 226-17 Red Hat Enterprise Linux Desktop version 4 nss_ldap 226-17 Red Hat Enterprise Linux ES version 4 nss_ldap 226-17 Red Hat Enterprise Linux WS version 4 nss_ldap 226-17
    fixed: vendor fix RHSA-2006:0719

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

4.15% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Classification

Weakness
  • CWE-755 Improper Handling of Exceptional Conditions

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.