Closed Bug 820635 Opened 12 years ago Closed 12 years ago

Investigate if different app processes that share uid can compromise each other

Categories

(Firefox OS Graveyard :: General, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 820560

People

(Reporter: sicking, Unassigned)

Details

Bug 812289 comment 50 expresses the concern that app processes that share UIDs might be able to read and write each other's memory and thus compromise each other.

Since we currently share UID for all app processes, that would mean that a hacked 3rd party app could compromise the settings or telephony apps. In fact, it would allow any app to get almost any permission by simply asking the user to launch the app which has that permission (or launching it itself using webactivities).

So for example, any app could place a phone call by simply launching the telephony app using webactivities and then hacking into the telephony app's process space.

My understanding is that the current B2G sandbox should protect against this, despite the processes sharing UIDs. If that's not the case then we have a problem.
Flags: needinfo?(jones.chris.g)
Check your email, way ahead of you.
Group: core-security
Status: NEW → RESOLVED
Closed: 12 years ago
Flags: needinfo?(jones.chris.g)
Resolution: --- → DUPLICATE
blocking-basecamp: ? → ---
Group: core-security
You need to log in before you can comment on or make changes to this bug.