CVE-2024-33600: nscd: Null pointer crashes after notfound response
After a failed cache insertion, addgetnetgrentX tries to send the non-existing response after the not-found header.
In addinnetgrX, addgetnetgrentX may have produced a NULL result, indicating a not-found status, but this is not handled in the subsequent code that prepares the record that will be sent out to the client.
Reference: https://sourceware.org/bugzilla/showbug.cgi?id=31678
Other sources
glibc is vulnerable to a denial of service, caused by a NULL pointer dereference when the Name Service Cache Daemon's (nscd) cache fails to add a not-found netgroup response to the cache. A remote attacker could exploit this vulnerability to cause a denial of service.
— IBM
nscd: Null pointer crashes after notfound response
— Microsoft
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-33600?
CVE-2024-33600 is considered to have a moderate severity due to its potential impact on application stability.
What products are affected by CVE-2024-33600?
CVE-2024-33600 affects IBM QRadar Network Packet Capture version 7.5.0 and certain versions of the glibc package on Debian.
How do I fix CVE-2024-33600?
To mitigate CVE-2024-33600, upgrade the affected software to a version that addresses the vulnerability.
What are the symptoms of CVE-2024-33600?
Symptoms may include application failures or unexpected behavior when handling cache insertions in affected systems.
Is there a workaround for CVE-2024-33600?
Currently, there are no known workarounds for CVE-2024-33600, and upgrading is advised to eliminate the risk.