News for hackers. Stuff that matters.
Re:Glibc getaddrinfo stack-based buffer overflow by ptrincr on Tuesday February 16, 2016 @11:45AM (#11111114)
Redhat (RHEL5 unaffected) - https://access.redhat.com/security/cve/cve-2015-7547 - https://access.redhat.com/articles/2161461

RHEL6 - https://rhn.redhat.com/errata/RHSA-2016-0175.html - update to glibc-2.12-1.166.el6_7.7.x86_64.rpm

RHEL7 - https://rhn.redhat.com/errata/RHSA-2016-0176.html - update to glibc-2.17-106.el7_2.4.x86_64.rpm

Debian - https://security-tracker.debian.org/tracker/CVE-2015-7547 Use "aptitude show libc6" - needs to be 2.19-18+deb8u3 (jessie), 2.21-8 (sid)

Ubuntu - http://people.canonical.com/~ubuntu-security/cve/2015/CVE-20...

SUSE - https://www.suse.com/security/cve/CVE-2015-7547.html

Interesting to note this tip:

While it is only necessary to ensure that all processes are not using the old glibc anymore, it is recommended to reboot the machines after applying the security upgrade.

From - https://lists.debian.org/debian-security-announce/2016/msg00...

Therefore at the very least you will need to restart anything which depends on glibc. This should give you a list of packages:

  lsof | grep libc | awk '{print $1}' | sort | uniq
Re:Glibc getaddrinfo stack-based buffer overflow by tomputer on Tuesday February 16, 2016 @02:29PM (#11112468)
On Debian there is also the tool checkrestart available, it is part of the debian-goodies package. This might be useful if a reboot is (currently) not possible.

  apt-get install debian-goodies
Then you can run:

  checkrestart
And it will list services which require a restart. For example:

  service sudo restart
  service ssh restart
  service cron restart
  service ...
On Debian 8 (Jessie) i had to restart the systemd services as well:

  systemctl daemon-reexec 
  systemctl restart systemd-journald
  systemctl restart systemd-logind
Re:Glibc getaddrinfo stack-based buffer overflow by dne on Tuesday February 16, 2016 @02:52PM (#11112643)
Also see "needrestart", which automatically offers to do the above when upgraded packages have been installed: https://packages.debian.org/jessie/needrestart
Re:Glibc getaddrinfo stack-based buffer overflow by ptrincr on Tuesday February 16, 2016 @03:14PM (#11112809)
Thanks for this. Good to know.
Re:Glibc getaddrinfo stack-based buffer overflow by bits on Tuesday February 16, 2016 @12:34PM (#11111561)
Re:Glibc getaddrinfo stack-based buffer overflow by nisa on Tuesday February 16, 2016 @01:14PM (#11111874)
Just out of interest: How is this classified medium by Ubuntu? If someone manages to bypass ASLR this is a remote exploit on every SSH server running glibc out there? Or did I misunderstood something?

Out of the box SSH seems to use getaddrinfo:

    reverse mapping checking getaddrinfo for <host> [<ip>] failed - POSSIBLE BREAK-IN ATTEMPT!
Re:Glibc getaddrinfo stack-based buffer overflow by Racsoo on Tuesday February 16, 2016 @01:32PM (#11112035)
Refresh the page. It was just updated

> Priority: High

Re:Glibc getaddrinfo stack-based buffer overflow by idnar on Tuesday February 16, 2016 @02:14PM (#11112352)
Fairly sure the default changed to not doing this, although I'm not sure as of what release.
Re:Glibc getaddrinfo stack-based buffer overflow by collinmanderson on Tuesday February 16, 2016 @01:42PM (#11112097)
Ubuntu Trusty 14.04 user here. Am I correct that there's no patch out yet?
Re:Glibc getaddrinfo stack-based buffer overflow by ptrincr on Tuesday February 16, 2016 @01:57PM (#11112233)
Not that I can see
Re:Glibc getaddrinfo stack-based buffer overflow by collinmanderson on Tuesday February 16, 2016 @02:09PM (#11112318)
Thanks.
Re:Glibc getaddrinfo stack-based buffer overflow by ptrincr on Tuesday February 16, 2016 @02:20PM (#11112393)
Latest version I can see from here - https://launchpad.net/ubuntu/trusty/+source/eglibc

Is - https://launchpad.net/ubuntu/+source/eglibc/2.19-0ubuntu6.6

  apt-get update
  apt-cache show libc6
  *snip*
  Version: 2.19-0ubuntu6.6
This was released on 2015-02-25
Re:Glibc getaddrinfo stack-based buffer overflow by ptrincr on Tuesday February 16, 2016 @05:09PM (#11113512)
Re:Glibc getaddrinfo stack-based buffer overflow by collinmanderson on Tuesday February 16, 2016 @04:36PM (#11113299)
Update: It looks like the patch is finally out.
Re:Glibc getaddrinfo stack-based buffer overflow by atom_enger on Tuesday February 16, 2016 @04:47PM (#11113369)
What are you doing to pull this patch? I've apt-get updated and still am seeing Version: 2.19-0ubuntu6.6
Re:Glibc getaddrinfo stack-based buffer overflow by ptrincr on Tuesday February 16, 2016 @05:09PM (#11113509)
Does appear to be out - https://launchpad.net/ubuntu/+source/eglibc/2.19-0ubuntu6.7

apt-get update not seeing it at the moment though, guess its the mirror I'm using.

Edit - working now. I can see:

   Version: 2.19-0ubuntu6.7
Re:Glibc getaddrinfo stack-based buffer overflow by atom_enger on Tuesday February 16, 2016 @05:25PM (#11113612)
Yep I'm seeing it too. Thanks! Ubuntu just released this:

http://www.ubuntu.com/usn/usn-2900-1/

Re:Glibc getaddrinfo stack-based buffer overflow by chinathrow on Tuesday February 16, 2016 @03:19PM (#11112841)
It takes time - too much in my opinion in this case.
Re:Glibc getaddrinfo stack-based buffer overflow by orblivion on Wednesday February 17, 2016 @11:17AM (#11118840)
Does "DNE" mean there's no patch coming at all, or none yet? What about pending?

Also, why is all this important and useful information scattered all over the place? Ubuntu people, if you're reading, on this page: http://packages.ubuntu.com/trusty/libc6 I think you should have a history of updates to the package, and which security vulnerabilities it covers, with a link back to the above linked page. Looking at this page, looking at my system, looking at the news, I kind of have no idea what's going on.

I was going to complain that this people.canonical.com CVE page should also be linked from some sort of Ubuntu security bulletin, but I googled first and found that that's exactly where it's linked from. Still, I somehow reckon I would have never thought of that if not for this conversation. It should perhaps be linked from the packages page, though I'm not a UX guy, maybe that would just add confusion. But, this CVE page, with the domain "people.canonical.com", linking to launchpad pages, it doesn't look like it's made for users. You could make some improvements to make it more user friendly like the packages page. You could make it explicit: "Here's the packages you need to upgrade. here's the command to run to upgrade your whole system. Here's the command to upgrade just this package." As it stands, this doesn't even tell you what binary packages to get (libc6, I think? I'm still not even sure!), this just lists the source package (glibc). And, change "DNE" and "pending" to indicators that are more clear to us. Or, make a new page if this one is not meant for users.

For security stuff (not just Ubuntu by any means), all sorts of useful information is scattered all over the place. To name a few questions that I never determined clear answers to:

* What about this Android MMS attack that was supposed to be catastrophic and so easy to mount, that supposedly like half of all Android users are still vulnerable to? We've not heard of a single actual exploit in the wild. Where's some sort of official source downgrading its severity?

* If the libpng thing was such a fiasco, why were there no updates in Ubuntu for so long? Did it turn out not to be such a serious attack vector? Where's the documentation on that determination?

* For heartbleed: I recall having to poke around looking at the "built on" date for my openssl packages to see whether I was upgraded or not. That's not an acceptable state of affairs.

I'm not looking for answers to these particular questions now, I'm just wondering, why do we all have to rely on rumors and advice from random people in discussion forums for this stuff? There's a recent trend of understanding that improved UX can improve security (Signal, etc). Here's a good place to make some improvements, IMHO.

Sorry if I've come off as entitled here, it's just a source of irritation to me.

Re:Glibc getaddrinfo stack-based buffer overflow by ptrincr on Tuesday February 16, 2016 @01:35PM (#11112057)
Cheers!
Re:Glibc getaddrinfo stack-based buffer overflow by korethr on Tuesday February 16, 2016 @02:43PM (#11112585)
Re:Glibc getaddrinfo stack-based buffer overflow by pferde on Wednesday February 17, 2016 @06:17AM (#11117032)
Do I understand it correctly that Gentoo does not plan to push out a fix for this sooner than in 30 days?
Re:Glibc getaddrinfo stack-based buffer overflow by mark-wagner on Wednesday February 17, 2016 @02:58PM (#11120766)
No, they were talking about marking glibc-2.22 as stable i.e., removing the tilde from the arches in the KEYWORDS of the ebuild.

glibc-2.22-r2 was released at the same time as glibc-2.21-r2 and it contains the fix for this issue. The Changelog merely says "misc upstream fixes" but I verified the relevant changes are there.

The GLSA is https://security.gentoo.org/glsa/201602-02

Re:Glibc getaddrinfo stack-based buffer overflow by ptrincr on Tuesday February 16, 2016 @03:27PM (#11112893)
Thanks! Can't edit the original post now, else I would throw it in there and credit you.
Re:Glibc getaddrinfo stack-based buffer overflow by shaggy on Tuesday February 16, 2016 @11:58AM (#11111229)
Thanks for these. Has anyone seen a link from/for CentOS yes?
Re:Glibc getaddrinfo stack-based buffer overflow by ptrincr on Tuesday February 16, 2016 @12:17PM (#11111411)
Not sure about Centos, can't find anything. Looks like someone has submitted a patch for Fedora - https://bodhi.fedoraproject.org/updates/FEDORA-2016-0f9e9a34...

I'm guessing Ubuntu will add something here once they get a fixed released - http://www.ubuntu.com/usn/

Should be able to see centos updates here, once they are released, for files glibc-2.12* with a 2016 timestamp -

http://mirror.centos.org/centos/6/updates/x86_64/Packages/

http://mirror.centos.org/centos/7/updates/x86_64/Packages/

Re:Glibc getaddrinfo stack-based buffer overflow by alinspired on Tuesday February 16, 2016 @08:15PM (#11114444)
centos patch has been released at http://mirror.centos.org/centos/6/updates/ Note: it's likely not propagated to all mirrors yet