views:

130

answers:

2

I wish to know from SO security experts and hackers what kind of tools would they use to find a security hole in Chrome's armor? And using what programming and testing techniques?

I'm particularly interested in Open Source tools running on Linux.

Google announced on the Chrome Web Browser blog that they will pay 500$US for each security bug found. They plan to offer 1337$ for major bugs.

Thanks and happy bounty hunting!

+2  A: 

just my opinion,

If you are not experienced in software you have better to exploit your skills doing some normal application/web app development then trying to get money from Google. After all two days of a freelance developer is about 500$.

Finding exploit is a difficult task and require really an huge knowledge of how computers works. There is many tecnics to discover exploits but almost none of them are automatic. If it was just using a tool Google would have done it themselves.

after for some basic tool you can try fuzzing tool but not really sure how it would behave with a browser.

RageZ
Thanks, I was just wondering if there is tools to help finding security holes in a software product. I do have experience in software but not that kind of expertise. I don't intend to find bugs in Chrome to make a leaving. :)
esavard
one way to go is also to download the source and try to use some code analyze tool on the source but like I said those kind of tool require a lot of knowledge and are not easy to use ^^ If you are doing that just by curiosity I would advice you to read tutorials on internet and try to find security holes in your own code, if you have coded a network service/daemon in your life. Security and exploit finding got really complex because the complexity of Oses/kernel/Just In time compilation/Obfuscation really changed lately, good luck
RageZ
A: 

Couple of points

  • Read up about fuzzing
  • Read up about Assembly language
  • Obtain a fuzzer
  • Obtain a reverse engineering program / Debugger (OllyDB, IDA Pro)

Sorry I can't be more help, but I don't do a lot of fuzzing myself. But the points above should help you find overflows and whatnot in Chrome, if there are any. Finding exploits like this can be very tricky. I can only imagine the testing Google would give their apps before releasing them, but good luck ;-D