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

> A stack-based buffer overflow in the nscd netgroup cache allows attackers to execute arbitrary code or cause denial of service.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 May 2024
- **Updated:** 15 Oct 2026
- **Also known as:** AZL-40288, AZL-40310, BELL-CVE-2024-33599, CLSA-2024-1718900760, CLSA-2024-1718901417, CLSA-2024-1718973147, CLSA-2024-1719920973, CLSA-2024-1723482999, DEBIAN-CVE-2024-33599, GHSA-9gvm-vcgf-x5xw, MINI-v8qg-cm59-fh55, MINI-xgpj-hqhx-gr5r, UBUNTU-CVE-2024-33599, openSUSE-SU-2024:13935-1

## What is CVE-2024-33599?

CVE-2024-33599 is a high-severity memory corruption vulnerability in Debian Debian Linux, published on 6 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2024-33599?

It affects 8 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `glibc` | openSUSE:Tumbleweed | All versions | 2.39-6.1 |

Products: Debian Debian Linux, Gnu Glibc, Netapp H300s Firmware, Netapp H410c Firmware, Netapp H410s Firmware, Netapp H500s Firmware, Netapp H700s Firmware, Netapp Hci Bootstrap Os.

## How do I fix CVE-2024-33599?

Apply the vendor's patch.

## Is CVE-2024-33599 being exploited?

There is no known exploitation of CVE-2024-33599 in the wild and no public exploit code.

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-33599 and fix it if it is affected.

What it is: CVE-2024-33599 is a high-severity memory corruption vulnerability in Debian Debian Linux, published on 6 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-33599 in the wild and no public exploit code.

Affected product: Debian Debian Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-33599/ (Markdown: https://insights.sbomify.com/CVE-2024-33599/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-33599
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-33599
- OSV: https://osv.dev/vulnerability/CVE-2024-33599

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-33599/
Summaries are generated and may contain mistakes; the official description above is the record.