LiveActive security incident?Get immediate response
CVE Record

CVE-2024-33599: nscd: Stack-based buffer overflow in netgroup cache

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.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2024-33599 is a high-severity flaw in glibc's Name Service Cache Daemon. If nscd's fixed-size cache is exhausted, a later netgroup lookup can trigger a stack buffer overflow. Business risk depends on whether nscd is installed and enabled.

Executive priority

Treat as a high-priority Linux infrastructure issue where nscd is used. It is not automatically enterprise-wide; scope first, then patch or disable unnecessary nscd service promptly.

Technical view

The issue is CWE-121 in the nscd netgroup cache. Source data says repeated client requests can exhaust a fixed-size cache, after which a netgroup request may cause stack-based overflow. CVSS 3.1 is 8.1 with high impact but high attack complexity.

Likely exposure

Exposure is limited to systems using the nscd binary from affected glibc packaging. The bundle states the flaw was introduced in glibc 2.15, but does not enumerate every affected downstream version.

Exploitation context

The provided data does not show CISA KEV listing or confirmed active exploitation. The CVSS vector indicates unauthenticated, no-user-interaction attack potential, but with high attack complexity.

Researcher notes

Evidence supports an nscd-only stack overflow tied to netgroup cache exhaustion. Public bundle does not provide exploit details, active exploitation evidence, or a complete affected-version matrix, so validation should rely on vendor package advisories.

Mitigation direction

  • Check vendor advisories for updated glibc or nscd packages.
  • Prioritize systems where nscd is installed, enabled, and reachable by clients.
  • If vendor guidance permits, disable nscd where it is unnecessary.
  • Apply Debian, Siemens, NetApp, or platform-specific fixes when available.
  • Track sourceware GLIBC-SA-2024-0005 for authoritative glibc guidance.

Validation and detection

  • Inventory hosts with nscd installed or running.
  • Identify glibc package versions and vendor backport status.
  • Check whether netgroup caching is used in affected environments.
  • Review vendor advisories for product-specific applicability.
  • Confirm patched packages are deployed after remediation.
Prepared
Confidence
medium
Sources
6

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-121: 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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-33599 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.1 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

1CVSS vectors
3Timeline events
3ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
8.1CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H2.25.9CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

8.1High
CVSS 3.1 vector shape for CVE-2024-33599Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
CVECVE Program Container
siemens-SADPADP container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
The GNU C Libraryglibc2.15unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-121 · source CWE mapping

Stack-based Buffer Overflow

Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.