Email Bypass

• At password reset pages always try manipulating HOST header, you might get lucky and find that the password reset URL contain your own host instead of the original domain name. Just got easy 500$ for this stupid bug.

• bugbountytip: if a website does not verify email, try signing up with <whatev>@domain.com (the company email). Sometimes this gives you higher privilege like deleting/viewing any other user's profiles etc.

• Do you have any problem with creating a new account in some application due to requirement of business email (corp)? Solution is here: #Burp Collaborator. Create an account with [e-mail] and look after SMTP request at your client. #Security #bugbountytip #webapp

• Just found an interesting bug.. can you invite other users (via email usually) to xyz? Try the invite link on a different account and see what happens. In my case, it auto leaked my other accounts email to me. (no prompts to accept invite, didn't validate user) #BugBountyTips

• Ever signup for a service and your account needs approval? Try reset your password as sometimes it bypasses the approval process.. :D #bugbountytips

• #bugbountytip If you can send letters from your email [e-mail], try to substitute your email with company employers or other users email in the request. You can find it with http://hunter.io or reg another acc. For me, it worked a few times in private BB.

• #BugBountyTip: Always remember to check emails for access control issues. Sometimes the same access control is not applied when sending emails. Thanks@gitlab for the bounty!Quote Tweet

• [Tip]

  Create many accounts with one email :D

  A lot of web apps treat [e-mail] and [e-mail] as different emails but actually the emails sent to [e-mail] will be received by [e-mail] because gmail considers them the same email address.

• -Weird bug I found yesterday -victim has email as [e-mail] -i signed up with [e-mail] - deleted my account and victim account got deleted too #bugbountytip

• Another example of two systems handling data differently and how it can be exploited. tl;dr<[e-mail]>[e-mail] is submitted as the email address Email is sent to [e-mail] [e-mail] gets registered

• https://nathandavison.com/blog/exploiting-email-address-parsing-with-aws-se

https://twitter.com/intigriti/status/1272860780694843392?s=20

• Validate your email address with the payload you can here: - https://twitter.com/Haoneses/status/1292456202857742338?s=20

• http://sphinx.mythic-beasts.com/~pdw/cgi-bin/emailvalidate

• 1.Account setting page: Update new Email: Normal: "Email":"[e-mail]" (200 OK) New: "Email":"[e-mail]" (error msg : u can't change the email [e-mail] ) New Update: "Email":" [e-mail] " (200 OK) just add space Bounty: 500$ #bugbountytips #hackerone