7 ms·
MAYHEM – automatically finding bugs and shell-spawning exploits in binaries [pdf]
- contingencies 13y agoGee, they could have sold those for a lot of money. Well done researchers, you have a strong moral compass.
- dguido 13y agoYes, all of those vulnerabilities in non-privileged applications like 'ls' are worth millionssssss.
- jerf 13y agoYes, and then they combine them with a kernel exploit and, uh, suddenly your "unprivileged process" turns out to not be so unprivileged after all. Resist the temptation to marginalize security bugs. They don't exist in isolation.
- tptacek 13y agoYou're right, but so is the parent commenter; there is a popular meme that security bugs in general are worth large amounts of money, but in reality only a small subset of bugs command real money.
- lawnchair_larry 13y agoYou could be a better ambassador of our industry by explaining the misconception instead of being condescending. And we wonder why developers think we are just arrogant jerks.
- dguido 13y agoYou're welcome to step in and explain, but I think it's pretty obvious why local vulnerabilities in non-setuid binaries aren't exactly "critical."
- betterunix 13y agohttps://xkcd.com/1200/ https://xkcd.com/1200/
- dguido 13y agoThat would only be accurate if you could trigger one of these bugs remotely.
- betterunix 13y ago...or if you can trick the user into opening a malicious file. An exploit in ls? Send them a zip, tarball, etc. with a maliciously named file.
- contingencies 13y agoIMHO anyone who contributes to the state of the art with regards to public security tooling is doing the world a favour. Even if the majority of these applications are not well privileged, and therefore of dubious value, applying the same technical knowledge elsewhere could earn them cash. I still applaud their efforts.
- bradleyland 13y agoThe value of a vulnerability is linked to its usefulness in accomplishing the goals held by those paying for the exploit. Based on that information, it should become obvious that the only bugs worth large sums of money are bugs that result in escalated privileges on the system or arbitrary code execution. Bugs that crash services also have value for DDoS attacks, but they're not as valuable as the two previously mentioned types. While 1.2k bugs sounds like a lot, we can't make an inference about the severity of the bugs based solely on the number of them. Also keep in mind that the Debian repository contains thousands of packages. From the Debian 7.0 Wheezy release page: "* more than 36,000 other ready-to-use software packages, built from nearly 17,500 source packages" http://www.debian.org/News/2013/20130504 http://www.debian.org/News/2013/20130504 The best we can infer that given 1.2k bugs, there is some statistical probability that any number of them may be severe. Without studying the data, we can't say what that probability might be though.
- wslh 13y agoDebian mailing list: http://lists.debian.org/debian-devel/2013/06/msg00720.html http://lists.debian.org/debian-devel/2013/06/msg00720.html Reddit's reverse engineering discussion: http://www.reddit.com/r/ReverseEngineering/ http://www.reddit.com/r/ReverseEngineering/
- dfc 13y agoThe link to reddit mentioned in parent is to the RE subbredit. The link to the actual MAYHEM discussion on reddit is: http://www.reddit.com/r/ReverseEngineering/comments/1h4vs4/reporting_12k_crashes/ http://www.reddit.com/r/ReverseEngineering/comments/1h4vs4/r...
- bluetooth 13y agohttp://www.reddit.com/r/ReverseEngineering/comments/1h4vs4/reporting_12k_crashes/ http://www.reddit.com/r/ReverseEngineering/comments/1h4vs4/r...
- lampe3 13y agokeep in mind: bug != security hole
- dfc 13y agoI have not finished reading the paper but after the second sentence in the abstract it seems that the authors clearly define what they consider to be a bug: Every bug reported by MAYHEM is accompanied by a working shell-spawning exploit. The working exploits ensure soundness and that each bug report is security critical and actionable.
- bugfinder 13y agoMayhem changed quite a bit since the publication of the paper. It now reports all crashes, and therefore bugs are not necessarily security critical.
- maerF0x0 13y agoMisleading title-- abstract says 29 exploitable vulnerabilities, not 1200 .
- wslh 13y agoLook at the reddit thread above.
- lysium 13y agoImpressive! Where does that 1.2K number come from, though? The abstract mentions only 29 (still a lot) and the results list 'only' 29, too, two of which where 0days. I admit I haven't read the whole article thoroughly.
- aroch 13y agoFrom the looks of things, the 1.2K number is the number of bug reports they plan on filing after de-duping and removing ones that aren't pertinent.
- bugfinder 13y agoThe paper has been published a while ago. We have been improving Mayhem quite a bit since then, and we recently ran it on debian binaries. It found many crashes, that are not necessarily exploits. 1.2K is the number of bug reports we are going to submit to the Debian bug tracker.
- dfc 13y agoAs a long time Debian user I would like to thank you for choosing Debian as a target platform. The maintainers might not appreciate the bugs in the short term but in the long term this is great for everyone involved. Was there any reason why you chose Debian? I imagine bts made things easier for bug wrangling/submission.
- joeyh 13y agoHaving received one of the bugs (that was not exploitable), I appreciated it in the short term. :P I hope a free version of this can be built, it would be a nice additional QA step to run before release.
- dfc 13y agoI see that it is for moreutils. I am having the hardest time using the interface for forallsecure.com. It seems that you can not search by package. When I browsed through the list I figured I would have come across moreutils around page 49/51 but I did not see it. I am tempted to download: http://forallsecure.com/programs/1 ... http://forallsecure.com/programs/22630 But that seems like a waste of everyone's resources. What was the bug? For people unfamiliar with joeyh's contribution to Debian it is important to note that he is a legendary DD: http://qa.debian.org/developer.php?login=joeyh%40debian.org http://qa.debian.org/developer.php?login=joeyh%40debian.org
- HockeyInJune 13y agoThe paper above and the post to the debian mailing list describe two different uses of the Mayhem tool. One with exploits, one without.
- lysium 13y agoWhile I find the reported results impressive, I'm sad to see another publication about a closed-source application. Nobody can reproduce the results or place their work on top of that. Research was not supposed to work that way (at least in my little universe :-), yet it gets published by the IEEE (but what does that mean nowadays?).
- therobot24 13y agoSometimes research is closed source due to where the funding comes from, I'm working a project that's been funded by two different entities over the years - one of which won't even release the dataset we've been using - so when trying to open source my code I get stuck.
- gwern 13y ago> This research was supported by a DARPA grant to CyLab at Carnegie Mellon University (N11AP20005/D11AP00262), a NSF Career grant (CNS0953751), and partial CyLab ARO support from grant DAAD19-02-1-0389 and W911NF-09-1-0273.
- xenophonf 13y agoThe paper documents their approach pretty thoroughly, and honestly, if it were me (and I'm a damn-the-torpedos-full-disclosure-open-access-everything kind of guy), I'd think twice about publishing a program that would give the kiddies something to do on a wet, wet, wet, day.