6 ms·
Quick notes about the bash bug, its impact, and the fixes so far
- tobinfricke 12y agoReminds me of this: "Nobody really knows what the Bourne shell's grammar is. Even examination of the source code is little help." — Tom Duff http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.41.3287&rep=rep1&type=pdf http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.41.... Sounds like a time-bomb for exploitable unexpected behavior.
- krakensden 12y agoI wonder how many people are relying on this behavior for their production systems. It can't be zero.
- marcosdumay 12y agoI wonder how many people knew about this behavior a week ago.
- dscrd 12y agoIt's so cute when people ridicule superior engineering like plan 9 while they wallow in the incredible quagmire of so-called pragmatic systems.
- wereHamster 12y ago> Ree88. J. Reeds, ‘‘/bin/sh: the biggest UNIX security loophole,’’ 11217-840302-04TM, AT&T Bell Laboratories (1988).
- dfc 12y agoDo you have a copy of or link to that article? Or are you just pasting a citation with a cute title? I have stumbled across that citation a couple of times but I have never been able to find it.
- pilif 12y agoThis is a perfect example of why you should never, ever put special magical values in-band with a facility which has a different purpose normally. I know it's tempting and in many cases, it will save you a lot of work, but it will eventually lead to data corruption, or, way worse, a problem like this one here. People in the office complain about my annoyed remarks when they succumb to the dark side and use some special values. My question "but what if a real value is ever sent that looks like one of these magic values?" is usually countered with "but who's ever going to send this value?". This bug here is providing me with a perfect answer to that question: "Security researchers, or worse, bad guys". There are so many ways of transferring functions to subshells that don't involve magic values in a free-form key/value store, but all of them would have been more complicated, so people chose the quick hack. And now the sh*t has hit the fan :(
- ygra 12y agoLike Terminal escape sequences? ;) (On an old SunOS machine in uni back in the day I could create files that changed the colour of ls output. The very same mechanisms sometimes also allow you to redefine keys, depending on the terminal.)
- cleaver 12y ago:) Years ago a colleague carefully crafted an ASCII escape sequence for VT320 terminals that would mess up the screen and program a function key to send a network-wide broadcast message. He sent a note to an admin... something like: "This is cool. If the screen gets messed up, just hit Shift-F12." Everyone on the network received a broadcast message: "I've been had." Obviously, it could have been a lot worse.
- minikomi 12y ago> And now the st has hit the fan :( And now the sh has hit the fan :(
- pilif 12y agothere we go - another example of my point :p
- sp332 12y agoI thought the patch wasn't that effective? Is there a PoC that runs on a patched system anymore? Edit: found one https://news.ycombinator.com/item?id=8365216 https://news.ycombinator.com/item?id=8365216
- vpeters25 12y agoCould we fork bash to make this "feature" configurable?
- TeeWEE 12y agoSo only servers actually executing bash with input from browser (cookies etc) are affected (like CGI)?
- manicdee 12y agoPlus any DHCP client that runs shell scripts using parameters from The Evil DHCP Server, for example.
- chomp 12y agoSo has a new patch come out? I hacked up a temporary patch that fixes this last night after the new PoC was released, but I'd rather have something from upstream.
- f- 12y agoThere is an unofficial patch that takes a much more reasonable approach: http://www.openwall.com/lists/oss-security/2014/09/25/13 http://www.openwall.com/lists/oss-security/2014/09/25/13
- ck2 12y agoSomeone really needs to interview Stephane Chazelas and ask them how the heck they found this flaw in the first place (after 15 years).