Firefox 63 Blocks Tracking Cookies
25.10.2018 securityweek Security
The new policy was added as part of the Enhanced Tracking Protection feature, which represents Mozilla’s new effort to protect users from being tracked across the websites they access.
“We aim to bring these protections to all users by default in Firefox 65,” Mozilla says.
The new policy effectively blocks domains classified as trackers from accessing the storage on the user’s device. Thus, such domains cannot access or set cookies or other site data when loaded in a third-party context.
Trackers are also blocked from accessing other APIs that could allow them to communicate cross-site, such as the Broadcast Channel API. Firefox uses the Tracking Protection list maintained by Disconnect to know which domains are classified as trackers.
Blocking third-party cookies may break websites, especially if the sites integrate third-party content. To prevent issues, Mozilla added heuristics to Firefox to automatically grant time-limited storage access under certain conditions. Such permissions are added on a site-by-site basis, and only for access to embedded content that receives user interaction.
More structured access will be available through a Storage Access API that is now implemented in Firefox Nightly for testing. Also implemented in Safari, the API is a proposed addition to the HTML specification. It allows trackers to explicitly request storage access when loaded in a third-party context.
To enable the new policy in Firefox, users should go to Options > Privacy & Security and select Third-Party Cookies in the Content Blocking section, then select Trackers (recommended). Users, however, can still take advantage of Tracking Protection to block all tracking loads. They simply need to set All Detected Trackers to Always.
Firefox 63 was also released with patches for 14 vulnerabilities, including two memory safety bugs rated “critical severity.” Additionally, it addressed three high risk bugs, four medium severity issues, and 5 low risk flaws.
The new browser release was also supposed to completely remove trust in Symantec certificates but, after learning that over 1% of the top 1,000,000 websites still use such certificates, Mozilla decided to delay the move.