Open Bug 1888894 Opened 2 years ago Updated 9 days ago

Remove DOMHighResTimeStamp privacy.reduceTimerPrecision value for localhost / 127.0.0.1 hosts

Categories

(Core :: Privacy: Anti-Tracking, enhancement)

Firefox 124
enhancement

Tracking

()

UNCONFIRMED

People

(Reporter: mowod66703, Unassigned)

References

(Depends on 1 open bug)

Details

Steps to reproduce:

Remove rounding policy for DOMHighResTimeStamp for privacy.reduceTimerPrecision value for localhost / 127.0.0.1 hosts, so every call to performance.now / Date.now will get real values

The Bugbug bot thinks this bug should belong to the 'Core::Privacy: Anti-Tracking' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Privacy: Anti-Tracking
Product: Firefox → Core

Thoughts?

Flags: needinfo?(tihuang)

I think exempting the protection from the localhost page can cause a potential loophole. If a user loads a page that contains fingerprinting scripts on localhost, the fingerprint can be sent to attackers via fetch.

I suggest adding a separate pref to control the behavior on the localhost page instead of disabling it from localhost pages.

Flags: needinfo?(tihuang)

If a user loads a page that contains fingerprinting scripts on localhost, the fingerprint can be sent to attackers via fetch.

Not for file:// protocols, for that still be restrictions. Only for localhost domain names, as it is for devs only, so they will know what they do, casual users will not be able to run anything locally, downloaded pages will be opened via file:// schema

As here pointed localhost is trusted and secure
https://developer.mozilla.org/en-US/docs/Web/Security/Secure_Contexts

Any ideas?

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