Closed Bug 1954137 (CVE-2025-5267) Opened 1 year ago Closed 1 year ago

Autofill clickjacking Leads to Credit Card Leak

Categories

(Toolkit :: Form Autofill, defect, P2)

defect

Tracking

()

VERIFIED FIXED
139 Branch
Tracking Status
firefox-esr115 --- wontfix
firefox-esr128 139+ verified
firefox137 --- wontfix
firefox138 --- wontfix
firefox139 + verified
firefox140 --- verified

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)

Attached file test.html

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

  1. Host and open the html file on firefox latest
  2. Click the button rapidly (after 7th click the attack starts)
  3. 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

Flags: sec-bounty?
Summary: Autofill Tapjackking Leads to Credit Card Leak → Autofill Tapjacking Leads to Credit Card Leak
Component: Security → Form Autofill
Product: Firefox → Toolkit
Summary: Autofill Tapjacking Leads to Credit Card Leak → Autofill clickjacking Leads to Credit Card Leak
See Also: → 1650961
See Also: → 1399356

Emma: perhaps my question in bug 1954262 really belongs in this bug.

Flags: needinfo?(emz)

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.

Flags: needinfo?(emz)

The severity field is not set for this bug.
:dimi, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(dlee)
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: sec-moderate
Duplicate of this bug: 1958732
No longer duplicate of this bug: 1958732

I'll work on a fix that:

  1. Only shows the autocomplete popup for real user events.
  2. Renews the autocomplete popup secure delay when users click the popup while the element is disabled.
Assignee: nobody → dlee
Severity: -- → S3
Status: NEW → ASSIGNED
Flags: needinfo?(dlee)
Priority: -- → P2
Keywords: leave-open
Pushed by dlee@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/c1e9a6e513dc refresh timer when needed r=NeilDeakin
Group: firefox-core-security → core-security-release
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 139 Branch
Depends on: 1963301

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.

QA Whiteboard: [qa-triage-done-c140/b139] [qa-verif-needed-c140/b139]
Flags: qe-verify+
QA Whiteboard: [qa-triage-done-c140/b139] [qa-verif-needed-c140/b139] → [sec] [qa-triage-done-c140/b139] [qa-verif-needed-c140/b139]
Flags: sec-bounty? → sec-bounty+

Did you want to nominate this for ESR128 uplift?

Flags: needinfo?(dlee)

(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?

Flags: needinfo?(dlee) → needinfo?(sfriedberger)

The fix seems tiny and local so I would suggest uplifting.

Flags: needinfo?(sfriedberger)
Attachment #9486608 - Flags: approval-mozilla-esr128?

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
Attachment #9486608 - Flags: approval-mozilla-esr128? → approval-mozilla-esr128+
Attachment #9486608 - Flags: approval-mozilla-esr128+ → approval-mozilla-esr128-
QA Whiteboard: [sec] [qa-triage-done-c140/b139] [qa-verif-needed-c140/b139] → [sec] [qa-triage-done-c140/b139] [qa-verif-needed-c140/b139] [uplift]

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).

Attachment #9486608 - Attachment description: Bug 1954137 - refresh timer when needed r=NeilDeakin → Bug 1954137 - refresh timer when needed
Attachment #9486608 - Flags: approval-mozilla-esr128- → approval-mozilla-esr128?
Attachment #9486608 - Flags: approval-mozilla-esr128? → approval-mozilla-esr128+

Verified this as well on Firefox 128.11.0 ESR on Windows 11.

Status: RESOLVED → VERIFIED
QA Whiteboard: [sec] [qa-triage-done-c140/b139] [qa-verif-needed-c140/b139] [uplift] → [sec] [qa-triage-done-c140/b139] [qa-verif-done-c140/b139] [uplift]
Flags: qe-verify+
Whiteboard: [client-bounty-form] → [client-bounty-form] [adv-main139+] [adv-esr128.11+]
Group: core-security-release
See Also: → CVE-2026-8961
Alias: CVE-2025-5267
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: