Example:
1) Fraudster create an account and put in a bogus card number.
2) Fraudster changes account email address to [email protected]. [email protected] already exists in Netflix's DB - but [email protected] does not, so Netflix is ok with this.
3) Netflix emails [email protected] and says "hey your card is bad, please update it" by clicking here.
4) The real [email protected] receives the email, clicks the link and is taken directly to a "update your card screen" and types in their credit card information.
5) Fraudster has their Netflix account paid for by the real Joe Smith.
Granted, Netflix could fix this by requiring a login before updating billing details. But the dot aliases in Gmail are a part of the scam.
Rule #1 of security: trust nothing from the client!
If the user clicks a link in the email they won’t be able to log in to that account to confirm the change.
If the user navigates to Netflix themselves they won’t have anything to confirm in their own account.
Also Netflix gets partial responsibility for accepting email validation via a different browser session. Unfortunately it’s either that or have people constantly complain they can’t validate their emails from their phone yet browse on a different device.
Middle ground may be IP address check so if you’re on the same WiFi it’ll work. Of course IPv6 kills that.
1) https://jameshfisher.com/2018/04/07/the-dots-do-matter-how-t...
Besides, even without a magic link, they could still phish you into clicking a link to a malicious page that performed a login-csrf which would have the same effect.
Given standard password flows include email-based password reset, there's really no difference in security; either way, if someone owns your email, you're screwed. TFA does help mitigate this though.
This isn't just Gmail - outlook also has "plus aliases", and unless the web developer handles these you can simply sign up with "[email protected]" and perform the same attack.
It might be better to look at solutions that actually fix the underlying issue - like requiring a login.
Imagine what would happen if we let this kinda sloppiness play loose on DNS instead. Terrifying, right?
So why do we allow google to mangle standard internet email?
https://gmail.googleblog.com/2008/03/2-hidden-ways-to-get-mo...
Fuck that shit!
Oh... We should only give Google and Gmail a free pass because they’re big?
No, fuck that too. That’s not how internet standards and internet emailing works.
It’s level playing field because everyone plays by the rules, and when you cause fuck-ups like this, it’s entirely on your base.
Gmail is the one who needs fixing, not everyone else.
Websites should be validating email addresses by sending them an email with an (expiring quickly) link and having the user act upon it. Short of that there’s no way for you to know that a user controls a given address.
That’s grossly irresponsible. Let the users who needs aliases enable them explicitly and manage them themselves.
Regardless that’s no excuse for shitty software and websites that don’t follow standards. Literally anything before the @ sign is fair game to be interpreted by the email server as it sees fit. That include emojis, case sensitive names, and most punctuation.
Assuming email addresses are unique because the text is unique is simply wrong.
If you have catch-all service forwarding your email, you as a technically minded person made that choice for your domain and you have to consider the consequences and risks.
Gmail has made this a default for everyone, including 99.999999% of its users who does not know scammers can automatically create aliases for them, so that the 0.0000001% which uses this feature doesn’t have to tick a checkbox first, or pre-register their aliases.
Completely irresponsible and a world of difference.
I'm sure there are creative & compelling uses of Gmail dot addresses to commit fraud out there, but this one barely counts as fraud. I'm not sure what the point of the article is.