Open Bug 1400864 Opened 7 years ago Updated 2 years ago

Window sandboxed child process launch fails with error codes 40 and 0x000000b7

Categories

(Core :: Security: Process Sandboxing, defect, P3)

Product:
Core
Component:
Security: Process Sandboxing
Type:
defect

Tracking

()

People

(Reporter: bobowen, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: sb+) 

Found from SANDBOX_FAILED_LAUNCH_KEYED telemetry.

Chromium sandbox error code is 40 SBOX_ERROR_CANNOT_SETUP_INTERCEPTION_THUNK, which can only come from [1].
Although there are several potential failures that lead up to that.

Windows error is 0x000000b7 ERROR_ALREADY_EXISTS.

[1] https://hg.mozilla.org/mozilla-central/file/tip/security/sandbox/chromium/sandbox/win/src/interception.cc#l535
The 0x000000b7 looks like it comes from these (from the Setup, CopyThunk isn't used), when IsFunctionAService returns false:
http://searchfox.org/mozilla-central/search?q=return+STATUS_OBJECT_NAME_COLLISION

These are nearly all 64-bit.
Priority: P2 → P3
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.