WebAPI/Security/PermissionsAPI: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== Permission API==
== Permission API==
Reference: https://bugzilla.mozilla.org/show_bug.cgi?id=707625
Brief purpose of API: Allow an app to manage app permissions in a centralized location
Brief purpose of API: Allow an app to manage app permissions in a centralized location


Line 11: Line 8:
Threat severity: Critical
Threat severity: Critical


=== Regular web content (unauthenticated) ===
References:  
Use cases for unauthenticated code:None
*https://bugzilla.mozilla.org/show_bug.cgi?id=707625
 
*https://groups.google.com/d/topic/mozilla.dev.webapps/sEN6K4y4Am8/discussion
Authorization model for normal content: None
 
Authorization model for installed content: None
 
Potential mitigations:
 
=== Trusted (authenticated by publisher) ===
 
Use cases for authenticated code: None
 
Use cases for trusted code: None
 
Potential mitigations:


=== Certified (vouched for by trusted 3rd party) ===
=== Permissions Table===
Use cases for certified code:  Centralized permissions management app; modify per-app settings


Authorization model: Implicit
{| border="1" class="wikitable"
! Type
! Use Cases
! Authorization Model
! Notes & Other Controls
|-
| Web Content || None || No access ||
|-
| Installed Web Apps || None || No access ||
|-
| Privileged Web Apps || None || No access ||
|-
| Certified Web Apps || Centralized permissions management app; modify per-app settings || Implicit ||
|}


Potential mitigations: None
==Notes==
We are not exposing permission settings to non-certified apps.  Apps cannot determine their current settings without actually requesting a permission.


Note: We are not exposing permission settings to non-certified apps.  Apps cannot determine their current settings without actually requesting a permission.
__NOTOC__


___NOTOC___
[[Category:Web APIs]]
[[Category:Security]]

Latest revision as of 23:41, 1 October 2014

Permission API

Brief purpose of API: Allow an app to manage app permissions in a centralized location

General Use Cases: None

Inherent threats: Change security and privacy permissions, potentially leading to device compromise

Threat severity: Critical

References:

Permissions Table

Type Use Cases Authorization Model Notes & Other Controls
Web Content None No access
Installed Web Apps None No access
Privileged Web Apps None No access
Certified Web Apps Centralized permissions management app; modify per-app settings Implicit

Notes

We are not exposing permission settings to non-certified apps. Apps cannot determine their current settings without actually requesting a permission.

Retrieved from "https://wiki.mozilla.org/index.php?title=WebAPI/Security/PermissionsAPI&oldid=1021343"