Open Bug 1484019 (fission-ipc) Opened 6 years ago Updated 1 month ago

[meta] Enforce Content Process Restrictions in IPC

Categories

(Core :: IPC, enhancement)

Product:
Core
Component:
IPC
Type:
enhancement

Tracking

()

Project Flags:
Fission Milestone Future

People

(Reporter: tjr, Unassigned)

References

(Depends on 36 open bugs, Blocks 1 open bug)

Details

(Keywords: meta)

In addition to ensuring the Parent (+ Compositor/RDD) processes never _send_ data belonging to origin B to origin A, we should ensure that the content process of Origin B cannot _receive_ data even if it explicitly requests data for origin A. Such a request would be the result of either a bug or a compromised child process. The Parent/Compositor/RDD process needs a trusted mapping of Content Processes -> Origins, and then needs to add checks into all relevant IPC/MM methods to confirm that requested data is for an origin the process is authorized for. Surely there will be a lot of shared code in these checks, so creating a framework for that would be a task for the first of these checks added.
Depends on: 1484026
Depends on: 1486598
Depends on: 1487520
Depends on: 1487526
Depends on: 1487533
Depends on: 1490049
Depends on: 1490093
Depends on: 1490124
Depends on: 1490129
Depends on: 1490131
Depends on: 1490450
Depends on: 1490461
Depends on: 1490475
Depends on: 1490479
Depends on: 1490784
Depends on: fission-ipc-map
Depends on: 1491113
Depends on: 1491119
Depends on: 1492223
Depends on: 1492569
Depends on: 1492596
Depends on: 1494447
Depends on: 1494457
Depends on: 1494458
Depends on: 1494459
Depends on: 1495835
Depends on: 1495887
Depends on: 1500513
Keywords: meta
Depends on: 1500558
Depends on: 1500586
Depends on: 1500953
Depends on: 1501010
Depends on: 1501072
Depends on: 1501082
Depends on: 1375122
Summary: Enforce Content Process Restrictions in IPC → [meta] Enforce Content Process Restrictions in IPC
Blocks: fission-site-sandbox
No longer blocks: fission
Bug 1513003 is a particurally important one given its high value (Saved Logins) and how easy it would be to abuse given a UXSS vulnerability.
Depends on: 1513003
Depends on: 1513680
No longer depends on: 1472158
Depends on: 1432831
Depends on: 1520280
Depends on: 1527710
Depends on: CVE-2020-12424
Depends on: CVE-2019-11765
Fission Milestone: --- → Future
Depends on: 1602318
Depends on: 1604058
Depends on: 1696159
Depends on: 1499868
Depends on: 1770227
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.