CVE-2024-33601: nscd: netgroup cache may terminate daemon on memory allocation failure
nscd: netgroup cache may terminate daemon on memory allocation failure
The Name Service Cache Daemon's (nscd) netgroup cache uses xmalloc or
xrealloc and these functions may terminate the process due to a memory
allocation failure resulting in a denial of service to the clients. The
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
CVE-2024-33601 is a denial-of-service risk in glibc's nscd netgroup cache. If memory allocation fails, nscd may terminate, disrupting clients that depend on it for name service caching. The source bundle says the issue is only in the nscd binary and was introduced with the netgroup cache in glibc 2.15.
Executive priority
Treat this as a high-priority availability issue where nscd supports authentication, identity lookup, or production service dependencies. It is not currently evidenced as exploited in the provided sources, but outages in shared name-service infrastructure can have broad operational impact.
Technical view
The nscd netgroup cache uses xmalloc/xrealloc, which can terminate the daemon on allocation failure. The weakness is classified as CWE-617 and scored CVSS 7.3. Available evidence identifies nscd as the vulnerable component, not general glibc runtime behavior across all binaries.
Likely exposure
Exposure is most likely on Linux or appliance systems using glibc nscd with netgroup caching. Systems without the nscd binary, without nscd running, or using unaffected vendor packages are less likely exposed. Exact affected downstream versions require vendor advisory confirmation.
Exploitation context
The bundle does not cite CISA KEV listing or active exploitation. The practical impact is service disruption to clients relying on nscd. No source in the bundle provides exploit maturity, public exploit evidence, or operational attack details.
Researcher notes
Evidence is strongest for the root cause and component boundary: nscd netgroup cache only. The source bundle does not provide fixed upstream commit details, exact downstream version ranges, or exploit observations. Validate through vendor package advisories rather than assuming all glibc deployments are affected.
Mitigation direction
Apply vendor-provided glibc or nscd updates where available.
Check Debian, NetApp, Siemens, and OS vendor advisories for product-specific guidance.
Disable nscd netgroup caching if not required and supported by vendor guidance.
Prioritize internet-adjacent or authentication-dependent systems using nscd.
Monitor nscd restarts or crashes until patched.
Validation and detection
Inventory systems for glibc packages and the nscd binary.
Confirm whether nscd is installed, enabled, and actively running.
Check whether netgroup caching is configured or used.
Map appliance and distribution versions to vendor advisories.
Verify deployed package versions include the vendor fix.
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-617: 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-617 · source CWE mapping
Reachable Assertion
Reachable Assertion represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.