iframe sandbox on Android allows opening to external protocol (including `intent:`)
Categories
(GeckoView :: General, defect, P2)
Tracking
(firefox142 wontfix, firefox143 wontfix, firefox144 fixed)
People
(Reporter: haxatron1, Assigned: boek)
References
Details
(Keywords: csectype-mitigation-bypass, reporter-external, sec-moderate, Whiteboard: [reporter-external][geckoview:m113][group1][adv-main144+])
Attachments
(4 files)
iframe sandbox requires one of the following to open external protocol. (ref: https://chromestatus.com/feature/5680742077038592)
- allow-popups
- allow-top-navigation
- allow-top-navigation-with-user-activation
- allow-top-navigation-to-custom-protocols
On Firefox for Android, iframe sandbox requires none. Compare this to Firefox for Desktop where it is correctly blocked.
STR:
Go to external.html and click the link. You will open Phone app.
Expected: Phone app not opened because none of the required attributes are not set.
Updated•3 years ago
|
Comment 2•3 years ago
•
|
||
We need to investigate this and find out why this is different from desktop (something not implemented? a bug?). We already have several bugs that seem to be related to this, and we need to improve our iframe support. Nominating this for the next sprint
Updated•3 years ago
|
Comment 3•3 years ago
|
||
This is essentially the same thing as bug 1791312, but since intents and external protocol handlers are different mechanisms internally it's probably safest to track each separately lest one be forgotten.
I would say this bug is a dependency of bug 1791312. Reason being that even if intent URLs were to follow the 4 attribute listed, a fallback intent initiates a top-navigation. This effectively means that:
-
Enabling allow-popups implies that a sandboxed iframe can cause a top navigation if they want to which would eliminate the sandbox flags.
-
allow-top-navigation-to-custom-protocol now becomes allow-top-navigation by abusing intent fallbacks.
Updated•3 years ago
|
Comment 5•3 years ago
|
||
The severity field is not set for this bug.
:cpeterson, could you have a look please?
For more information, please visit auto_nag documentation.
| Comment hidden (obsolete) |
Updated•3 years ago
|
Updated•3 years ago
|
Comment 7•3 years ago
|
||
Dropping to P2 because Irene says she's not actively working on this bug.
Updated•2 years ago
|
Comment 8•2 years ago
|
||
Just to make it clear, intent: is an external protocol. But because android <gestures>, we should explicitly test to make sure it's blocked also once this is fixed.
Updated•2 years ago
|
Updated•2 years ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
| Assignee | ||
Updated•11 months ago
|
| Assignee | ||
Comment 13•11 months ago
|
||
Updated•11 months ago
|
Comment 14•11 months ago
|
||
We discussed this on Slack, where I gave some feedback which led to the patch in comment 13. Clearing ni?
| Assignee | ||
Comment 15•11 months ago
|
||
Comment 16•11 months ago
|
||
Comment 17•11 months ago
|
||
Updated•10 months ago
|
Comment 18•10 months ago
|
||
Comment 19•10 months ago
|
||
Comment 20•10 months ago
|
||
Backed out for causing lint failures @NavigationDelegateTest.kt:
Comment 21•10 months ago
|
||
| Assignee | ||
Updated•10 months ago
|
Comment 22•10 months ago
|
||
Updated•9 months ago
|
Comment 23•9 months ago
|
||
Updated•9 months ago
|
Updated•3 months ago
|
Description
•