Google Broadens Bug Bounties To Include Web App Security 50
n0-0p writes "Google just announced they will pay between $500 and $3133.70 for security bugs found in any of their web services, such as Search, YouTube, and Gmail. This appears to be an expansion of the program they already had in place for Chrome security bugs. 'We've seen a sustained increase in the number of high quality reports from researchers, and their combined efforts are contributing to a more secure Chromium browser for millions of users.' The rules and qualification details were posted today at the Google Online Security Blog."
Apparently (Score:2, Funny)
Ain't the first, ain't the last (Score:1)
Rejoice!
Re: (Score:3, Informative)
Re: (Score:2)
1 in hexadecimal is the same as 1 in decimal. 1 dollar (decimal) is the same as 1 dollar (hex).
Now, 100 (hexadecimal) cents is the same as 256 (decimal) cents, which is probably what you mean.
1 dollar (decimal or hexadecimal) = 100 (decimal) cents
Re: (Score:2)
A hexadecimal dollar is 100 hexadecimal = 256 decimal cents. There's a semantic difference in "1 (hexadecimal dollar)" (Knuth's version) vs "(1 hexadecimal) dollar" (your version).
See Donald Knuth's FAQ [stanford.edu].
Also, it's a joke, so there's probably no point in arguing technicalities.
Does this imply.... (Score:3, Interesting)
Re:Does this imply.... (Score:5, Informative)
These categories of bugs are definitively excluded:
Re:Does this imply.... (Score:4, Funny)
Re: (Score:2)
Never mind how many, I'm still wondering about that number.
I'm sure there is a swoosh involved somewhere, but what is the significance of 3133.70?
Re: (Score:2)
31337 = eleet (elite)
Re: (Score:3, Funny)
Too old to pay much attention to kiddies I guess.
Re: (Score:2)
Hand over your geek card, that's a 3-month suspension.
New Minivan! (Score:2)
http://thedailywtf.com/Comments/The-Defect-Black-Market.aspx?pg=2 [thedailywtf.com]
Found some! (Score:1)
>> they will pay between $500 and $3133.70 for security bugs found in any of their web services,
I just found "About 7,690,000 results (0.33 seconds)" for security bugs in one of their services. Just go ahead and make that check out for an even bazillion and we'll call it good.
I wonder how the culture works on the other side. (Score:1)
This is such a smart move... (Score:2)
Just wait for it.
Re: (Score:2)
Bug economy (Score:5, Interesting)
A story from the past...
A Former Employer Who Shall Not Be Named had a product about to go golden-master, and wanted every employee in the company to participate in the final round of testing. Then the pointy-haired bosses got an idea! During the last round of testing, they put up a bounty of twenty dollars for each P3, fifty dollars for each P2, and a hundred dollars for each P1 bug found. However, the pointy-hairs decreed QA and Dev were excluded, and in the same breath decreed that QA and Dev would be working overtime.
An underground economy of bugs immediately sprang up. QA guys would find bugs and quietly share them with tech support/sales engineers/etc. Devs would notice (and it was whispered, though never proven, create) bugs and quietly share them with IT. And the proceeds would be split between the ineligible employees and the eligible.
Over fifty thousand in bounties were paid. Then the pointy-hairs got wind of what was going on.
And that was the end of that.
Irrelevant to the story at hand, though, I'm quite sure...
Re: (Score:1)
Seems CVS or similar would counter purposely creating bugs, unless someone's going to modify the history tree, and any older copies of the source code sitting around.
Am I missing any openings where "insert bugs" can still fill "???" and lead to "PROFIT!"? Maybe putting a bug in on purpose, and letting it sit around for a month before reporting it?
Re: (Score:2)
Though one must always watch for people gaming the system, or becoming too fixated on the reward, when it's the bug-fixing that's the important part.
Perhaps only reward during specified "bugfix drives", and disqualify/discipline/fire anyone found to be inserting bugs just to be the one to fix them?
Re: (Score:2)
As far as I know (this was about 6 months before my time at That Company, and was the subject of hallway lore, which is how I learned of it), it was never proven that buggy code was being deliberately checked in. What WAS certainly going on was that people who were in a position to know about bugs but were bounty-ineligible were sharing that knowledge with people who were bounty-eligible. The bugs were found and fixed, the product wasn't hurt, but the bounty system was thoroughly gamed by people who were ex
BFD (Score:4, Funny)
Oh, what's that, you can't find any?
Security through obscurity wins again.
Re: (Score:1)
Re: (Score:1)
Re: (Score:2)
Re: (Score:2)
I would guess experience...because he's right.
Although not about the "exponentially" part. 3000^2=9 million. But yeah the black market price for any remote-exploitable bug starts higher than Google's biggest reward. And it's easier to get away with not paying taxes on the black market deal.
China (Score:2)
China is paying $1,000 and $6267.40 for any security bugs found in any of Googles web services. ;)
IE? (Score:3, Funny)
waiting for microsoft to start one of these for Internet Explorer or Windows. Then I can retire :)
Re: (Score:2)
How about Google starts listening to its forums? (Score:1)
What bugs get the eleet bounty? (Score:1)
Re: (Score:2)
It's OVER 9000!