1863831 working on latest 122 iOS Firefox Focus via Apple default apps like iOS Mail App
Categories
(Focus :: Security: iOS, defect)
Tracking
(Not tracked)
People
(Reporter: proof131072, Unassigned)
References
Details
(Keywords: csectype-sop, reporter-external, sec-high, Whiteboard: [reporter-external] [client-bounty-form] [verif?])
We are able to reproduce it via Apple default apps like iOS Mail App.
- Open https://pwning.click/googleloc.php and immediately leave the browser
2, Open Gmail and type in an Email Title: The first ever YouTube video
-
"Text to display": https://www.youtube.com/watch?v=jNQXAC9IVRw
-
"Link to: Web address": firefox-focus://open-url?url=javascript:document.write(document.domain)
-
Send this to your iOS Apple Mail App sync'd email account address
Of course, the link could be any legitimate link instead like https://google.com, https://apple.com etc.
Updated•1 year ago
|
Updated•1 year ago
|
The following steps are also another way to reproduce this issue (using Safari and provided links instead of Gmail) as seen in 1863831
Steps to reproduce
- Navigate to https://pwning.click/googleloc.php
- Leave Focus application (by moving it to background)
- Open Safari
- Navigate to https://pwning.click/focuslink.php in Safari
- Click on the link "Open with Firefox Focus"
Actual behavior
Focus is opened and JavaScript is running
Expected behavior
Focus is opened and JavaScript should not be running
Updated•1 year ago
|
Comment 4•1 year ago
|
||
This says it's a variant of bug 1863831, but tested in v122 while that bug appears to have been fixed in v123 (I think? checking on that). Is this perhaps exactly the same and is now fixed?
Updated•1 year ago
|
bug 1863831 was fixed on v122 https://github.com/mozilla-mobile/focus-ios/pull/3973
But I confirmed bug 1863831 and bug 1880745 were properly fixed on v123 for some reason.
Please confirm this report worked up to Focus v122.1 like we can check from this demo video link https://pwning.click/RPReplay_Final1708482262.mp4 despite the fix for v122 https://github.com/mozilla-mobile/focus-ios/pull/3973
Sorry for the needinfo here, I just want to make sure that we confirm the above comment.
(In reply to James Lee from comment #6)
Please confirm this report worked up to Focus v122.1 like we can check from this demo video link https://pwning.click/RPReplay_Final1708482262.mp4 despite the fix for v122 https://github.com/mozilla-mobile/focus-ios/pull/3973
(In reply to James Lee from comment #7)
Sorry for the needinfo here, I just want to make sure that we confirm the above comment.
(In reply to James Lee from comment #6)
Please confirm this report worked up to Focus v122.1 like we can check from this demo video link https://pwning.click/RPReplay_Final1708482262.mp4 despite the fix for v122 https://github.com/mozilla-mobile/focus-ios/pull/3973
Ah, I'll cancel needinfo since I should've added them on bug 1880745
Ah my bad, #c7 is correct; this is another one that was also fixed on v123 for some reason.
Sorry for the needinfo here, I just want to make sure that we confirm the above comment.
(In reply to James Lee from comment #6)
Please confirm this report worked up to Focus v122.1 like we can check from this demo video link https://pwning.click/RPReplay_Final1708482262.mp4 despite the fix for v122 https://github.com/mozilla-mobile/focus-ios/pull/3973
Comment 10•1 year ago
•
|
||
Hello, I tested in v123 and indeed it seems like this issue was fixed (we load a search with the "javascript" rather than running the javascript itself). Let me know if you think otherwise. Thank you!
Updated•9 months ago
|
Comment 11•6 months ago
|
||
Should this be marked as a duplicate, and/or fixed?
Comment 13•4 months ago
•
|
||
Per above comments it appears this was fixed in v123; it seems like we can safely close this, however if anyone has concerns that there are still remaining issues here please let me know. I'm not entirely sure why it wasn't closed earlier, it looks like it may be that it was resolved as a side-effect of a separate set of changes in Focus.
Comment 14•4 months ago
|
||
Note: Bugzilla does not allow me to set the Fix field to the applicable version (it only appears to provide the 3 most recent versions as options). @dveditz Is there any way to properly set that field in the ticket at this point?
Comment 15•4 months ago
|
||
(In reply to mreagan from comment #14)
Note: Bugzilla does not allow me to set the Fix field to the applicable version [...] @dveditz Is there any way to properly set that field in the ticket at this point?
Not really, short of asking admins to force it in there. But since there's no separate fix responsible for this it seems to be a dupe after all
Updated•3 months ago
|
Updated•3 months ago
|
Description
•