CVE-2024-33600: nscd: Null pointer crashes after notfound response
nscd: Null pointer crashes after notfound response
If the Name Service Cache Daemon's (nscd) cache fails to add a not-found
netgroup response to the cache, the client request can result in a null
pointer dereference. This flaw was introduced in glibc 2.15 when the
cache was added to nscd.
This vulnerability is only present in the nscd binary.
Security readout for executives and security teams
Plain-English summary
This is a denial-of-service issue in glibc's Name Service Cache Daemon, not the whole glibc library surface. A crafted or triggering client request after a failed not-found netgroup cache insert can crash nscd through a null pointer dereference. The business impact is service disruption on systems that depend on nscd for name-service lookups.
Executive priority
Treat as a moderate availability risk. It is not described as data theft or privilege escalation, but a crash in name-service caching can disrupt dependent infrastructure. Prioritize patch verification on Linux servers and appliances where nscd is active.
Technical view
CVE-2024-33600 is a CWE-476 null pointer dereference in the nscd binary. The flaw follows failure to cache a not-found netgroup response, after which a client request can crash the daemon. The CVSS 3.1 score is 5.9, with network attack vector, high complexity, no privileges, no user interaction, and availability-only impact.
Likely exposure
Exposure is limited to systems that include and run the vulnerable nscd binary. The bundle says the issue was introduced in glibc 2.15 and is only present in nscd. Product-specific exposure should be confirmed through OS, appliance, and vendor advisories.
Exploitation context
The provided sources do not show CISA KEV listing or active exploitation. Exploitation appears constrained by high attack complexity and an availability-only outcome: crashing nscd. The bundle does not provide enough evidence to claim public weaponization or broad real-world exploitation.
Researcher notes
The key boundary is that the vulnerability is only in nscd. The affected-version evidence in the bundle is sparse: it states introduction in glibc 2.15 but does not enumerate every vulnerable downstream build. Use vendor advisories and package changelogs for exact exposure and fixed versions.
Mitigation direction
Check OS and appliance vendor advisories for affected glibc or nscd packages.
Apply vendor-provided updates where your platform lists this CVE as affected.
Disable nscd only if vendor guidance and operational dependencies allow it.
Prioritize systems where nscd supports authentication, directory, or netgroup-dependent workflows.
Validation and detection
Inventory hosts and appliances running the nscd binary or service.
Identify deployed glibc package versions and vendor backport status.
Check whether netgroup lookups are used in production name-service paths.
Map affected assets to Debian, NetApp, Siemens, or other relevant advisories.
Monitor for unexpected nscd crashes or availability symptoms.
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.
cwe · low confidence lookup
CWE-476: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-476 · source CWE mapping
NULL Pointer Dereference
NULL Pointer Dereference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.