News for hackers. Stuff that matters.
Re:Glibc getaddrinfo stack-based buffer overflow by weinzierl on Tuesday February 16, 2016 @12:09PM (#11111324)

    > The vectors to trigger this buffer overflow are very common and can include ssh, sudo, and curl.
Why are browsers missing in the list? Don't they use getaddrinfo() as well?
Re:Glibc getaddrinfo stack-based buffer overflow by msbarnett on Tuesday February 16, 2016 @12:15PM (#11111384)
Literally the next sentence:

> We are confident that the exploitation vectors are diverse and widespread; we have not attempted to enumerate these vectors further.

Re:Glibc getaddrinfo stack-based buffer overflow by weinzierl on Tuesday February 16, 2016 @04:00PM (#11113095)
I read that, I just found the examples strange. Browsers are incredibly important for an incredible number of people while curl is not.
Re:Glibc getaddrinfo stack-based buffer overflow by vdfs on Tuesday February 16, 2016 @02:37PM (#11112527)
I tried the exploit server, Firefox crashed right after changing the DNS name server.
Re:Glibc getaddrinfo stack-based buffer overflow by muraiki on Tuesday February 16, 2016 @03:30PM (#11112910)
That is not awesome :(
Re:Glibc getaddrinfo stack-based buffer overflow by jimrandomh on Tuesday February 16, 2016 @12:33PM (#11111543)
I'm not sure, but I suspect that major browsers may have their own DNS client implementations, or be calling getaddrinfo from within sandboxed contexts.
Re:Glibc getaddrinfo stack-based buffer overflow by collinmanderson on Tuesday February 16, 2016 @01:57PM (#11112229)
Chrome uses a custom DNS client implementation.

https://plus.google.com/+WilliamChanPanda/posts/FKot8mghkok

"The problem is that Chromium is issuing too many DNS queries in a short period of time, which may overload upstream devices (typically cheap NAT routers) ... which will then ignore DNS queries for a period of time."