New issue
Advanced search Search tips

Issue 818613 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Mar 2018
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: ----
Type: Bug-Security



Sign in to add a comment

Security: getUserMedia SSL bypassing (Invalid certificates permitted to create a Secure Context)

Reported by mentosme...@gmail.com, Mar 5 2018

Issue description

VULNERABILITY DETAILS
To use the navigator.mediaDevices.getUserMedia on a website, that website requires SSL to be enabled. However, a website can also access the getUserMedia while it has no ssl installed. The only thing required to do so is replacing http:// with https:// in the url. You will still get the chrome warning the website is insecure. When you ignore that error and still proceed to the webpage, that website is able to see your webcam.

VERSION
Chrome Version: 64.0.3282.137 stable, 64.0.3282.186 stable
Operating System: Android 7.0.0 Motorola Moto G4 Plus, Windows 10

REPRODUCTION CASE
Extract the attached zip file inside your localhost / server location (like XAMPP htdocs folder). Make sure that that location has no SSL enabled. Then, on another device, visit the ip address or url where you put the index.html. You will see an alert that getUsermedia is not supported (like it should). Now, replace the leading http:// in the url with https:// . Ignore the Google Chrome SSL warning and proceed to the website. It will ask to use your camera, and when granted will also display it.

In my specific test, i did the following:
Extract this zip in my XAMPP htdocs folder. Then find my computer's IP address. Enter that IP address on any other device (tested with Windows 10 and Android). Replace the http:// of the url with https://. Ignore the SSL warning. Accept the use of the camera. Camera is now visible.
 
https-getusermedia.zip
34.7 KB Download
Status: WontFix (was: Unconfirmed)
Summary: Security: getUserMedia SSL bypassing (Invalid certificates permitted to create a Secure Context) (was: Security: getUserMedia SSL bypassing)
To reproduce this, the server in question must have HTTPS enabled. The report complains that, after clicking through a Certificate Error interstitial, window.isSecureContext returns true and APIs that require secure contexts (geolocation, getUserMedia, etc[1]) are permitted. This is working as designed. In this scenario, the user (rather than the browser's own certificate validation) has vouched for the validity of the certificate.

[1] https://www.chromium.org/Home/chromium-security/deprecating-powerful-features-on-insecure-origins
Project Member

Comment 2 by sheriffbot@chromium.org, Jun 11 2018

Labels: -Restrict-View-SecurityTeam allpublic
This bug has been closed for more than 14 weeks. Removing security view restrictions.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment