News for hackers. Stuff that matters.
Re:Glibc getaddrinfo stack-based buffer overflow by dalore on Tuesday February 16, 2016 @10:22AM (#11110377)
But this is hard for them to 'scan' for. As they need to get vulnerable systems to query their dns server.

But it's not hard to get a system to do a dns query. Sometimes even connecting to it will cause your ip to appear in the logs which are then sometimes reversed ip. But one could easily just create a webpage with img.src pointing to the host.

DNS being distributed could halt the attack upstream by patching their servers to stop the queries so any vulnerable clients won't get compromised even if they make the query.

Re:Glibc getaddrinfo stack-based buffer overflow by Xylakant on Tuesday February 16, 2016 @11:23AM (#11110895)
> DNS being distributed could halt the attack upstream by patching their servers to stop the queries so any vulnerable clients won't get compromised even if they make the query.

Anybody connecting to a public network that pushes network settings may still be affected. For wifis with a capture portal (hotel wifi etc) you usually have to use the network-provided dns server.

Re:Glibc getaddrinfo stack-based buffer overflow by caf on Tuesday February 16, 2016 @08:22PM (#11114475)
I don't think a reverse query will tickle this bug, because this bug requires simultaneous A and AAAA lookups to be triggered whereas a reverse query uses a single PTR lookup.