Redirect Chain leaks to Content Process
Categories
(Core :: Networking, defect, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox101 | --- | fixed |
People
(Reporter: tjr, Assigned: jewilde)
References
(Blocks 1 open bug)
Details
(Whiteboard: [necko-triaged][spectre-blocker][sp3])
Attachments
(1 file)
Presently when following a redirect chain we include the redirect chain in the LoadInfo which we send to the final Content Process. This type of behavior can leak to user credential theft via leaked OAuth tokens.
This bug report is a sample of one such vulnerability - this bug report didn't involve Spectre, the tokens were leaked to the attacker site in the Referer header. But considering a Spectre attacker, we could expose the tokens in an otherwise-secure flow because the redirect chain is in memory.
Is the redirect chain needed in the Content Process? Can we merely omit it there?
Comment 1•4 years ago
|
||
Thanks Tom - it seems like consumers of RedirectChain would need to modify their code to support this, but it does look generally possible.
Marking P3 since most consumers are outside of netwerk/
Do you mind setting a Severity here based on your assessment of the likelihood of exposure and the impact should an exposure arise?
Reporter | ||
Comment 2•3 years ago
|
||
We discussed this and consider it a blocker for disabling Spectre mitigations.
At a minimum we think the redirect chain should be redirect chain should be trimmed to just principals or something to that effect; but ideally we could exclude it from the content process?
Comment 3•3 years ago
|
||
Christoph, can someone on your team take a look at this. Do you know if you need this information on the content process.
Note: Necko only provides this to the content process but does not consume the information. We can easily remove this from the content process if it is not needed. I also see this we can easily transform that into a flag and calculate it on the parent process.
Comment 4•3 years ago
|
||
June, can you please take a look? I can provide some guidance on fixing this.
Assignee | ||
Comment 5•3 years ago
|
||
I'm on it!
I'm planning on picking this up when we return from the holidays in January.
Assignee | ||
Comment 6•3 years ago
|
||
Updated•3 years ago
|
Comment 8•3 years ago
|
||
bugherder |
Updated•3 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Description
•