{"id":396028,"date":"2022-01-18T20:00:43","date_gmt":"2022-01-18T17:00:43","guid":{"rendered":"https:\/\/en.buradabiliyorum.com\/apples-safari-is-leaking-your-browsing-data\/"},"modified":"2022-01-18T20:00:43","modified_gmt":"2022-01-18T17:00:43","slug":"apples-safari-is-leaking-your-browsing-data","status":"publish","type":"post","link":"https:\/\/buradabiliyorum.com\/en\/apples-safari-is-leaking-your-browsing-data\/","title":{"rendered":"#Apple\u2019s Safari Is Leaking Your Browsing Data"},"content":{"rendered":"

“#App<\/a>le\u2019s Safari Is Leaking Your Browsing Data”<\/strong><\/p>\n

\n
\n
\"\"
FellowNeko\/Shutterstock.com<\/a><\/span><\/figcaption><\/figure>\n

A new Safari bug has been discovered in iOS, iPadOS, and Mac by\u00a0FingerprintJS<\/a>\u00a0(Via 9To5Mac<\/a>). The bug can reveal information about your recent browsing history in addition to\u00a0some info on the logged-in Google account.<\/p>\n

The bug is in Safari\u2019s IndexedDB implementation on all three of Apple\u2019s operating systems. Apparently,\u00a0a website can see the names of databases for any domain. Typically, a website should only see the names of databases of its own domain, so this is definitely a security issue. The names of the databases\u00a0can be used to extract information from a lookup table.<\/p>\n

With this information, your recent browsing history could surface. Additionally, because Google services store an IndexedDB instance for each of your logged-in accounts, your account name could also be revealed.<\/p>\n

As far as what someone could do with this information, they could scrape your Google ID and then use that to find out other personal information about you.<\/p>\n

If you want to see the bug in action, you can visit\u00a0safarileaks.com<\/a> in the Safari browser on Mac, iPad, or iPhone. If you try from a different browser on Mac, you\u2019ll see a message stating that \u201cYour browser is not affected. Please open this demo in Safari 15 on macOS or any browser on iOS and iPadOS 15.\u201d If you\u2019re on iPad or iPhone, it\u2019ll work either way.<\/p>\n

FingerprintJS first reported the bug to Apple on November 28, 2021, but the issue has yet to be resolved. Hopefully, the pressure of the problem being public will push Apple to get a fix out.<\/p>\n<\/div>\n


\n\n<\/div>\n