• Now, if you are slightly experienced, after a few minutes of tinkering with this workflow, you will get a feeling whether it might have something interesting going on or not. This point is difficult to explain. It will come with practice.
🧵:👇
• The weird behavior doesn’t necessarily mean you have found a bug that is worth reporting. It probably means you have a good chance so you should keep digging into it more.
🧵:👇
• There is some research that might be required as well. Let’s say you found that a particular version of an email server is being used that is outdated. Look on the internet for known vulnerabilities against it. You might encounter a known CVE with a known exploit.
Try that exploit and see what happens (provided you are operating under the terms and conditions of the bug bounty).
• There might be special tools that are required. Explore into that, if possible.
Remember, Burp is a swiss army knife but you might have to use certain specific tools in certain cases. Always, be aware of that.
• After spending a few hours on this, if you think you have exhausted all your options and are not getting anything meaningful out of it,
stop and move on. Getting hung up on something is the biggest motivation killer but that doesn’t mean you are giving up. Get back to it later if something else comes up. Make a note of it.
🧵:👇
• Something that has worked for me is bounds checking on parameters, pick a parameter that has an obvious effect on the flow of the application.
For example, if a field takes a number (lets call it ID for lulz).
What happens if :
-you put in a minus number?
-you increment or decrement the number?
-you put in a really large number?
-you put in a string or symbol characters?
-you try traverse a directory with …/
-you put in XSS vectors?
-you put in SQLI vectors?
-you put in non-ascii characters?
-you mess with the variable type such as casting a string to an array
-you use null characters or no value
I would then see if I can draw any conclusions from the outcomes of these tests,
-see if I can understand what is happening based on an error
-is anything broken or exposed
-can this action affect other things in the app.
You Will Get :
➡Best Tips for Bug Bounty
➡Good And Informative Articles From Infosec Community
➡One-liners Command
➡Infosec Resources
➡ebooks - Paid ?😎
➡And Many More
☑ Establish how session management is handled in the application (eg, tokens in cookies, token in URL)
☑ Check session tokens for cookie flags (httpOnly and secure)
☑ Check session cookie scope (path and domain)
Thread🧵(1/n) :👇
☑ Check session cookie duration (expires and max-age)
☑ Check session termination after a maximum lifetime
☑ Check session termination after relative timeout
☑ Check session termination after logout
☑ Test to see if users can have multiple simultaneous sessions
🧵(2/n) :👇
☑ Test session cookies for randomness
☑ Confirm that new session tokens are issued on login, role change and logout
☑ Test for consistent session management across applications with shared session management
☑ Test for session puzzling
☑ Test for CSRF and clickjacking
• Bug Bounty Hunting Tip #1- Always read the Source Code
How To Approach a Target - Thread🧵:👇
Approach a Target (Lot of this section is taken from
Jason Haddix and portswigger blog)
• Ideally you wants to choose a program that has a wide scope. You’re also going to be wanting to look for a bounty program that has wider range of vulnerabilities within scope.
• Mining information about the domains, email servers and social network connections.
—————————
I've opened My Bug Bounty tips Group =>
Join Link : t.me/bugbountyresou…
—————————