Select option appears in different origin if user manually opens a new tab with the keyboard or the webpage is allowed popups (window.open)
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
People
(Reporter: sas.kunz, Assigned: Gijs)
References
Details
(Keywords: csectype-spoof, reporter-external, sec-low, Whiteboard: [adv-main130-][adv-esr128.2-][client-bounty-form])
Attachments
(6 files, 1 obsolete file)
|
2.44 MB,
video/mp4
|
Details | |
|
2.90 KB,
text/html
|
Details | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-beta+
|
Details | Review |
|
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-esr128+
|
Details | Review |
after https://bugzilla.mozilla.org/show_bug.cgi?id=1875354 is fixed the select option will close in a new window or new tab but this can be bypassed by pressing ctrl + t (opens a new tab)
steps to reproduce
- open sf.html
- click on "click me"
- press Ctrl + T to new tab
OS: windows 10
| Assignee | ||
Comment 2•2 years ago
|
||
This is trivially fixable by using tabspecific=true on the ContentSelectDropdown element.
| Assignee | ||
Comment 3•2 years ago
|
||
Updated•2 years ago
|
Comment 4•2 years ago
|
||
This doesn't seem that bad to me. The interaction is a bit weird, and I don't see how you are confusing people much by having it on top of the about:new tab page, so the user would have to have a custom page, which of course the attacker can't tell.
| Assignee | ||
Comment 5•2 years ago
|
||
Comment 6•2 years ago
|
||
Comment 7•2 years ago
|
||
Thank you for reporting this variation. As a sec-low bug it does not qualify for our bounty unfortunately
Updated•2 years ago
|
Updated•2 years ago
|
Comment 8•2 years ago
|
||
Please nominate this for ESR128 approval when you get a chance.
| Assignee | ||
Comment 9•2 years ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D217232
Updated•2 years ago
|
Comment 10•2 years ago
|
||
esr128 Uplift Approval Request
- User impact if declined: Spoofing/confusion around select popups
- Code covered by automated testing: no
- Fix verified in Nightly: no
- Needs manual QE test: yes
- Steps to reproduce for manual QE testing: see comment 0
- Risk associated with taking this patch: low
- Explanation of risk level: single attribute on the select dropdown
- String changes made/needed: no
- Is Android affected?: no
| Assignee | ||
Comment 11•2 years ago
|
||
Comment on attachment 9419867 [details]
Bug 1909163 - mark select dropdown as tabspecific, r?emilio
So digging into this, I'm realizing this patch doesn't actually work.
| Assignee | ||
Updated•2 years ago
|
| Assignee | ||
Updated•2 years ago
|
Updated•2 years ago
|
| Assignee | ||
Comment 12•2 years ago
|
||
Comment 13•2 years ago
|
||
Updated•2 years ago
|
Comment 14•2 years ago
|
||
| Assignee | ||
Comment 15•2 years ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D219618
Updated•2 years ago
|
Comment 16•2 years ago
|
||
beta Uplift Approval Request
- User impact if declined: spoofy select dropdowns
- Code covered by automated testing: no
- Fix verified in Nightly: no
- Needs manual QE test: yes
- Steps to reproduce for manual QE testing: see comment 0
- Risk associated with taking this patch: low
- Explanation of risk level: minor changes to select popup attributes
- String changes made/needed: no
- Is Android affected?: no
Updated•2 years ago
|
Updated•2 years ago
|
Comment 17•2 years ago
|
||
| uplift | ||
Updated•2 years ago
|
Comment 18•2 years ago
|
||
I managed to reproduce the issue on Firefox 129.0.2, under Windows 11.
The issue is no longer reproducible on Firefox 130.0b8(treeherder build), or on Firefox 131.0a1.
Tests were performed under Windows 11x64, macOS 10.15 and Ubuntu 22.04.
Updated•2 years ago
|
| Assignee | ||
Comment 19•2 years ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D217232
Updated•2 years ago
|
Comment 20•2 years ago
|
||
esr128 Uplift Approval Request
- User impact if declined: Confusing select dropdowns
- Code covered by automated testing: no
- Fix verified in Nightly: yes
- Needs manual QE test: yes
- Steps to reproduce for manual QE testing: See earlier comments
- Risk associated with taking this patch: Low
- Explanation of risk level: Minor JS changes, already verified in nightly
- String changes made/needed: No
- Is Android affected?: no
Updated•2 years ago
|
Comment 21•2 years ago
|
||
| uplift | ||
Updated•2 years ago
|
Comment 22•2 years ago
|
||
Managed to verify the issue on Firefox 128.2.0ESR on Windows 10 and Windows 11.
Updated•2 years ago
|
Comment 23•2 years ago
|
||
The Select Element didn't support showPicker() until bug 1854112
Updated•2 years ago
|
Updated•1 year ago
|
Description
•