New issue
Advanced search Search tips
Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Apr 2012
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug-Security

Restricted
  • Only users with EditIssue permission may comment.



Sign in to add a comment
link

Issue 119150: Sandboxed processes should not be able to open other sandboxed processes

Reported by jsc...@chromium.org, Mar 20 2012 Project Member

Issue description

By default, sandboxed processes can open other sandboxed processes and manipulate them. Integrity levels and the restricted group prevent reaching into unsandboxed processes. However, it's possible to start a renderer with privileged IPCs, open the process, and manipulate it directly.
 

Comment 1 Deleted

Comment 2 Deleted

Comment 3 Deleted

Comment 4 Deleted

Comment 5 Deleted

Comment 6 Deleted

Comment 7 Deleted

Comment 9 by scarybea...@gmail.com, Apr 19 2012

Labels: -Restrict-View-SecurityTeam Restrict-View-SecurityNotify Mstone-19 Merge-Approved
Status: FixUnreleased
Good to merge to M19 Beta once it's survived a few more days on dev?

Comment 10 by jsc...@chromium.org, Apr 19 2012

Yeah, I'll do the merge since it might get hairy.

Comment 11 by scarybea...@gmail.com, Apr 30 2012

Labels: -Mstone-19 -Merge-Approved Mstone-20
Justin says M20. Seems reasonable!

Comment 12 by scarybea...@gmail.com, Jun 25 2012

Labels: CVE-2012-2816

Comment 13 by jsc...@chromium.org, Jul 6 2012

Labels: -Restrict-View-SecurityNotify
Status: Fixed

Comment 14 by bugdroid1@chromium.org, Oct 13 2012

Project Member
Labels: Restrict-AddIssueComment-Commit
This issue has been closed for some time. No one will pay attention to new comments.
If you are seeing this bug or have new data, please click New Issue to start a new bug.

Comment 15 by bugdroid1@chromium.org, Mar 10 2013

Project Member
Labels: -Type-Security -Area-Internals -Feature-Security -SecImpacts-Stable -SecImpacts-Beta -SecSeverity-Medium -Mstone-20 M-20 Security-Impact-Stable Security-Impact-Beta Cr-Security Security-Severity-Medium Cr-Internals Type-Bug-Security

Comment 16 by bugdroid1@chromium.org, Mar 14 2013

Project Member
Labels: -Restrict-AddIssueComment-Commit Restrict-AddIssueComment-EditIssue

Comment 17 by bugdroid1@chromium.org, Mar 21 2013

Project Member
Labels: -Security-Impact-Stable Security_Impact-Stable

Comment 18 by bugdroid1@chromium.org, Mar 21 2013

Project Member
Labels: -Security-Severity-Medium Security_Severity-Medium

Comment 19 by bugdroid1@chromium.org, Mar 21 2013

Project Member
Labels: -Security-Impact-Beta Security_Impact-Beta

Comment 20 by sheriffbot@chromium.org, Jun 14 2016

Project Member
Labels: -security_impact-beta

Comment 21 by sheriffbot@chromium.org, Oct 1 2016

Project Member
This bug has been closed for more than 14 weeks. Removing security view restrictions.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 22 by sheriffbot@chromium.org, Oct 2 2016

Project Member
This bug has been closed for more than 14 weeks. Removing security view restrictions.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 23 by mbarbe...@chromium.org, Oct 2 2016

Labels: allpublic

Comment 24 by awhalley@chromium.org, Apr 25 2018

Labels: CVE_description-submitted

Sign in to add a comment