#57 The injection of Connected cameras and microphones wrappers in Recommended level generates Uncaught (in promise) Error: Permission denied to access object in Firefox on testing page
Opened 2 years ago by polcak. Modified 2 years ago

Summary

Something is broken during the script injection mechanism. When I visit https://polcak.github.io/jsrestrictor/test/test.html with JShelter 0.9 and Recommended level, I can see "Uncaught (in promise) Error: Permission denied to access object" in the console 4 times.

Setup

Pages affected: https://polcak.github.io/jsrestrictor/test/test.html
JShelter Version: 0.9

Popup information (open JShelter popup on affected pages:

JavaScript Shield active, Recommended level, no tweaks
Browser: Firefox
Other extensions that might affect JShelter behaviour: Appears without any other extension installed

How to reproduce

  1. Go to https://polcak.github.io/jsrestrictor/test/test.html
  2. Open the console of WebDev tools
  3. See the 4 errors

Expected result

No error reported

Actual result

Uncaught (in promise) Error: Permission denied to access object in Firefox (generated 4-times)

Reproducibility

Yes, I tried different profiles and machines. The same result. The error does not appear on Strict and "Turn fingerprinting protection off" levels.

Workarounds

The error does not appear on Strict and "Turn fingerprinting protection off" levels.

The error does not appear if I disable Connected cameras and microphones wrappers.


Additional information: it seems to me that the problem concerns the iframes. When I try to execute the following code in the console (taken from the test page):

appendLi = console.log;
ul = "None";
var p =     navigator.mediaDevices.enumerateDevices()
.then(function(devices) {
        appendLi(ul, devices.length.toString() + " cameras and microphones detected");
        devices.forEach(function(device) {
            appendLi(ul, device.kind + ": " + device.label + " id = " + device.deviceId);
        });
    })

I get the correct output. The page itself displays the correct output.

Possible duplicate of #55.

Metadata Update from @polcak:
- Issue priority set to: High (was: Normal)

2 years ago

Log in to comment on this ticket.

Metadata