Re:Re: CVE-2014-6271 – remote code execution through bash
by mrmondo on Friday September 26, 2014 @12:42AM
(#8371360)
Debian patched this 8 hours ago, Redhat issued a patch about 3 hours ago, I believe Centos is still vulnerable, Ubuntu 14.10 isn't patched yet, Ubuntu 14.04 was patched about 3 hours ago.
[ Parent
| on HN ]
Re:Re: CVE-2014-6271 – remote code execution through bash
by psgbg on Friday September 26, 2014 @01:03AM
(#8371411)
I'm using debian jessie (testing) i386, and I had to download bash myself (from sid) because my up-to-date system was affected but the first patch was available for sid (unstable) and wheezy (stable) and not in jessie.
So I don't know if every architecture, and version is updated with the same speed.
Re:Re: CVE-2014-6271 – remote code execution through bash
by mrmondo on Friday September 26, 2014 @01:26AM
(#8371476)
Jessie isn't released / stable and doesn't receive security patches until it is. It's called testing for a reason.
Re:Re: CVE-2014-6271 – remote code execution through bash
by bigbugbag on Friday September 26, 2014 @04:12AM
(#8371812)
debian testing do receive security patches, but it is not a priority so they may not get there in a timely manner.
Re:Re: CVE-2014-6271 – remote code execution through bash
by psgbg on Friday September 26, 2014 @09:18AM
(#8372519)
Yeah. I'm aware that stable and old stable need to be patched first, I was just surprised by how much time it took considering the kind of risk (and being beaten by sid, the kid whom always breaks his toys).
Re:Re: CVE-2014-6271 – remote code execution through bash
by ScottBurson on Friday September 26, 2014 @01:31AM
(#8371483)
I did 'yum update bash' on my Centos 5.8 Linode a couple of hours ago, and it updated to 3.2-33 and is apparently no longer vulnerable, according to the one-line test I have been using:
X="() { :;} ; echo busted" /bin/sh -c "echo stuff"
Re:Re: CVE-2014-6271 – remote code execution through bash
by gklyne on Friday September 26, 2014 @03:18AM
(#8371689)
That test doesn't detect the vulnerability - needs to mention /bin/bash not /bin/sh
Re:Re: CVE-2014-6271 – remote code execution through bash
by bigbugbag on Friday September 26, 2014 @04:09AM
(#8371807)
Well, maybe you should look at your /bin/sh
ls -l /bin/sh
lrwxrwxrwx 1 root root 4 Sep 24 08:07 /bin/sh -> bash
Re:Re: CVE-2014-6271 – remote code execution through bash
by makomk on Friday September 26, 2014 @05:16AM
(#8371955)
I think /bin/sh is /bin/bash on CentOS and RedHat, but Debian, Ubuntu and probably other distros use dash as /bin/sh instead which was never vulnerable.