8.1

CVSS Score

3.1

-

CVSS Score

Basic Information

Concerned about an active attack path?

Talk to our security experts and see Miggo in action.

Miggo Vulnerability Database

→

CVE-2024-33599

CVE-2024-33599: nscd: Stack-based buffer overflow in netgroup cache If the Name Service Cache Daemon's (nscd)...

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.

(GitHub Advisory)

Miggo Vulnerability Database

→

CVE-2024-33599

CVE-2024-33599:

8.1

CVSS Score

3.1

-

CVSS Score

Basic Information

Is this CVE running in your environment?

Easily map the attack path and prioritize which CVEs are a threat to your organization

Validate Exposure

Technical Details

Vulnerability Intelligence
Miggo AI

Root Cause Analysis

The vulnerability description and the commit patch clearly point to a stack-based buffer overflow in the addinnetgrX function within nscd/netgroupcache.c. The patch modifies how memory is allocated when a cache allocation fails, specifically replacing a fixed-size stack buffer with alloca. This change directly addresses the overflow condition. The commit message explicitly mentions CVE-2024-33599 and the nature of the bug.

Initially, I tried to fetch content from sourceware.org but it was protected. I then used Google to search for the CVE and found a link to an Ubuntu security page which contained the commit hash 87801a8fd06db1d654eea3e4f7626ff476a9bdaa. I then used this hash to fetch commit information from a glibc mirror on GitHub (bminor/glibc). The commit details directly implicated the addinnetgrX function and provided the patch diff showing the vulnerable code and its fix. The vulnerability occurs when mempool_alloc fails and the code falls back to a fixed-size stack buffer dataset_mem, which could be overflowed if req->key_len is too large. The fix involves using alloca instead, with a comment indicating that key_len is checked elsewhere, making alloca safe in this context for the patched version, but highlighting the original flaw with the fixed-size buffer on the stack when the primary allocation failed.

Vulnerable functions

Only Mi**o us*rs **n s** t*is s**tion

Vulnerability Intelligence
Miggo AI

Unlock WAF rules for this CVE

Generate vendor-ready rules for the observed attack patterns, plus reasoning and safe deployment guidance

Get WAF rules

WAF Protection Rules

WAF Rule

W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.

Reasoning

*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.