Lesson learned :
- If you want consistent income, bug bounty might not be the best fit (in my opinion).
- Don’t take it personally. Even if you’re sure your report has a security impact, the final decision is up to the program owner.
- Just submit it, move on, and forget it!
Bug bounty is unpredictable.
Here’s my real story:
2023:
- Submitted the report
- Closed as “Informative”
2026:
- Reopened 🙂 (I almost forgot what the report even looked like)
- Triaged
- Received a bounty reward
From rate-limit to ATO.
TLDR; Broken authentication - exploiting reset passwd endpoint.
Tips: Coloring your POC script to looks like 1337 hackrzzz and showing the greater impact for client. 😅😊
I'm using projectdiscovery data to built bounty search target test with typesense.
Here are some of the things i'm interested in
- lightning fast
- search-as-you-type
- highlighting
- auto-correction
✌️
- Directory bruteforcing
- Found .zip file, containing backup apps.
- Found credentials in config.php file.
- Try to login admin panel with it. Success! Apps compromised!
Escalating:
- Try to login creds for ssh also works! and it has root priv.
Game over!