Skip to content
Noroxi
CVE-2007-5794· NVD / CVE Program· CNA redhat

Race condition in nss_ldap, when used in applications that are linked against the pthread library and fork after a call to nss_ldap, might s

Race condition in nss_ldap, when used in applications that are linked against the pthread library and fork after a call to nss_ldap, might send user data to the wrong process because of improper handling of the LDAP connection. NOTE: this issue was originally reported for Dovecot with the wrong mailboxes being returned, but other applications might also be affected.

MediumCVSS 4.3 · v2.0—No exploit Fix available
Published
Nov 13, 2007
Updated
Jun 16, 2026
EPSS
1.2% · 66th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

17

Monitor

Low priority for now.

CVSS
17 / 40 · 4.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.2%

Affected systems

VendorProduct
nss ldapnss ldap

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • nss ldap nss ldapall versions

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:11libnss-ldapbefore 256-1256-1
Debian:3.1libnss-ldapbefore 238-1sarge1238-1sarge1
Debian:4.0libnss-ldapbefore 251-7.5etch1251-7.5etch1
Red Hat:enterprise_linux:4::asnss_ldapbefore 0:253-5.el40:253-5.el4
Red Hat:enterprise_linux:4::asnss_ldap-debuginfobefore 0:253-5.el40:253-5.el4
Red Hat:enterprise_linux:5::clientnss_ldapbefore 0:253-12.el50:253-12.el5
Red Hat:enterprise_linux:5::clientnss_ldap-debuginfobefore 0:253-12.el50:253-12.el5

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:libnss-ldap256-1 · Debian:11Package registry (OSV)
red hat:nss_ldap0:253-12.el5 · Red Hat:enterprise_linux:5::clientPackage registry (OSV)
red hat:nss_ldap-debuginfo0:253-12.el5 · Red Hat:enterprise_linux:5::clientPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

    If successful

    Confidentiality
    P · data can be read
    Integrity
    none
    Availability
    none
    Attack complexity
    M
    Confidentiality impact
    P
    Integrity impact
    None
    Availability impact
    None

    CVSS vector

    AV:N/AC:M/Au:N/C:P/I:N/A:N

    nvd-primary

    Attack context

    MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

    Noroxi analysis

    No Noroxi analysis for this record yet

    We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

    We use this product, ask for help

    Change log

    1. Fix✗ → ✓

    For records you follow, these changes also arrive as notifications. →

    References

    All records