Bug 1518566 (CVE-2017-7843) - CVE-2017-7843 Mozilla: Web worker in Private Browsing mode can write IndexedDB data
Summary: CVE-2017-7843 Mozilla: Web worker in Private Browsing mode can write IndexedD...
Alias: CVE-2017-7843
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 1518567 1518568 1518569 1518570
Blocks: 1518574
TreeView+ depends on / blocked
Reported: 2017-11-29 08:32 UTC by Huzaifa S. Sidhpurwala
Modified: 2021-02-26 01:40 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
A privacy flaw was discovered in Firefox. In Private Browsing mode, a web worker could write persistent data to IndexedDB, which was not cleared when exiting and would persist across multiple sessions. A malicious website could exploit the flaw to bypass private-browsing protections and uniquely fingerprint visitors.
Clone Of:
Last Closed: 2017-12-05 06:08:55 UTC

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:3382 0 normal SHIPPED_LIVE Important: firefox security update 2017-12-05 10:45:18 UTC

Description Huzaifa S. Sidhpurwala 2017-11-29 08:32:30 UTC
When Private Browsing mode is used, it is possible for a web worker to write persistent data to IndexedDB and fingerprint a user uniquely. IndexedDB should not be available in Private Browsing mode and this stored data will persist across multiple private browsing mode sessions because it is not cleared when exiting.

Comment 2 Huzaifa S. Sidhpurwala 2017-11-29 08:32:41 UTC
External References:


Comment 4 Doran Moppert 2017-11-30 03:08:57 UTC

Name: the Mozilla project
Upstream: Konark

Comment 5 errata-xmlrpc 2017-12-05 05:45:46 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 6
  Red Hat Enterprise Linux 7

Via RHSA-2017:3382 https://access.redhat.com/errata/RHSA-2017:3382

Note You need to log in before you can comment on or make changes to this bug.