Security Blog

The latest news and insights from Google on security and safety on the Internet

Rewarding web application security research

1 de novembro de 2010
Share on Twitter Share on Facebook
Google

31 comentários :

Oscar disse...

This is a really good approach. It rewards people for pushing the boundaries of the software and finding issues with it. I wish the Diaspora guys had something like this in place.

1 de novembro de 2010 às 16:00
Unknown disse...

Excellent effort by Google (clap clap clap)

1 de novembro de 2010 às 16:49
Unknown disse...

I was just talking to someone about the recent vulns found in the android kernel from HTC being a good argument for "no more free bugs". This is great news. I look forward to them expanding the program to android.

1 de novembro de 2010 às 16:58
Anônimo disse...

Rewards programs like this are legally interesting. I don't know if it's legally possible to participate in this program without breaking an "attempted computer intrusion" law.

1 de novembro de 2010 às 17:20
Unknown disse...

I'm sure the young hackers among us will be interested in precisely what you mean by
"This program is also not open to minors", in particular, what jurisdiction applies in determining the age or majority.

1 de novembro de 2010 às 18:11
rjwalltech disse...

Mark, they probably mean the age in which a person is allowed to vote. In the U.S. this means 18.

1 de novembro de 2010 às 18:47
Maxwell disse...

Is there a reason for the no-minors restriction?

1 de novembro de 2010 às 19:51
jcwayne disse...

Maxwell, in many (most?) jurisdictions there are various legal restrictions regarding how companies interact with minors (especially when money is involved). I'm sure the intent here is to avoid the need to involve lawyers in validating the legality of giving an award in any particular case. That said, I would suggest any minor looking to claim a reward simply have a parent or other trusted adult apply on their behalf.

1 de novembro de 2010 às 21:21
Arthur disse...

@oscar Diaspora is software in pre-alpha state, it's open sourced, it has no current user base, no revenue stream, it's currently being supported entirely by donations it received, and there's only 4 people at the company. This model of paying for security bugs has absolutely no feasibility or relevance at this point to Diaspora.

1 de novembro de 2010 às 21:38
Unknown disse...

Do, *.blogger.com is included... but is *.blogspot.com?

2 de novembro de 2010 às 01:48
Anônimo disse...

There is a large section of the community who see bug hunting for money as a diss and are not interested in it and will not associate with any company offering money.

This programme won't help your plight, but send people walking further away.

Google should not be limiting their scope to draw in good bug hunters, but this is exactly the effect offering money will have.

This is not in the best interest of security.

Andrew

2 de novembro de 2010 às 07:57
Unknown disse...

Are vulnerabilities in the reCaptcha service elegible for the reward?

If so, what is the scope in this case about what would be considered a vulnerability?

2 de novembro de 2010 às 08:05
Unknown disse...

You have some "buggy links" on the Hall of Fame page:
For most of the HOF entries, clicking on the bug number takes me to the report page. However, some of the bug numbers take me to a page promoting Google Project Hosting. I didn't check all numbers but here are the problematic ones I found: 51630, 48283, 51070. There are probably others too.

By the way, searching the HOF page or the other related linked pages, I didn't see any directions on how to contact anybody to report such issues about the web pages. That's why I'm posting it here. It would be nice to add some contact info to those pages.

2 de novembro de 2010 às 14:11
Unknown disse...

This is still pathetic and ridiculous, "$3,133.7 dollars" that is it!!! a company as big as Google and only pays $3K and not just for any bugs, the "severe and unusual" are you serious?! , a severe and unusual bug would be sold somewhere else for thousands, and EAP/ZDI/iDefense pays more than $3K (if you provide accurate details for the bug) for the not severe and unusual ones.

so why again would Google bother and announce this?

2 de novembro de 2010 às 15:17
Chris Evans disse...

@Selim: I think the Chromium Hall of Fame links are ok. You're not seeing a promotion page, but a login page. Some of the bugs are still "hidden" when they are fixed in Chromium but might still affect the products of other vendors which use the same underlying libraries.

@Netdev: as clearly stated, the rewards can be donated to charity. This gives hackers who get their buzz via non-monetary means to make the world better in two different ways at once.

2 de novembro de 2010 às 15:19
Anônimo disse...

I don't see how would finding bugs in software would ever make the world for a better place.

This 3K offer might be pathetic but for some minor XSS problems and other stuff it well worth it if you put into 10-20 hours work.

Anyway now that they announced it to the public and thousands of newsportals advertising it this bughunt will also exhaust. Like any other opportunities online to make money eg: elance.

Even if you find some bugs theres a good chance someone did it already and you wasted your time, google wont pay for it.

2 de novembro de 2010 às 17:39
Muhammad Huzaifa Ali disse...

I have found a bug in Google Buzz this bug also indirectly effect Google Adsense program which results in false clicks and google TOS breach.

I do not know whether google buzz is included in this program.

2 de novembro de 2010 às 23:33
Unknown disse...

I bet Apple would do the same thing.

3 de novembro de 2010 às 15:14
test12563 disse...

great.. I'll try ;)

6 de novembro de 2010 às 14:27
Unknown disse...

I just passed the "Gmail Security Verification" questionnaire in Russian, and found one small mistake:

on the last step there I see Romanian "Selectaţi „Rămâneţi conectat(ă)” numai dacă vă conectaţi de pe un computer personal.", that cannot be understood by Russian. Please fix it.

Thanks

11 de novembro de 2010 às 04:11
Jay disse...

Thanks for your report, GeniU$. We have passed your comment to the appropriate team to investigate and make a correction.

Google Operations Team

11 de novembro de 2010 às 13:31
Adriano Morgon disse...

Hi, i'm from Brazil, here the version 8.0.552.224 of Google Chrome returns many pages using orkut.com, it's very unconfortable. Thank You, and sorry for the worst english ):

30 de dezembro de 2010 às 19:52
Pedro disse...

Hi, i send one email about google adsense bugs, its a very dangerous bug make 5 day and google dont have-me send any feedback, i just whait google fix to publish on some security blogs, sorry bad english

3 de janeiro de 2011 às 00:44
Unknown disse...

Hey blackmind

Can you please post the ID number you received in the auto-reply? It should be in the subject header.

thanks,
Adam

4 de janeiro de 2011 às 12:30
Pedro disse...

Hi adam, the id is 740250882

Tks

4 de janeiro de 2011 às 14:12
Kirk Gehman disse...

I assume the cash reward is not available to Google developers :-)

7 de fevereiro de 2011 às 07:00
test2009 disse...

Hello.

These sites are included in the awards program ?

admob.com
googlestore.com
gizmoproject.com
gizmo5.com
picnik.com
on2.com
googleusercontent.com
opensocial.org
whatbrowser.org
googledeveloperday.com
zeitgeistminds.com

7 de abril de 2011 às 04:35
jaumlucas disse...

feedburner.com is on the scope of reward program?

31 de maio de 2011 às 10:11
Sagan Marketing disse...

It's a good idea but I agree that the money reward is not worth it... most hackers would be able to see such security bugs for more money than than in other markets... plus those of us who would be willing to invest time into finding such bugs would need a bigger reward than $500 with a chance of $3k... maybe if they did $3k with a chance of $10k... we live in a world where those of us with skills value our time very much... still I'll be on the lookout for anything I can spot indirectly...

13 de fevereiro de 2012 às 01:30
Anônimo disse...

Why do I have to have a cellphone?I've been asked for a mobile number again when I made it clear days ago I don't have a cellphone.

I was instead provided with a verification e-mail.

I can barely get the hang of the newer ones and I have trouble with using text on cellphones.

23 de maio de 2012 às 10:38
Unknown disse...

Hi.

What about Android platform? It's in the program or it isn't?

14 de maio de 2013 às 10:26

Postar um comentário

  

Marcadores


  • #sharethemicincyber
  • #supplychain #security #opensource
  • android
  • android security
  • android tr
  • app security
  • big data
  • biometrics
  • blackhat
  • C++
  • chrome
  • chrome enterprise
  • chrome security
  • connected devices
  • CTF
  • diversity
  • encryption
  • federated learning
  • fuzzing
  • Gboard
  • google play
  • google play protect
  • hacking
  • interoperability
  • iot security
  • kubernetes
  • linux kernel
  • memory safety
  • Open Source
  • pha family highlights
  • pixel
  • privacy
  • private compute core
  • Rowhammer
  • rust
  • Security
  • security rewards program
  • sigstore
  • spyware
  • supply chain
  • targeted spyware
  • tensor
  • Titan M2
  • VDP
  • vulnerabilities
  • workshop


Archive


  •     2025
    • mai.
    • abr.
    • mar.
    • fev.
    • jan.
  •     2024
    • dez.
    • nov.
    • out.
    • set.
    • ago.
    • jul.
    • jun.
    • mai.
    • abr.
    • mar.
    • fev.
    • jan.
  •     2023
    • dez.
    • nov.
    • out.
    • set.
    • ago.
    • jul.
    • jun.
    • mai.
    • abr.
    • mar.
    • fev.
    • jan.
  •     2022
    • dez.
    • nov.
    • out.
    • set.
    • ago.
    • jul.
    • jun.
    • mai.
    • abr.
    • mar.
    • fev.
    • jan.
  •     2021
    • dez.
    • nov.
    • out.
    • set.
    • ago.
    • jul.
    • jun.
    • mai.
    • abr.
    • mar.
    • fev.
    • jan.
  •     2020
    • dez.
    • nov.
    • out.
    • set.
    • ago.
    • jul.
    • jun.
    • mai.
    • abr.
    • mar.
    • fev.
    • jan.
  •     2019
    • dez.
    • nov.
    • out.
    • set.
    • ago.
    • jul.
    • jun.
    • mai.
    • abr.
    • mar.
    • fev.
    • jan.
  •     2018
    • dez.
    • nov.
    • out.
    • set.
    • ago.
    • jul.
    • jun.
    • mai.
    • abr.
    • mar.
    • fev.
    • jan.
  •     2017
    • dez.
    • nov.
    • out.
    • set.
    • jul.
    • jun.
    • mai.
    • abr.
    • mar.
    • fev.
    • jan.
  •     2016
    • dez.
    • nov.
    • out.
    • set.
    • ago.
    • jul.
    • jun.
    • mai.
    • abr.
    • mar.
    • fev.
    • jan.
  •     2015
    • dez.
    • nov.
    • out.
    • set.
    • ago.
    • jul.
    • jun.
    • mai.
    • abr.
    • mar.
    • fev.
    • jan.
  •     2014
    • dez.
    • nov.
    • out.
    • set.
    • ago.
    • jul.
    • jun.
    • abr.
    • mar.
    • fev.
    • jan.
  •     2013
    • dez.
    • nov.
    • out.
    • ago.
    • jun.
    • mai.
    • abr.
    • mar.
    • fev.
    • jan.
  •     2012
    • dez.
    • set.
    • ago.
    • jun.
    • mai.
    • abr.
    • mar.
    • fev.
    • jan.
  •     2011
    • dez.
    • nov.
    • out.
    • set.
    • ago.
    • jul.
    • jun.
    • mai.
    • abr.
    • mar.
    • fev.
  •     2010
    • nov.
    • out.
    • set.
    • ago.
    • jul.
    • mai.
    • abr.
    • mar.
  •     2009
    • nov.
    • out.
    • ago.
    • jul.
    • jun.
    • mar.
  •     2008
    • dez.
    • nov.
    • out.
    • ago.
    • jul.
    • mai.
    • fev.
  •     2007
    • nov.
    • out.
    • set.
    • jul.
    • jun.
    • mai.

Feed

Follow
Give us feedback in our Product Forums.
  • Google
  • Privacy
  • Terms