canmove, Confirmed users
1,220
edits
Security/Sandbox/IPCguide: Difference between revisions
Jump to navigation
Jump to search
→Expose as few capabilities as possible to the child (e.g. content process)
Ptheriault (talk | contribs) |
Ptheriault (talk | contribs) |
||
| Line 139: | Line 139: | ||
'''BUT''', if you consider the case of the content process being compromised, this pretty much bypasses all the sandbox restrictions in place for protecting write access. Because an attacker can now just request access to any file and will get back a file descriptor from the chrome process. | '''BUT''', if you consider the case of the content process being compromised, this pretty much bypasses all the sandbox restrictions in place for protecting write access. Because an attacker can now just request access to any file and will get back a file descriptor from the chrome process. | ||
This issue also | This issue has also been seen in Message Manager based IPC, for example see bug [https://bugzilla.mozilla.org/show_bug.cgi?id=1341191 ''1341191'']. | ||
=== Whitelist over Blacklist === | === Whitelist over Blacklist === | ||