Glibc getaddrinfo stack-based buffer overflow
&gt; &quot;The glibc DNS client side resolver is vulnerable to a stack-based buffer overflow when the getaddrinfo() library function is used. Software using this function may be exploited with attacker-controlled domain names, attacker-controlled DNS servers, or through a man-in-the-middle attack.&quot;<p>&gt; &quot;The vectors to trigger this buffer overflow are very common and can include ssh, sudo, and curl. We are confident that the exploitation vectors are diverse and widespread; we have not attempted to enumerate these vectors further.&quot;<p>&gt; &quot;Remote code execution is possible, but not straightforward. It requires bypassing the security mitigations present on the system, such as ASLR.&quot;<p>It is time for the bimonthly Internet security meltdown. Again. When they say that &quot;exploitation vectors are diverse and widespread&quot;, they really mean it. Patch ASAP. This is a race; it is only a matter of time before criminals start automatically and systematically scanning every server on the internet for this, and you really really want to be patched before that happens.<p>Thinking a bit more long term, it&#x27;s pretty clear at this point that we need to expunge all C language networking code from the world, replacing it with Rust or pretty much anything else. That&#x27;s not sufficient by itself, but it is necessary, or else the periodic Internet security meltdowns won&#x27;t ever stop.