CVE-2011-4609: Medium severity GNU glibc vulnerability
It was reported that if a process that called glibc's svcrun() exceeded the limit of opened files for a longer period of time, that accept() in rendezvousrequest()/svcudprecv() would fail with the EMFILE error, which would lead to looping between poll(), accept(), and 'for' loops which would consume a lot of CPU time. This could lead to an unresponsive system that requires human intervention (service restart or system restart) to resolve.
Other sources
The svcrun function in the RPC implementation in glibc before 2.15 allows remote attackers to cause a denial of service (CPU consumption) via a large number of RPC connections.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2011-4609?
CVE-2011-4609 has a medium severity level due to the potential for denial-of-service conditions.
How do I fix CVE-2011-4609?
To fix CVE-2011-4609, ensure you upgrade to a patched version of glibc that addresses this vulnerability.
Which versions of glibc are affected by CVE-2011-4609?
CVE-2011-4609 affects multiple versions of glibc, including 2.0.0 through 2.1.9 and some versions up to 2.14.
What are the potential impacts of CVE-2011-4609?
The potential impacts of CVE-2011-4609 include application crashes and denial-of-service occurrences when file descriptor limits are exceeded.
Is CVE-2011-4609 still a concern for modern systems?
CVE-2011-4609 is less of a concern for modern systems that run updated versions of glibc, but it should still be monitored.