Bug bounty Tips

I have compiled all the resources from this 📱 YouTube video for you (free!), and I believe they will be sufficient for anyone looking to start their journey in #cybersecurity. Special thanks to David Bombal and Jason Haddix for sharing their knowledge to help us learn in 2024!

📚Web application hacker's handbook 📚OWASP  Web Security Testing Guide 📚Real World Bug Hunting 📚Bug Bounty Bootcamp 📚Red Team Field Manual v1 & v2 📚Red Team Development ... 📚Operator Handbook: Red Team... 📚Tribe of Hackers Red Team 📚The Pentester Blueprint 📚OSINT Techniques: Resources ... 📚Evading EDR 📚Attacking Network Protocols 📚Black Hat GraphQL 📚Hacking API’s 📚Black Hat Go 📚Black Hat Python 📚Black Hat Bash 📚Zseano’s methodology 📚Breaking into information security 📚Expanding your security horizons

📱 Wiki Book Pentest living document 📱 Fuzzing lists 📱 Sec Lists 📱 Payloads all the thing

s: 🖥 HackTRICKS 🖥 Web Security Testing Guide v4.2 🖥 APISEC University 🖥 Web security academy, Port Swigger 🖥 Pentester Lab 🖥 Try Hack Me: Red Team... 🖥 HTB Academy 🖥 Hacktivity 🖥 Vulnerable U 🖥 Bug Bounty Reports Explained 🖥 Sharing what matters in security 🖥 Intigriti 🖥 tl;dr sec 🖥 Unsupervised learning 🖥 Pentest Book 🖥 Bugcrowd 🖥 Trick

afrog is a high-performance vulnerability scanner that is fast and stable. It supports user-defined PoC and comes with several built-in types, such as CVE, CNVD, default passwords, information disclosure, fingerprint identification, unauthorized access, arbitrary file reading, and command execution. With afrog, network security professionals can quickly validate and remediate vulnerabilities, which helps to enhance their security defense capabilities.

go install -v github.com/zan8in/afrog/v3/cmd/afrog@latest

18. Bypassing Digits Origin Validation Which Leads to Account Takeover- How to Hunt: - Look for vulnerabilities where digits origin validation can be bypassed. - Refer to [HackerOne Report 129873](https://hackerone.com/reports/129873) for more details. 19. Top ATO Reports in HackerOne - How to Hunt: - Review top account takeover reports in HackerOne. - Refer to [TOP ACCOUNT TAKEOVER](https://github.com/reddelexc/hackerone-reports/blob/master/tops_by_bug_type/TOPACCOUNTTAKEOVER.md) for more details.

1. Pre-Account Takeover - How to Hunt: - Register an email without verifying it. - Register again using a different method (e.g., 'sign up with Google') with the same email. - Check if the application links both accounts. - Try logging in to see if you can access information from the other account. 2. Account Takeover due to Improper Rate Limiting - How to Hunt: - Capture the login request. - Use tools like Burp Suite's Intruder to brute-force the login. - Analyze the response and length to detect anomalies. 3. Account Takeover by Utilizing Sensitive Data Exposure - How to Hunt: - Pay attention to the request and response parts of the application. - Look for exposed sensitive data like OTPs, hashes, or passwords. 4. Login Vulnerabilities - Check for: - Brute-force vulnerabilities. - OAuth misconfigurations. - OTP brute-forcing. - JWT misconfigurations. - SQL injection to bypass authentication. - Proper validation of OTP or tokens. 5. Password Reset Vulnerabilities - Check for: - Brute-force vulnerabilities in password reset OTPs. - Predictable tokens. - JWT misconfigurations. - IDOR vulnerabilities. - Host header injection. - Leaked tokens or OTPs in HTTP responses. - Proper validation of OTP or tokens. - HTTP parameter pollution (HPP). 6. XSS to Account Takeover - How to Hunt: - Try to exfiltrate cookies or auth tokens. - Craft XSS payloads to change user email or password. 7. CSRF to Account Takeover - Check for: - Vulnerabilities in email update endpoints. - Vulnerabilities in password change endpoints. 8. IDOR to Account Takeover - Check for: - Vulnerabilities in email update endpoints. - Vulnerabilities in password change endpoints. - Vulnerabilities in password reset endpoints. 9. Account Takeover by Response & Status Code Manipulation- How to Hunt: - Look for vulnerabilities where manipulating response or status codes can lead to account takeover. 10. Account Takeover by Exploiting Weak Cryptography- Check for: - Weak cryptographic implementations in password reset processes. 11. Password or Email Change Function- How to Hunt: - If you see email parameters in password change requests, try changing your email to the victim's email. 12. Sign-Up Function- How to Hunt: - Try signing up with the target email directly. - Use third-party sign-ups with phone numbers, then link the victim's email to your account. 13. Rest Token - How to Hunt: - Try using your REST token with the target account. - Brute 13. Rest Token- How to Hunt: - Try using your REST token with the target account. - Brute force the REST token if it is numeric. - Try to figure out how the tokens are generated. For example, check if they are generated based on timestamp, user ID, or email. 14. Host Header Injection- How to Hunt: - Intercept the REST account request. - Change the Host header value from the target site to your own domain (e.g., `POST /PassRest HTTP/1.1 Host: Attacker.com`). 15. CORS Misconfiguration to Account Takeover - How to Hunt: - Check if the application has CORS misconfigurations. - If so, you might be able to steal sensitive information from the user to take over their account or make them change authentication information. - Refer to [CORS Bypass](https://book.hacktricks.xyz/pentesting-web/cors-bypass) for more details. 16. Account Takeover via Leaked Session Cookie - How to Hunt: - Look for vulnerabilities where session cookies are leaked. - Refer to [HackerOne Report 745324](https://hackerone.com/reports/745324) for more details. 17. HTTP Request Smuggling to ATO- How to Hunt: - Look for HTTP request smuggling vulnerabilities. - Refer to [HackerOne Reports 737140 and 740037](https://hackerone.com/reports/737140) and [HackerOne Report 740037](https://hackerone.com/reports/740037) for more details.