WebAPI/Security/BrowserAPI: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Created page with "Name of API: Browser API References: https://wiki.mozilla.org/WebAPI/EmbeddedBrowserAPI popup windows in b2g: https://bugzilla.mozilla.org/show_bug.cgi?id=716664 window.open in i...")
 
No edit summary
Line 1: Line 1:
Name of API: Browser API
Name of API: Browser API
References:
References:
https://wiki.mozilla.org/WebAPI/EmbeddedBrowserAPI
*https://wiki.mozilla.org/WebAPI/EmbeddedBrowserAPI
popup windows in b2g: https://bugzilla.mozilla.org/show_bug.cgi?id=716664
*popup windows in b2g: https://bugzilla.mozilla.org/show_bug.cgi?id=716664
window.open in iframe mozbrowser:
*window.open in iframe mozbrowser: https://bugzilla.mozilla.org/show_bug.cgi?id=742944
https://bugzilla.mozilla.org/show_bug.cgi?id=742944
*window.open in iframe mozapp: https://bugzilla.mozilla.org/show_bug.cgi?id=744451
window.open in iframe mozapp:
https://bugzilla.mozilla.org/show_bug.cgi?id=744451


Brief purpose of API: Provide an iframe that acts as a web browser
Brief purpose of API: Provide an iframe that acts as a web browser
General Use Cases: A browser app.
General Use Cases: A browser app.


Line 21: Line 21:
== Regular web content (unauthenticated) ==
== Regular web content (unauthenticated) ==
Use cases for unauthenticated code: None
Use cases for unauthenticated code: None
Authorization model for normal content: None
Authorization model for normal content: None
Authorization model for installed content:None
Authorization model for installed content:None
Potential mitigations:
Potential mitigations:


== Trusted (authenticated by publisher) ==
== Trusted (authenticated by publisher) ==
Use cases for authenticated code: Implement a 3rd party browser application
Use cases for authenticated code: Implement a 3rd party browser application
Authorization model: Implicit
Authorization model: Implicit
Potential mitigations: Each app has separate cookie and password stores
 
from other apps (including system browser app)
Potential mitigations: Each app has separate cookie and password stores from other apps (including system browser app)


== Certified (vouched for by trusted 3rd party) ==
== Certified (vouched for by trusted 3rd party) ==
Use cases for certified code: Replacement Browser
Use cases for certified code: Replacement Browser
Authorization model: Implicit
Authorization model: Implicit
Potential mitigations: N/A

Revision as of 06:19, 31 July 2012

Name of API: Browser API

References:

Brief purpose of API: Provide an iframe that acts as a web browser

General Use Cases: A browser app.

Inherent threats:

  • browser can see all data from all websites, and perform all actions
  • can steal passwords (user-entered; enumerate all saved passwords)
  • can steal cookies (by enumerating websites)
  • NOT a use case: OAuth or other app-content or content-content interactions

Threat severity: high per https://wiki.mozilla.org/Security_Severity_Ratings

Regular web content (unauthenticated)

Use cases for unauthenticated code: None

Authorization model for normal content: None

Authorization model for installed content:None

Potential mitigations:

Trusted (authenticated by publisher)

Use cases for authenticated code: Implement a 3rd party browser application

Authorization model: Implicit

Potential mitigations: Each app has separate cookie and password stores from other apps (including system browser app)

Certified (vouched for by trusted 3rd party)

Use cases for certified code: Replacement Browser

Authorization model: Implicit

Potential mitigations: N/A