getaddrinfo bug in glibc (CVE-2015-7547) questions?
Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
getaddrinfo bug in glibc (CVE-2015-7547) questions?
Hello
I just about the bug. As far as I understand it's this:
If you do reverse DNS lookups, and the result comes from an evil DNS server, bad things can happen. (if length > 2048) Now people are patching and rebooting.
My question is if it's only the the DNS servers need fixing. If I boot with a old live cd and reverse lookup some nasty IP address, what will happen?
It's not specifically DNS that needs patching (we're talking about an adversary exploiting what is "allowed" reply size-wise within the DNS RFCs) but any machine using an affected Glibc version that uses AF_UNSPEC-type lookups and uses unfiltered replies (doesn't say anything about the type) or receives unfiltered lookup results from other systems.
Ok. We have a DNS server using BIND, and as far as I understand, it's doing the actual resolving of reverse DNS lookups. Or am I incorrect?
The DNS server has been patched, but I was thinking it could maybe do the filtering of replies? A live CD gets the DNS from DHCP, so I was wondering if it was a way to protect them against this.
Ok. We have a DNS server using BIND, and as far as I understand, it's doing the actual resolving of reverse DNS lookups. Or am I incorrect?
A Domain Name server can be configured in many way: authoritative name server, slave, caching name server, forwarder. Then there's devices running Linux who have a resolver stub as libraries like Glibc provide them (uClibc, dietlibc and musl seem unaffected AFAIK). These are separate things ..
Quote:
Originally Posted by Guttorm
The DNS server has been patched, but I was thinking it could maybe do the filtering of replies? A live CD gets the DNS from DHCP, so I was wondering if it was a way to protect them against this.
.. so while you may patch DNS as part of your mitigation strategy this only combats symptoms but does not solve the cause IMHO.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
