Closed Bug 1570681 Opened 8 months ago Closed 7 months ago

Enforce AssertEvalNotUsingSystemPrincipal on non-Debug Builds


(Core :: DOM: Security, task, P2)




Tracking Status
firefox71 --- fixed


(Reporter: tjr, Assigned: tjr)


(Blocks 1 open bug)


(Whiteboard: [domsecurity-active])


(2 files)

In Bug 1567623 we're adding telemetry to look for in-the-wild uses of eval in the system principal context. That code will crash a debug build but will only log an error and allow execution in opt builds.

This bug tracks changing that code to (probably) abort execution of eval() without crashing the process. This might cause unknown errors so that's an argument for crashing instead... but since we believe we've figured out all the uses of eval() in our code this is probably caused by people doing weird things so maybe it'll be safer to give a less obvious (aborted execution) behavior rather than such a disruptive one (crashing)

Bugbug thinks this bug is a task, but please change it back in case of error.

Type: defect → task
Assignee: nobody → tom
Priority: -- → P2
Whiteboard: [domsecurity-active]

We'll log a console error plus abort execution. See example

I'm disabling eval() in Nightly builds now in bug 1572568. Please let us know when this bug goes ahead and we reverse the change.

Depends on: 1573622

We log to MOZ_LOG, report an error to the console, send telemetry, and in debug builds - crash

Pushed by
Move Eval testing logic from nsContentSecurityManager to nsContentSecurityUtils r=ckerschb
Enforce eval restrictions in system contexts and the parent process r=ckerschb
Closed: 7 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla71
You need to log in before you can comment on or make changes to this bug.