New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 706803 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner: ----
Closed: May 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug
Team-Security-UX



Sign in to add a comment

Push API - Notification permissions are allowed from an HTTPS iframe embedded within a HTTP page

Reported by maddyro...@gmail.com, Mar 30 2017

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36

Steps to reproduce the problem:
1. Place a hidden, secure iframe (src="https://b.com") within an insecure page (http://a.com)
2. Let the java script loaded on b.com request for a Notification permission using Notification.requestPermission()
3. This request will be honoured, and the browser will display the native opt-in pop-up with the message "b.com wants to: Show Notifications"

What is the expected behavior?
The Notification.permission() request should be declined by the browser since the original, top level page (a.com) is still on HTTP.

What went wrong?
As per the below mentioned chromium bugs, which were already closed, this behaviour should not be allowed at all.

https://bugs.chromium.org/p/chromium/issues/detail?id=430496
https://bugs.chromium.org/p/chromium/issues/detail?id=559480

However, the design appears to be broken.

Did this work before? N/A 

Does this work in other browsers? No
 Browser: Chrome -55	Chrome-56	Firefox-49	Firefox-50	Firefox-51
OS: Windows 7 Windows 10
    Mac os Sierra Mac os El Capitan

Chrome version: 55.0.2883.87  Channel: n/a
OS Version: 
Flash Version: Shockwave Flash 25.0 r0

I was exploring a solution around this, and later realized that it is actually a security loophole! And, the overall theme discussed, and the conclusion reached in the above mentioned tickets appears to be violated.
 

Comment 1 by peter@chromium.org, Apr 3 2017

Cc: dominickn@chromium.org raymes@chromium.org
Components: -Blink>PushAPI UI>Notifications Internals>Permissions
Status: Assigned (was: Unconfirmed)
We're actually going to deprecate this behaviour in Chrome 59, and are planning to remove it in Chrome 61. See Issue 695693 and  Issue 563297 . I think that addresses your concerns?
Components: -Internals>Permissions Internals>Permissions>Model
Status: WontFix (was: Assigned)

Sign in to add a comment