Daemon compromise via undersized cache-failure buffer
Published May 6, 2024 · Updated Jul 14, 2026
Stack-based buffer overflow in glibc nscd 2.15 through 2.39 allows remote attackers to corrupt the daemon via netgroup requests. When cache allocation fails, addinnetgrX uses a fixed-size stack object but appends the request key; the patch allocates space for both. Exploitation requires exhausting nscd's cache before the request; only the nscd binary is affected, and the overwrite can crash or compromise the daemon.
Summary
What happened
Stack-based buffer overflow in glibc nscd 2.15 through 2.39 allows remote attackers to corrupt the daemon via netgroup requests. When cache allocation fails, addinnetgrX uses a fixed-size stack object but appends the request key; the patch allocates space for both. Exploitation requires exhausting nscd's cache before the request; only the nscd binary is affected, and the overwrite can crash or compromise the daemon.
The record
- CVE
- CVE-2024-33599
- Published
- May 6, 2024
- Updated
- Jul 14, 2026
- Vendor
- The GnuPG Project
- Product
- glibc
- Classifications
- CWE-121, CAPEC-100, T1499, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 6, 2024CVE publishedPublication date reported by the CVE source.
- Jul 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.15 <2.40
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo