A simple OTP bypass resulted in a €2,000 bounty.
1. Request some OTP codes.
2. Test one of them randomly.
3. If accepted, try to bypass the OTP request limit.
How the exploit works: enter victim's email, request 99999 OTP codes, then submit any random code like 77777 and log in.
$2000 for a web cache deception bug. As always I share my methodology 👇
Identifying a deception bug is always easy but exploiting it can be hard due to SameSite restrictions on victims cookie
I bypassed this to steal victim JWT. Read about it here:
🔗 https://t.co/CAxfKAC0eP
Found a cool bug at Meta.
From misconfigured Grafana instance to R/W access on 507 private Meta repositories.
Wrote up the full chain here:
https://t.co/LYQ0prc68d
$157k bounty awarded by @metabugbounty
If the admin panel you targeted has a username enumeration , you can brute-force using a wordlist. This has worked many times for me in this case, the username was "admin"
My password wordlists:
Basic: https://t.co/dwZXsZISiJ
Advance: https://t.co/2AvuC5qTqz
Usernames wordlist:
https://t.co/cKCjZbmS39
#bugbountytips #bugbounty
@arth_bajpai@Fabrikat0r Actually it's two different programs not https://t.co/PtjFM8J6xc & https://t.co/t3AFPjMGeN it's like https://t.co/mZbeRZ9x37 & https://t.co/YTcZlcXcOp. Anyways they just closed it as informative but thanks for explanation
IDK why informative? The web restrict users from email changing and I bypassed it completely and still they are saying informative. What is this logic ? If I'm wrong on this, hunters can change me.
#bugbountytips#bugbounty#hackerone
Got invited to 2 similar prgms on @Hacker0x01 1 tested earlier & 1 recently. Noticed both used identical APIs, but only the newer prgm allowed email changes. By swapping its endpoint into the older prgm, I bypassed the restriction & successfully changed the email
#bugbountytips