4 ms·
This is actually kind of a vulnerability in itself. It would be very easy for a competitor or random bag of dicks to cause your server to flood an email server
by marginalia_nu 5y ago
This is actually kind of a vulnerability in itself.
It would be very easy for a competitor or random bag of dicks to cause your server to flood an email server with emails. Not that this will harm the recipient server, but you can easily find your email server blacklisted because of it, effectively locking every single one of your users out of their accounts.
I don't know what's a good mitigation strategy, since this can come from a botnet. Maybe just a global rate limit across all users that allows for some bursts.
- istjohn 5y agoHow is this any more of a problem than the conventional password reset email?
- marginalia_nu 5y agoIf you try to reset your password too often, especially without logging in, you often end up with a "try again in 48 hours or contact support here", to prevent this type of attack. That doesn't really work if this is how you log into your account. The expected rate of these emails is much higher, so you can't be as restrictive in sending them out. Another difference is that the ramifications are much bigger. If your password reset doesn't work, the minuscule fraction of users that can't remember their password can't log in. In this scheme, none of your users can log in.
- k__ 5y agoWhy not limit it to one email every five minutes or something?
- marginalia_nu 5y agoWell let's hypothesize I have a botnet and either I've spent a few months creating accounts, or I just have a list of email addresses from some breached site, and my army of 30,000 color changing lightbulbs and smart fridges are spamming login requests as fast as you'll let them. That's still a lot of emails even if just some are legit. Your option at that point is basically shutting down logins for everyone, or find yourself blacklisted.