Open Bug 1277381 Opened 8 years ago Updated 2 years ago

Prevent OS.File usage in the content process

Categories

(Toolkit :: Async Tooling, defect)

defect

Tracking

()

People

(Reporter: mccr8, Unassigned)

Details

(Whiteboard: sb+)

Attachments

(1 file)

toolkit/components/osfile/modules/osfile_async_front.jsm implements various low-level file system related things. Right now, this can be loaded in the child process, though I don't know if it can actually be used. It would be good to raise an error or at least make osfile.jsm not load anything when run in a content process, to avoid future sandboxing issues.

I found one place that imports osfile.jsm in the content process, TelemetryController.jsm, but it doesn't actually seem to use it any more.

Haik, somebody from the sandboxing team might be interested in working on this.
This is just the simple bit of code I wrote to detect where it is being used.
Whiteboard: [sb?]
Whiteboard: [sb?] → sbwc2, sblc2, sbmc2
Moving to sblc3 which concludes removing/restricting file system access.
Whiteboard: sbwc2, sblc2, sbmc2 → sbwc2, sblc3, sbmc2
Whiteboard: sbwc2, sblc3, sbmc2 → sb+
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: