Memory corruption via out-of-buffer NSS strings
Published May 6, 2024 · Updated Jul 14, 2026
Memory corruption in glibc 2.15 through 2.39 allows local users to corrupt nscd memory through crafted netgroup lookups. The addgetnetgrentX buffer-resizing path assumes every NSS callback string points into its supplied buffer, so an external pointer becomes invalid when that buffer is resized. Reachability requires the nscd binary, netgroup caching, and an NSS callback that returns an out-of-buffer string; Siemens embeds the affected code in the additional GNU/Linux subsystem of listed controller firmware.
Summary
What happened
Memory corruption in glibc 2.15 through 2.39 allows local users to corrupt nscd memory through crafted netgroup lookups. The addgetnetgrentX buffer-resizing path assumes every NSS callback string points into its supplied buffer, so an external pointer becomes invalid when that buffer is resized. Reachability requires the nscd binary, netgroup caching, and an NSS callback that returns an out-of-buffer string; Siemens embeds the affected code in the additional GNU/Linux subsystem of listed controller firmware.
The record
- CVE
- CVE-2024-33602
- Published
- May 6, 2024
- Updated
- Jul 14, 2026
- Vendor
- The GnuPG Project
- Product
- glibc
- Classifications
- CWE-466, CAPEC-129
- Attack vector
- local
- 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?
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