Closed
Bug 2014254
Opened 9 months ago
Closed 5 months ago
WindowGlobalParent: don't get securityInfo from content process
Categories
(Core :: DOM: Content Processes, enhancement)
Core
DOM: Content Processes
Tracking
()
RESOLVED
DUPLICATE
of bug 2022249
People
(Reporter: keeler, Assigned: keeler)
References
(Blocks 1 open bug)
Details
(Keywords: sec-want)
Attachments
(1 obsolete file)
WindowGlobalParent currently gets its securityInfo from the content process via RecvUpdateDocumentSecurityInfo. This is not great from a security perspective, because if the content process gets compromised, the parent process is trusting potentially malicious information.
| Assignee | ||
Comment 1•9 months ago
|
||
This avoids trusting the content process for this information. It also removes
an IPC call.
Comment 3•8 months ago
|
||
bug 1670242 might not be quite the right fission meta bug to block, but it's in the ballpark of known and ongoing efforts.
Blocks: site-isolation-principal-vetting
Keywords: sec-want
| Assignee | ||
Updated•5 months ago
|
Blocks: CVE-2026-16372
| Assignee | ||
Updated•5 months ago
|
Updated•5 months ago
|
Attachment #9542208 -
Attachment is obsolete: true
You need to log in
before you can comment on or make changes to this bug.
Description
•