dbcve.org
Debian LinuxOperating system · Debian

CVE-2024-33599

HIGH · 8.1 CVSS v3.1 Published 2024-05-06
Fix available
A fix is available. Upgrade to 2.40 or later.
See remediation →
90/100
Remediation priority · Urgent
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: Stack-based buffer overflow in netgroup cache If the Name Service Cache Daemon's (nscd) fixed size cache is exhausted by client requests then a subsequent client request for netgroup data may result in a stack-based buffer overflow. This 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 · moderate confidence

A stack-based buffer overflow vulnerability exists in the Name Service Cache Daemon (nscd) when handling netgroup cache data. When the fixed-size netgroup cache is exhausted by client requests, a subsequent client request for netgroup data can overflow a stack-based buffer. This flaw was introduced in glibc 2.15 when the cache feature was added to nscd and only affects the nscd binary.

MitigationUpdate glibc to a version that includes the security patch for this vulnerability, or if nscd is not required, disable or remove the nscd service to eliminate the attack surface.

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
Hci Bootstrap OsOperating 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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Verify nscd binary is present
    Run 'which nscd' or check for /usr/sbin/nscd or /sbin/nscd existence
    Affected if nscd binary exists on the system
  2. Verify nscd service is running
    Run 'systemctl status nscd' (systemd) or 'service nscd status' (SysV) or check process list with 'ps aux | grep nscd'
    Affected if nscd service is actively running
  3. Check glibc version
    Run 'ldd --version' to display glibc version, or check /lib/libc.so.6 with 'ldd -ld libc.so.6 2>&1 | grep version'
    Affected if glibc version is 2.15 or higher but below 2.40
  4. Check if netgroup caching is enabled in nscd
    Examine /etc/nscd.conf for lines containing 'enable-cache netgroup' or look for netgroup database entries in the configuration
    Affected if netgroup caching is enabled in the nscd configuration file

A system is affected if nscd is running with a vulnerable glibc version (2.15 through 2.39) and netgroup caching is enabled in the nscd configuration.

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 version that includes the security patch for this vulnerability, or if nscd is not required, disable or remove the nscd service to eliminate the attack surface.

Recommended fix High confidence

glibc 2.40 or later

  1. Identify the glibc version currently installed using: `ldd --version` or `rpm -q glibc` / `dpkg -l libc6`
  2. For Debian 10.0 systems: Run `apt-get update && apt-get install libc6` to upgrade glibc to version 2.40 or later
  3. For other Linux distributions: Update the system package manager (e.g., `yum update glibc` or `dnf update glibc`) to obtain glibc >= 2.40
  4. Restart any services that depend on nscd after the upgrade
  5. Verify the nscd binary has been updated by checking the glibc version again
Caveat Upgrading glibc is a major operation that may affect linked applications; ensure compatibility testing is performed in a non-production environment first

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

Fix this in Debian Linux Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-33599 — 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-33599 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