The Google password manager form overlaps fullscreen mode warnings, which could lead to address bar phishing.
Categories
(Firefox for Android :: Autofill, defect, P3)
Tracking
()
People
(Reporter: Laraweron, Assigned: polly)
References
Details
(Keywords: csectype-spoof, reporter-external, sec-moderate, Whiteboard: [client-bounty-form][adv-main130-])
Attachments
(4 files)
When a user enters their login and password into the authentication form, a prompt appears suggesting to save their credentials. In my case, two prompts appear. If we add a fullscreen mode activation function to the authentication button, the browser will not block such behavior.
We can also implement a double-click on the button: the first click activates fullscreen mode, and the second click sends the authentication request. I can provide an example of such implementation upon request.
Comment 2•1 year ago
|
||
This appears to be a Google password saving dialog, not ours, which is a recent Android feature. It looks similar to the WebAuthn one when you can't read the text :-)
You can decline this so it would not affect every user, but it will probably be pretty popular if it does a decent job. It might show up if you're on a page where you've already saved a password. This attack seems to rely on the user entering a password on a page they have not saved a password for, which would be extremely unusual if it's the attacker's site. Maybe it's a phishing site and the user already thinks they're somewhere else, but then they've entered their password and you've already won. What's the value of spoofing fullscreen at that point?
I apologize for the poor implementation example, it is indeed a bad practice to ask users to enter their login and password on an unknown website. I have changed the code so that users no longer need to enter their login and password. I have also hidden the fields.
Comment 5•1 year ago
|
||
Ah, right. Thanks. I'll increase the rating.
Updated•1 year ago
|
Comment 6•1 year ago
|
||
Polly has been working on a proposal for a way to fix all those issues more reliably. We'll bring more details here as soon as we have some results.
Updated•1 year ago
|
| Assignee | ||
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Comment 8•1 year ago
|
||
This bug will be referenced in the advisory for the fix (bug 1902996)
Updated•9 months ago
|
Description
•