dbcve.org
Debian LinuxOperating system · Debian

CVE-2024-33602

HIGH · 7.4 CVSS v3.1 Published 2024-05-06
Fix available
A fix is available. Upgrade to 2.40 or later.
See remediation →
79/100
Remediation priority · High
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 assumes NSS callback uses in-buffer strings The Name Service Cache Daemon's (nscd) netgroup cache can corrupt memory when the NSS callback does not store all strings in the provided buffer. 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 · moderate confidence

Memory corruption vulnerability in nscd's netgroup cache where the cache incorrectly assumes NSS callbacks always store strings in the provided buffer. When callbacks store strings elsewhere, memory corruption occurs. Only affects the nscd binary, introduced in glibc 2.15.

MitigationUpdate glibc/nscd to a patched version that properly handles NSS callbacks that do not store strings in the provided buffer, or disable netgroup caching if updates are not immediately available.

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
Element SoftwareApplication
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
Local
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/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 is running
    Run `ps aux | grep nscd` or `systemctl status nscd` to see if the nscd daemon is active on the system
    Affected if nscd is running and serving requests
  2. Check glibc version
    Run `ldd --version` or check the libc library file directly (e.g., `/lib/x86_64-linux-gnu/libc.so.6`) to obtain the installed glibc version
    Affected if glibc version is 2.15 or higher but lower than 2.40
  3. Verify netgroup caching is enabled
    Inspect the nscd configuration file at `/etc/nscd.conf` and look for a line containing `enable-cache netgroup yes`
    Affected if netgroup caching is explicitly enabled (set to yes) in the nscd configuration
  4. Confirm nscd binary in use
    Verify the nscd binary path with `which nscd` or `rpm -q nscd`/`dpkg -l nscd` to confirm the glibc-linked nscd binary is installed
    Affected if nscd binary from the vulnerable glibc version is installed

You are affected if nscd is running with a glibc version between 2.15 and 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/nscd to a patched version that properly handles NSS callbacks that do not store strings in the provided buffer, or disable netgroup caching if updates are not immediately available.

Recommended fix High confidence

glibc 2.40 or later

  1. 1. Identify all systems running glibc versions 2.15 through 2.39 that have nscd installed
  2. 2. For Debian Linux 10.0 systems: update the glibc package to the latest available version in Debian's security repositories
  3. 3. For systems with glibc: upgrade glibc to version 2.40 or later which contains the fix for the netgroup cache memory corruption
  4. 4. After upgrading glibc, restart the nscd service to ensure the patched version is loaded: systemctl restart nscd or service nscd restart
  5. 5. Verify the glibc version after upgrade: ldd --version or rpm -q glibc
  6. 6. For Siemens H-series firmware and Element Software products: contact Siemens for vendor-specific patches as these may require firmware updates
Caveat Upgrading glibc is a core library upgrade and may require system reboot. Test thoroughly in non-production environment first, as glibc upgrades can affect system compatibility.

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
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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