dbcve.org
Debian LinuxOperating system · Debian

CVE-2024-33601

HIGH · 7.3 CVSS v3.1 Published 2024-05-06
Fix available
A fix is available. Upgrade to 2.40 or later.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Name Service Cache Daemon (nscd) netgroup cache uses xmalloc and xrealloc memory allocation functions that terminate the process on allocation failure, causing denial of service to all clients relying on nscd. This flaw was introduced in glibc 2.15 when the netgroup cache was added and only affects the nscd binary.

MitigationUpdate glibc to a patched version that handles memory allocation failures gracefully in nscd's netgroup cache, or disable netgroup caching in nscd configuration if an update is not immediately feasible.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Debian LinuxOperating system
Affected:= 10.0
GlibcFramework / library
Affected:>= 2.15, < 2.40
H300s FirmwareOperating system
Affected:all versions
H500s FirmwareOperating system
Affected:all versions
H700s FirmwareOperating system
Affected:all versions
H410s FirmwareOperating system
Affected:all versions
H410c FirmwareOperating system
Affected:all versions
H610c FirmwareOperating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check glibc version
    Run 'ldd --version' or check /lib/libc.so.6' to determine the installed glibc version
    Affected if glibc version is 2.15 or higher but lower than 2.40
  2. Verify nscd is installed
    Check for the nscd binary with 'which nscd' or 'dpkg -l | grep nscd' (Debian)
    Affected if nscd package or binary is present on the system
  3. Inspect nscd configuration for netgroup caching
    Examine /etc/nscd.conf for 'enable-cache netgroup' setting; if present and set to 'yes', netgroup caching is enabled
    Affected if netgroup caching is enabled in nscd.conf (enable-cache netgroup yes)
  4. Confirm nscd service is running
    Check service status with 'systemctl status nscd' or 'service nscd status'
    Affected if nscd daemon is actively running

System is affected if glibc 2.15-2.39 is installed, nscd is running, and netgroup caching is enabled in nscd configuration (or for NetApp devices, any H300s/H500s/H700s/H410s/H410c/H610c/H610s firmware version).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.40 or later
Fixed in 2.40
Interim mitigation

Update glibc to a patched version that handles memory allocation failures gracefully in nscd's netgroup cache, or disable netgroup caching in nscd configuration if an update is not immediately feasible.

Recommended fix High confidence

glibc 2.40 or later

  1. 1. Identify the current glibc version by running: rpm -q glibc or dpkg -l libc6
  2. 2. Upgrade glibc to version 2.40 or later through your operating system's package manager (e.g., apt update && apt install libc6 for Debian, or yum update glibc for RHEL-based systems)
  3. 3. After glibc upgrade, restart the nscd service: systemctl restart nscd or service nscd restart
  4. 4. Verify the glibc version has been updated: rpm -q glibc or dpkg -l libc6 | grep version
  5. 5. Confirm nscd is running properly: systemctl status nscd
Caveat Major glibc upgrades can cause compatibility issues with older binaries or libraries linked against the previous glibc version; test in staging first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Debian Linux Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-33601 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-33601 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data