Browsers and javascript has been security disasters for decades and yet the web crowd perpetuates this model and even plans for webassembly. Large webassembly applications will make it extremely difficult to inspect suspicious code for this kind of attacks. Dodgy ad providers will exploit similar vulnerabilities to better track user behavior or worse. Yet, there isn't an ongoing discussion on limiting the resources a…
This isn't a language problem, it's a computers and networking problem.
This JavaScript can snoop on other browser tabs to work out what you're visiting
61–68 of 68 posts
Re: This JavaScript can snoop on other browser tabs to work out what you're visiting
#62From the paper [1]: Each round of attack consists of three steps. In the first step, the cache is primed, i.e., the attacker completely fills some of the cache sets with its own data. The attacker then waits some time to allow the victim to execute. Finally, the attacker probes the cache by measuring the time it takes to access the previously-cached data ... From a brief glance, it looks like they then use the timing…
We're talking here about an attacker finding out what website domain names are open in other tabs on a target's browser? Is that a big deal?
Re: This JavaScript can snoop on other browser tabs to work out what you're visiting
#63From the paper [1]: Each round of attack consists of three steps. In the first step, the cache is primed, i.e., the attacker completely fills some of the cache sets with its own data. The attacker then waits some time to allow the victim to execute. Finally, the attacker probes the cache by measuring the time it takes to access the previously-cached data ... From a brief glance, it looks like they then use the timing…
It seems like a very difficult and iffy technique to get NOT a lot of information. We're talking here about an attacker finding out what website domain names are open in other tabs on a target's browser? Is that a big deal?
It is probably difficult to say which sites one is using, but an easier task would be to profile by time and IP address that it seems that this group of people visits site A a lot around X time.
Re: This JavaScript can snoop on other browser tabs to work out what you're visiting
#64What is the most intuitive Chrome extension that you've used to block JavaScript on every site and to create a whitelist as you went?
I recommend uMatrix. At first it will take a few minutes to understand how it works, though. You can turn on and off images, css, scripts, XHR, etc, for individual sites or globally. I use it in that manner, with scripting off by default. If I am visiting a new site that needs javascript, I gradually whitelist specific bits until it works and then "save" those settings for that domain.
Re: This JavaScript can snoop on other browser tabs to work out what you're visiting
#65From the paper [1]: Each round of attack consists of three steps. In the first step, the cache is primed, i.e., the attacker completely fills some of the cache sets with its own data. The attacker then waits some time to allow the victim to execute. Finally, the attacker probes the cache by measuring the time it takes to access the previously-cached data ... From a brief glance, it looks like they then use the timing…
It seems like a very difficult and iffy technique to get NOT a lot of information. We're talking here about an attacker finding out what website domain names are open in other tabs on a target's browser? Is that a big deal?
Re: This JavaScript can snoop on other browser tabs to work out what you're visiting
#66Not sure if I understand this correctly, but the attacker's JS must load the pages in question to see if they are in cache, right? Wouldn't that put also them in cache, which means that next time this technique is used it will not work? Even more, there is now plausible deniability: "I never saw these pages, I guess some JS must have been snooping around and put them to my cache..." And the logical workaround is disa…
> And the logical workaround is disabling cache,... The attack uses the CPU cache, not the browser cache.
Re: This JavaScript can snoop on other browser tabs to work out what you're visiting
#67Re: This JavaScript can snoop on other browser tabs to work out what you're visiting
#68> The takeaway, they contend, is that anything short of running a single browser tab at any one point in time poses a privacy risk: if you open a second tab, JavaScript in it can snoop on the other tab. Disabling JavaScript completely will kill off the attack, but also kill off a lot of websites, which rely on JS functionality to work. Firefox Focus [1], my most used browser (single tab only), seems to be safe from t…
Firefox Focus does have multiple tabs - long press on a link, then select "Open link in new tab".