4 ms·
I'm double-mistaken. This is a month old. So, back to the original message. If you are just hearing about it, you really need to update your security news feeds
by jerf 12y ago
I'm double-mistaken. This is a month old. So, back to the original message. If you are just hearing about it, you really need to update your security news feeds, if you are responsible for any systems that have bash on them.
- sillysaurus3 12y agoif you have any interest in this matter but are only now hearing about it, it is vital that you improve your connection to security news. What would you suggest?
- dmix 12y agoFollow infosec people on Twitter.
- sillysaurus3 12y agoWho would you suggest?
- Phlarp 12y ago@erratarob, @thegrugq, @mattblaze, @matthew_d_green, @swiftonsecurity
- dmix 12y agoThere are plenty. Here are a few off the top of my head: https://twitter.com/ErrataRob https://twitter.com/ErrataRob https://twitter.com/mikko https://twitter.com/mikko https://twitter.com/thegrugq https://twitter.com/thegrugq https://twitter.com/r_netsec https://twitter.com/r_netsec https://twitter.com/0xabad1dea https://twitter.com/0xabad1dea https://twitter.com/agl__ https://twitter.com/agl__ https://twitter.com/dinodaizovi https://twitter.com/dinodaizovi
- sprkyco 12y agohttp://seclists.org/ http://seclists.org/ is another great resource.
- schrodingersCat 12y agoThe subreddits r/netsec and r/crypto can be helpful
- alec 12y agoMy computer runs Debian, so I read debian-security-announce, which gets one email per updated package. Sample of messages from this year: https://lists.debian.org/debian-security-announce/2014/threads.html https://lists.debian.org/debian-security-announce/2014/threa...
- dchest 12y agoFor Ubuntu: https://lists.ubuntu.com/mailman/listinfo/ubuntu-security-announce https://lists.ubuntu.com/mailman/listinfo/ubuntu-security-an...
- orblivion 12y agoIs there anything beyond getting what our distro sends down the pipeline? Exactly how behind would I be if I did that?
- gpvos 12y agoYour distro should be up to date already. They have been pretty quick on the uptake, many even quicker than the bash maintainer himself. Your bash is safe if it has a patch level equivalent to bash 4.3-027 (released 27-Sep-2014 22:38). Several distros had the equivalent patch by Florian Weimer already a day earlier. The later bash patches fixed the underlying bugs, but that patch removed the attack surface (but introduced a backwards compatibility problem for the very, very few programs (I don't know of any) that actually create shell functions to be inherited by bash).
- reirob 12y agoJust checked on my Raspberry Pi, Raspbian does not yet provide a fix.
- orblivion 12y agoI didn't get any updates on Debian yet either. From reading this: http://unix.stackexchange.com/questions/158767/which-debian-patches-fixes-shellshock-lcamtuf-cve-2014-6277-and-cve-2014-6278 http://unix.stackexchange.com/questions/158767/which-debian-... It looks like Debian may have applied something to make the attack not exploitable, even though it still segfaults. Seems weird to me, but it's the best explanation I have.
- gpvos 12y agoYou are confused. You say that you didn't get any updates on Debian, yet you say that it looks like Debian may have applied something. As I explained above, the patch for CVE-7169 by Florian Weimer made bash invulnerable to code injection by arbitrary environment variables. The underlying bugs CVE-6277 and CVE-6278 therefore have no known attack vector from outside bash, though they can still be triggered from a shell script or the command line if they are not patched. Theoretically, they could become part of a different attack, so it's wise to patch them, but there's no hurry, since as long as you or Debian have applied the abovementioned patch for CVE-7169, it means there's currently no publicly-known exploit. Also, Debian uses dash as its version of sh, so the problem can only occur if bash is called explicitly.
- ultramancool 12y agoYou sure you're not thinking of https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-7169 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-7169 instead? Interestingly, I see many references to 6271 and 7169 but nothing for 6277. Can anyone break this down better?
- deleted 12y ago[deleted]
- laumars 12y agoSeems like it was created a month ago today: Date Entry Created: 20140909 Also, there's been a few more patches since (bash43-030): http://ftp.gnu.org/gnu/bash/bash-4.3-patches/ http://ftp.gnu.org/gnu/bash/bash-4.3-patches/
- f- 12y agoBatches of CVE numbers get pre-allocated to major players well ahead of any actual vulns being found, so that there is no need to individually request IDs from a central authority for, say, every single browser bug. That happened here, the vuln itself is... um, around two weeks old.
- laumars 12y agoAhh I didn't realise that. Thanks for the correction. Do you know if the more recent patches, {27..30}, are also vulnerable to this CVE?
- gpvos 12y agoPatches 28-30 fixed underlying bugs, but 27 closed the loophole that made them accessible from the outside. So if you have 27 but not the later ones, you are safe from any currently known attack method from "outside" bash; you can still trigger unexpected code execution from the command line or a shell script, but this cannot be done remotely anymore. Theoretically, these bugs could be used as part of another attack, so it's wise but not urgent to patch them anyway.
- willvarfar 12y agoIt's a month old. There's a filing date on the linked post. You can also Google it.