Skip to content
This repository has been archived by the owner on Sep 4, 2019. It is now read-only.

Enable whitelisting support for embedded content #118

Open
nukulb opened this issue Jun 20, 2012 · 4 comments
Open

Enable whitelisting support for embedded content #118

nukulb opened this issue Jun 20, 2012 · 4 comments

Comments

@nukulb
Copy link
Contributor

nukulb commented Jun 20, 2012

All api's are available to embedded content, regardless of config.xml

App is a local index.html with app api's whitelisted, embedded iframe
with no api's allowed (think of an rss reader app)

The embedded content has access to any api the app has.

Expected:
@kwallis - fill in the details on what you want the behavior to be for remote url vs. local url

@kwallis
Copy link
Member

kwallis commented Jun 20, 2012

Is local vs. Remote the right question? Or is it more about differing domains of content?

----- Original Message -----
From: Nukul Bhasin [mailto:[email protected]]
Sent: Tuesday, June 19, 2012 11:17 PM
To: Ken Wallis
Subject: [BB10-WebWorks-Framework] Security hole with api whitelisting and embedded content (#118)

All api's are available to embedded content, regardless of config.xml

App is a local index.html with app api's whitelisted, embedded iframe
with no api's allowed (think of an rss reader app)

The embedded content has access to any api the app has.

Expected:
@kwallis - fill in the details on what you want the behavior to be for remote url vs. local url


Reply to this email directly or view it on GitHub:
#118


This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.

@nukulb
Copy link
Contributor Author

nukulb commented Jun 20, 2012

different domains is a better question.

Here is the problem, there is no way to find out from that if a NetworkResourceRequest came from an iFrame or original page. So I will be opening a PR.

@kwallis
Copy link
Member

kwallis commented Sep 18, 2012

Fixed?

cc @jeffheifetz

@jeffheifetz
Copy link
Contributor

Not yet

sleroux added a commit to blackberry-webworks/BB10-WebWorks-Framework that referenced this issue Oct 31, 2012
Changes a webview's requests to use the referrer from the
NetworkResourceRequestedEvent instead of originalLocation.

Reviewed By: Jeffrey Heifetz <[email protected]>
Tested By: Igor Shneur <[email protected]>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants