Autofill clickjacking Leads to Credit Card Leak
Categories
(Toolkit :: Form Autofill, defect, P2)
Tracking
()
People
(Reporter: ameenbasha111, Assigned: dimi)
References
Details
(Keywords: csectype-clickjacking, reporter-external, sec-low, Whiteboard: [client-bounty-form] [adv-main139+] [adv-esr128.11+])
Attachments
(5 files)
HI team, Firefox latest on windows is vulnerable for autofill tapjackking which allows the attacker to trick the victim to leak the saved card details
Steps to reproduce
- Host and open the html file on firefox latest
- Click the button rapidly (after 7th click the attack starts)
- you can see the credit card details are leaked
Note: for poc i have alerted the details. if not, the victim will not even aware of this attack other than just a seconds of dropdown shown.
I have attached the poc video and html file for reference
| Reporter | ||
Comment 1•1 year ago
|
||
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Comment 2•1 year ago
|
||
Emma: perhaps my question in bug 1954262 really belongs in this bug.
Comment 3•1 year ago
|
||
I've answered most of the questions there. One thing to add: while the autofill UI seems to have a security delay, the security delay is not extended when the user clicks it while the element is disabled. This is important to mitigate attacks like the one described in this bug where a user ist told to spam click.
Comment 4•1 year ago
|
||
The severity field is not set for this bug.
:dimi, could you have a look please?
For more information, please visit BugBot documentation.
Updated•1 year ago
|
| Assignee | ||
Comment 6•1 year ago
|
||
I'll work on a fix that:
- Only shows the autocomplete popup for real user events.
- Renews the autocomplete popup secure delay when users click the popup while the element is disabled.
| Assignee | ||
Comment 7•1 year ago
|
||
| Assignee | ||
Updated•1 year ago
|
Comment 9•1 year ago
|
||
Updated•1 year ago
|
Updated•1 year ago
|
| Assignee | ||
Comment 10•1 year ago
•
|
||
Although "leave-open" was set, the bug was still closed after the patch landed. Chatted with :Ryan, and he suggested filing another bug to track the remaining issue.
Filed Bug 1963301 for the fix of the "Only show the autocomplete popup for real user events" part.
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
| Assignee | ||
Comment 12•1 year ago
|
||
(In reply to Ryan VanderMeulen [:RyanVM] from comment #11)
Did you want to nominate this for ESR128 uplift?
The fix itself is not very complicated, so I think we could uplift it. However, since this has been triaged as sec-low,
I’m not sure if it's necessary.
Simon, from the security team's perspective, do you think we should uplift this to ESR128?
Comment 13•1 year ago
|
||
The fix seems tiny and local so I would suggest uplifting.
| Assignee | ||
Comment 14•1 year ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D246212
Updated•1 year ago
|
Comment 15•1 year ago
|
||
firefox-esr128 Uplift Approval Request
- User impact if declined: Vulnerable to autofill clickjacking if users are tricked into repeatedly clicking.
- Code covered by automated testing: no
- Fix verified in Nightly: yes
- Needs manual QE test: no
- Steps to reproduce for manual QE testing:
- Risk associated with taking this patch: Low
- Explanation of risk level: The fix itself is straightforward and not complicated
- String changes made/needed: no
- Is Android affected?: no
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Reproduced the issue on Firefox 138.0a1 (2025-03-14) on Windows 11 by following the infos provided in Comment 0.
The autocomplete popup secure delay is fixed on Firefox 139.0b7 and Firefox 140.0a1 (2025-05-12).
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Comment 17•1 year ago
|
||
| uplift | ||
Verified this as well on Firefox 128.11.0 ESR on Windows 11.
Updated•1 year ago
|
Comment 19•1 year ago
|
||
Updated•9 months ago
|
Updated•4 months ago
|
Updated•3 months ago
|
Description
•