1381342 - Enable chromium ASLR features for Windows content

Status: NEW

(Core :: Security: Process Sandboxing, enhancement, P2)

Description

[Jim Mathies [:jimm]]

Mitigation flags:

MITIGATION_BOTTOM_UP_ASLR - random lower bound as the minimum user address
MITIGATION_RELOCATE_IMAGE - Forces ASLR on all images
MITIGATION_HIGH_ENTROPY_ASLR - increased randomness range for bottom-up ASLR
MITIGATION_RELOCATE_IMAGE_REQUIRED - refuse to load dlls that can't be relocated

I don't see issues with any of these for content.

Note, Tom filed this bug on MITIGATION_BOTTOM_UP_ASLR - 
https://bugs.chromium.org/p/chromium/issues/detail?id=727708

Comment 1

[Jim Mathies [:jimm]]

try run looks good - 
https://treeherder.mozilla.org/#/jobs?repo=try&revision=6e97346875067a87bdf619fe66aae5f3ac3b0360

Comment 2

[Jim Mathies [:jimm]]

Hey David, lets take a look at these and see if we can knock any of these out (or close this bug as invalid). Some of these ALSR settings kick in by default. The current sandbox feature comparison spreadsheet has notes about this on individual flags.