MacBook Hacked In Contest Via Zero-Day Hole in Safari
EMB Numbers writes "Shane Macaulay just won a MacBook as a prize for successfully hacking OS X at CanSecWest conference in Vancouver, BC. The hack was based on a Safari vulnerability found by Dai Zovi and written in about 9 hours. CanSecWest organizers actually had to relax the contest rules to make the hack possible, because initially nobody at the event could breach the computers under the original restrictions. 'Dai Zovi plans to apply for a $10,000 bug bounty TippingPoint announced on Thursday if a previously unknown Apple bug was used. "Shane can have the laptop, I want the money," Dai Zovi said in a telephone interview from New York. TippingPoint runs the Zero Day Initiative bug bounty program.'"
If I recall correctly, originally the requirement was remote access, but when that went nowhere, they allowed entrants to submit URLs that would be navigated to via Safari. Check out Engadget for more details...
As I understand it:
The rules originally required getting a user shell on a macbook connected to a wireless router without any other access, or getting a root shell under the same conditions on a second macbook without using the same bug.
The prize was the macbook(s) you hacked.
But they decided not enough people were interested, so 3Com added a $10,000 bounty for a winning bug.
But no one could crack it, so they set the machine up to visit malicious web pages submitted by email.
Then someone found a bug in Safari, and successfully crafted a webpage to exploit it to get user shell access.
"The worst tyrannies were the ones where a governance required its own logic on every embedded node." - Vernor Vinge
The MacBook was actually only hacked because they lessened the rules and actually had someone open Safari and use a malicious website. No ports were closed nor was the firewall running.
I'm a Mac user and as such I'm not claiming invincibility although the "Unix" like foundation makes me more secure its still the end user's responsibility to not run as admin or God forbid root. Not to mention using a good firewall or correctly configuring the one that's already built in is vital and just practicing caution on the web. That aside I just don't think this is entirely honest, I wish they would disclose all the variables involved to include all settings used. But as others here have said considering Apples foresight using open source means the between Apple and the Konqueror devs this will be quickly addressed. But my gut feeling here is that something stinks in Denmark!
Die First, Then Quit
The intent was always that the rules would be progressively relaxed - see http://www.securityfocus.com/archive/142/464216/30 /0/threaded from last month.
Safari lets you include local files, for example...
i told apple (and got a lame reply that it would be fixed eventually) month ago, yet it still works.
see http://destabili.zation.eu/ for a quick harmless example that can check what applications you got installed.
and then there is a way to crash Safari which exists for more than a year - again i had an email conversation where they wanted more info and crashreports - yet nothing was ever done about it.
http://lixlpixel.org/safaricrash/ and follow the instructions - but make sure you don't have any important tabs open...
Well in the nightly Webkit builds the javascript engine has been overhauled, so chances are it's "already" fixed, in a sense. Up until now it's looked like Apple's been prepping that for a Leopard release, but maybe this will prompt them to move it up.
By the way, those Webkit nightlies are really looking strong.
Now, WebKit is developed in a public repository, and used by Nokia and others, as well as Apple. There has been some discussion of KDE abandoning KHTML and using WebKit for Konqueror, but this was met with mixed reactions. WebKit and HTML are now very different systems, although they share a common heritage and often import each others' changes when possible.
I am TheRaven on Soylent News