Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Hands-On Bug Hunting for Penetration Testers
  • Toc
  • feedback
Hands-On Bug Hunting for Penetration Testers

Hands-On Bug Hunting for Penetration Testers

By : Himanshu Sharma, Joe Marshall
4 (2)
close
Hands-On Bug Hunting for Penetration Testers

Hands-On Bug Hunting for Penetration Testers

4 (2)
By: Himanshu Sharma, Joe Marshall

Overview of this book

Bug bounties have quickly become a critical part of the security economy. This book shows you how technical professionals with an interest in security can begin productively—and profitably—participating in bug bounty programs. You will learn about SQli, NoSQLi, XSS, XXE, and other forms of code injection. You’ll see how to create CSRF PoC HTML snippets, how to discover hidden content (and what to do with it once it’s found), and how to create the tools for automated pentesting work?ows. Then, you’ll format all of this information within the context of a bug report that will have the greatest chance of earning you cash. With detailed walkthroughs that cover discovering, testing, and reporting vulnerabilities, this book is ideal for aspiring security professionals. You should come away from this work with the skills you need to not only find the bugs you're looking for, but also the best bug bounty programs to participate in, and how to grow your skills moving forward in freelance security research.
Table of Contents (16 chapters)
close

Reproducing the Bug – How Your Submission Is Vetted

Without the internal security team being able to validate your findings by recreating your PoC, it's hard to get a reward. You could've spoofed or mocked up findings, or created them during some since-patched edge condition that doesn't represent a significant threat.

The easiest way to ensure that your bug is reproducible is to, from the very beginning, practice reproducing it yourself. If it's a manual finding or semi-automated tool such as Burp Intruder, can you reliably recreate it (it might take a couple of tries to get the right sample size if there's a race condition), and if it's from the tightly-controlled application of a scanner, can you recreate it manually? It's not enough to run the scan again and see the same results, if you can't recreate the automated vulnerability...

bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete