Linked by Thom Holwerda on Thu 19th Mar 2009 06:44 UTC, submitted by Moulinneuf
Privacy, Security, Encryption As he had already predicted, cracker Charlie Miller has won the PWN2OWN contest by cracking Safari and Mac OS X within seconds of the start of the competition. "It took a couple of seconds. They clicked on the link and I took control of the machine," Miller said after his accomplishment. He took home the USD 10000 prize, as well as the MacBook he performed the exploit on. Internet Explorer 8 fell a while later by cracker Nils, who also cracked Safari and Firefox after being done with IE8.
Permalink for comment 353845
To read all comments associated with this story, please click here.
Comment by Hakime
by Hakime on Thu 19th Mar 2009 08:05 UTC
Hakime
Member since:
2005-11-16

"It will be interesting to see how it was cracked - and hopefully Apple will wake up and do something about the security issues in Safari and Quicktime"

You say that and in the same time IE and Firefox were also compromised. How does your point make any sense here?

" contest by cracking Safari and Mac OS X within seconds of the start of the competition."

BS, his job is to find security holes, he surely spend plenty of time to find this one, saying that he did this in x or y second for sensationalism does not make any sense as he had tested before if the exploit works. The only thing that he needed was someone to click where he wanted it.

"This is the second year in a row that Safari on the Mac is the first to fall in the PWN2OWN contest, again by Miller's hands."

The order is not important here because they all fell in the same stage of the context. Because Miller demonstrated the his exploit first does not make that Safari fell first. You make is it sound that Safari fell first and therefore it is less secure but the fact is that IE or Firefox fell exactly in the same manner, regardless who performed the exploit first.

"So far, only Chrome hasn't been cracked yet, but that probably won't take long"

Humm, the flaw in Safari is probably in webkit, Chrome is probably also affected.

Reply Score: 7