LiveActive security incident?Get immediate response
CVE Record

CVE-2005-2377: nss_ldap 181 to versions before 213, as used in Mandrake Corporate Server and Mandrake 10.0, and other oper...

nss_ldap 181 to versions before 213, as used in Mandrake Corporate Server and Mandrake 10.0, and other operating systems, does not properly handle a SIGPIPE signal when sending a search request to an LDAP directory server, which might allow remote attackers to cause a denial of service (crond and other application crash) if they can cause an LDAP server to become unavailable. NOTE: it is not clear whether this attack scenario is sufficient to include this item in CVE.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This is an old denial-of-service issue in nss_ldap, an LDAP name-service component. If LDAP becomes unavailable while affected systems query it, some applications such as crond may crash because SIGPIPE is mishandled. Sources indicate service disruption risk, not data theft or privilege escalation. Exposure is most likely on legacy Unix/Linux systems using nss_ldap before version 213 for LDAP-backed identity lookups, especially old Mandrake deployments. Modern systems are unlikely to be exposed unless they still run the vulnerable component. Treat this as a legacy hygiene issue unless vulnerable LDAP-dependent systems are still in production. Prioritize inventory and upgrade confirmation over emergency response because the sources do not establish active exploitation or high-impact compromise. Mitigation focus: Inventory systems using nss_ldap for name-service LDAP lookups.; Check whether nss_ldap is version 213 or later.; Review the Mandriva advisory for vendor-provided fixes..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2005-2377 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.