GTP
Well-Known Member
- Reaction score
- 9,834
- Location
- Adelaide, Australia
"Any site you visit can probe you to see whether you're logged into other specific sites.
Same Origin Policy strongly restricts which web content JavaScript can access to coming from
the same hosting site. But IMAGES, being benign and useful, are excluded from the Same Origin
Policy.
The login mechanisms of most major sites will check every incoming request for the presence of
a logged-in session cookie and, if not present, will redirect the user to their logon page.
In order to present the site's logo in the URL, browser tabs, etc., site place an image called
"favicon.ico" in the root (/) page of the server where all visiting web browsers know to fetch it.
These facts enable JavaScript from an snooping site to probe any user's browser for their current
logged-in status on another other compliant site. (And most sites are compliant.)
The snooping script simply requests the target site's /favicon.ico file, which the same origin
policy allows. If the image request succeeds -- as it would if the user is logged in and the site
returns the image -- the snooping JavaScript is able to detect the successful image load. But if
the user is NOT currently logged on to the target site, the target site will return a
redirect-to-login URL instead of an image, and the snooping JavaScript will see that as an image
load failure.
Thus, while this is not a security violation per se, it's a privacy violation. The snoopy site likely
DOES know who YOU are... and it can determine whether YOU are likely using any other service
that you are currently logged into.
And... since ADVERTISEMENTS are also allowed to run their own JavaScript for ad rotation, etc.,
that also means that the third part hosts of any ads can similarly perform a rather sophisticated
profiling of the person who is visiting the site hosting the advertisement."
You can check here. https://robinlinus.github.io/socialmedia-leak/
Source: GRC.com Security Now! #636
Same Origin Policy strongly restricts which web content JavaScript can access to coming from
the same hosting site. But IMAGES, being benign and useful, are excluded from the Same Origin
Policy.
The login mechanisms of most major sites will check every incoming request for the presence of
a logged-in session cookie and, if not present, will redirect the user to their logon page.
In order to present the site's logo in the URL, browser tabs, etc., site place an image called
"favicon.ico" in the root (/) page of the server where all visiting web browsers know to fetch it.
These facts enable JavaScript from an snooping site to probe any user's browser for their current
logged-in status on another other compliant site. (And most sites are compliant.)
The snooping script simply requests the target site's /favicon.ico file, which the same origin
policy allows. If the image request succeeds -- as it would if the user is logged in and the site
returns the image -- the snooping JavaScript is able to detect the successful image load. But if
the user is NOT currently logged on to the target site, the target site will return a
redirect-to-login URL instead of an image, and the snooping JavaScript will see that as an image
load failure.
Thus, while this is not a security violation per se, it's a privacy violation. The snoopy site likely
DOES know who YOU are... and it can determine whether YOU are likely using any other service
that you are currently logged into.
And... since ADVERTISEMENTS are also allowed to run their own JavaScript for ad rotation, etc.,
that also means that the third part hosts of any ads can similarly perform a rather sophisticated
profiling of the person who is visiting the site hosting the advertisement."
You can check here. https://robinlinus.github.io/socialmedia-leak/
Source: GRC.com Security Now! #636