Detecting Cross-Origin Redirect Using Iframe Load Events
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
People
(Reporter: fazim.pentester, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: reporter-external, Whiteboard: [reporter-external] [client-bounty-form] [verif?])
Attachments
(3 files)
In Firefox browser, we can identify whether a cross-origin redirect has occurred by checking the number of times the iframe load event is fired. Here, I have identified different conditions where this has leaked if a site has redirected the user:
- The first iframe uses a meta redirect condition.
- The second and third frames detect redirection when a user clicks a link on that website.
Step to reproduce:
- Download the attached poc.html.
- Host the poc.html on a local server using
python3 -m http.server 8080
. - Open
http://localhost:8080/poc.html
in the latest firefox browser and open the console/devtools for testing. - When the first iframe automatically redirects, the redirect will be detected and you can see it in the devtools.
- In the second and third steps, click the link inside the iframe and observe that this is also detected.
Reporter | ||
Comment 1•6 months ago
|
||
Reporter | ||
Comment 2•6 months ago
|
||
Updated•6 months ago
|
Comment 3•6 months ago
|
||
This sounds a bit like Bug 1741034, but a big difference is that we don't know where we'de redirected, just that we have redirected. As far as I can tell Chrome behaves like this as well. Hsin-Yi, you gave Bug 1741034 an S3, do you have a feeling about this? Also, is this a security issue to begin with?
Comment 4•6 months ago
|
||
We don't really know where we're redirected in bug 1741034 either. On a specific target site you could know a redirect goes here and if it doesn't redirect it goes there, but we're not actually leaking the destination. That's the same as in this report.
Updated•6 months ago
|
Reporter | ||
Comment 5•6 months ago
|
||
I still don't believe this issue is a duplicate of the one mentioned. I have provided a few additional methods that are not included in the opened bug. I have also reported this to Chrome, where it is currently assigned.
Reporter | ||
Updated•6 months ago
|
Updated•6 months ago
|
Description
•