In Under 10 Hours, Google Patches Chrome To Plug Hole Found At Its Pwnium Event
An anonymous reader writes "Last night, Google held its Pwnium 2 competition at Hack in the Box 2012, offering up a total of $2 million for security holes found in Chrome. Only one was discovered; a young hacker who goes by the alias 'Pinkie Pie' netted the highest reward level: a $60,000 cash prize and a free Chromebook (the second time he pulled it off). Google today patched the flaw and announced a new version of Chrome for Windows, Mac, and Linux."
Oracle could take a lesson from this.
New version of Chrome within 24 hours... wow.
So a My Little Pony hacked up Chrome?
I await the fan art for this visual image!
..that Pinkie Pie is best pony.
Hacking Google for fun, profit and to the benefit of other's.
How hard Pinkie Pie had to fight not use their real name, or if Google just let it slide.
Who would have thought that legal hacking can make you rich faster than a day job. I bet he can live quite OK with the prize money, until the itch for luxury will create more need for money.
~ Best man at your service.
Currently http://getfirefox.com is again pointing to Fx 15. I wonder if it was related to this at all?
I think this demonstration of crack-on-demand is not really a good thing for chrome. This means that cracks for chrome are not worth too much more than 60k on the black market. That doesn't seem like a very high price.
i) Create known flaw - a 'bug'
ii) challenge others to find bug
iii) fix 'bug' very quickly
iv) profit - as you Do Know Evil
It's good to see Google is able to get patches out this quick. I've worked in small businesses that same day fixes were doable but a challenge and a government office with so much red tape pushing something to production that quick would have been impossible. I bet neither MS nor Apple could pull that off.
Looks like Google is keeping it's hacker culture alive rather than becoming a slow moving behemoth like their competitors.
"If you are going through hell, keep going." - Winston Churchill
should be the main metric for security for web browsers (and other software exposed to the internet).
It would difficult to argue that there are not security holes in all browsers and that the holes can be found and exploited with sufficient resources. All of the security measures browser makers use at best make it harder to get a working exploit.
I think that that closing the wholes as fast as possible lowers the expected profit for finding an exploit and lowers the time the user is exposed and that this is more effective than sandboxing and memory randomization to providing a secure browser.
While the turn-around time is impressive, it could not possibly have undergone extensive QA testing...
I understand that some bugs can have such OBVIOUS solutions - what could POSSIBLY go wrong with the fix???
If the fix changes a behaviour in a corner-case not caught by a unit test then your module regression test isn't worth much anymore.
Back when people finding security holes had to beg to get vendors to fix them, the patch-and-release approach had a chance of working. Now that there's an active market in security holes, someone who finds one can make more money selling it to the attack side.
If by "pretty close" you mean "well above".
For 2010 (the most recent year for which statistics are available; the 2011 statistics should be available this month), the Social Security Administration figures show the median annual wage in the US as $26,363.55, and the average annual wage as $39,959.30.
So, $60K is more than twice the median annual wage and more than 1.5 times the average annual wage. Its also a more than the median household income ($50,054 in 2011, per the U.S. Census Bureau).
Factoring all overheads (e.g. HR, office space, equipment), how much would a company like Google have to pay to hire a security team to do the amount of security testing work done collectively at this "competition"? Well above $2,000,000. A whole bunch of people do free testing, and one guy gets $60,000 'and a free Chromebook, wow' - not that impressive an amount, considering the amount of self-training and self-development you have to put it in to reach that level of expertise, and the amount of time needed to find a security problem. $60K is, what, maybe 6 months salary of hiring a person of that skill level to do similar work .. when you factor in overhead costs, maybe even just 3 or 4 months worth (Google would probably have been very lucky to hire someone to find that bug for that cost). Come on Google, you can afford to pay people properly for such valuable work .. I don't like these cheap tricks that companies like Google use to effectively get people to work for them for free or peanuts.
As mentioned this isn't first time Pinkie Pie has made bank off of Google. This appears to bring his yearly earnings from this to $120,000. Seems like rather profitable work, but assuming (hoping?) the limited number of zero day exploits I reckon this quickly becomes a tight zero-sum game for the participants.
Yet I'm supposed to trust its security?
Presumably they _do_ pay people for such valuable work. This isn't a "cheap trick", it simply acknowledges that:
- No matter what experience you do employ, there will always be vastly more external experience.
- Not everyone interested in these things would necessarily be motivated by being employed by Google (or even by money).
- Offering an alternative to the black market for such skills is a good idea.
Boffoonery - downloadable Comedy Benefit for Bletchley Park
I recently went back to school for some classes, and not only does one of my classes want you to install Java on your home computer, but they want you to install Real as well.
Why Real? I didn't even think they were still in business, to be honest.
Exactly. Also, Real has managed to get rid of the advertising free versions that used to be available for educational use. Luckily, I still have a corporate ad-free real client at work that I downloaded a few years ago for someone if real-alternative doesn't work.
What were they using Real for, anyway?
I'm not really sure. It could have been a false/obsolete requirement. At work, people occasionally want to listen to web casts that are in real format.
I've run into a couple of places with that requirement and its always shitty lecture videos somebody recorded in Real format and is too fucking lazy to transcode.
ACs don't waste your time replying, your posts are never seen by me.