-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[hackerone] Extend font randomization fingerprinting protections to also cover src:local #23432
Comments
@pilgrim-brave @pes10k mind providing a testcase for this, please? 🙏 |
Verified
|
Brave | 1.44.85 Chromium: 105.0.5195.127 (Official Build) beta (x86_64) |
---|---|
Revision | 912488396852bf658ab32465980c0b93a3c27a83-refs/branch-heads/5195@{#1109} |
OS | macOS Version 11.7 (Build 20G817) |
Steps:
Followed the steps to reproduce from https://dev-pages.brave.software/fingerprinting/fonts.html
and https://dev-pages.bravesoftware.com/fingerprinting/fonts.html
Font setup |
more |
---|---|
Confirmed the rendered texts were the same, as well as their width
dimensions.
https://dev-pages.brave.software/fingerprinting/fonts.html
src:local |
Pseudo Fonts |
---|---|
https://dev-pages.bravesoftware.com/fingerprinting/fonts.html
src:local |
Pseudo Fonts |
---|---|
Verification
Confirmed the rendered texts were the same, as well as their width dimensions.
|
Removed |
Currently Brave allows sites to access a random subset of user fonts, to cause fingerprinters get a different fingerprint for each site, for each browser session.
However, recently researchers notified use
src:local
to have Chrome bypass these protections and query all installed fonts again. We should also apply our randomize font fingerprinting protections against alternative ways of accessing user fonts, likesrc:local
These researchers will be credited on HackerOne.
https://hackerone.com/reports/1598008
credit: xlin
The text was updated successfully, but these errors were encountered: