MSN Cookie Data Crosses Domains
tzanger writes "My brother pointed me to this article on pc-help.org. It explains a clever GUID tagging mechanism employed my MSN which allows cookies to be set and tracked over multiple domains. Of particular interest is that this mechanism works even if cookies are disabled. Finally, IE users may find that their Trusted Sites settings are useless if msn.com is on the list of sites that they do trust." Not a new issue, but a very clear and technical explanation of what is going on behind the scenes. Nice investigative work.
This article really needs to be on the front page....
Not a new issue, [snip]
This may be so but I haven't seen it covered here before and I do feel it's important to bring to light.
Where did you hear from it before? (not a flame-starter, an honest question)
... an aside. I clicked "no score +1 bonus, and then continued to type here. Every time I hit space, the checkmark toggles. I'm not sure How I managed to keep the checkbox highlighed and then resume typing. Neat bug at any rate. :-)
I wonder how much extra use the msid.msn.com server is getting tonight... it has certainly had a few hits from me that it wouldn't normally have.
Your browser will get caught in a loop, reloading blank pages until eternity.
Think that's bad? How 'bout msid.msn.com cookies set as part of your install, and re-created even after deletion?
Grab a hex editor or other file viewing tool (e.g. LIST.COM) and examine MSIE's cookie files, you'll see that msid.msn.com has a cookie set even if you don't use IE. (Reproduce: Delete - from within DOS, not Windoze, all MSIE cookie files. Reboot. Do not connect to the 'net. Observe that IE has re-created cookies pointing to msid.msn.com with your information in 'em, even though you never connected to the 'net. They're there on a clean install from CD-ROM, and they come back every time you delete 'em.
This is why I've had msid.msn.com firewalled for the past 2-3 years. Nothing comes in, nothing goes out. Ever.
I have no idea what Bill's doing with this data, but I sure as fuck don't like it.
(And I concur with the poster that said this should be on the /. front page. Whatever's going on at msid.msn.com has been going on since the release of Windows 98, and it needs to be investigated by those with more clue than I.)
The nastiest bit of the whole thing is saved for the very end of the article: the MS script is set up to do this cookie exchanging indiscriminately, not just for other MS sites. As the author put it:
That's a very, very serious security hole. I don't know how much data MS keeps, but I wouldn't be terribly surprised if it were possible to mine credit cards numbers this way. It's more proof of MS's lax attitude toward security.
There's no point in questioning authority if you aren't going to listen to the answers.
This is funny to watch.
---
Big Brother is Watching YOU. I Knew that they would figure out how to get around turning off cookies it was just a matter of time.My question is How do we Thwart them????????
PS no FUD or Hot Grits Please
Privacy. Who has the time to keep it? Oh Well. death and taxes
Getting around this problem is easy, I don't know how you missed it. Don't use Microsoft products. They can't keep doing this if they go out of business, now, can they?
Constitutionally Correct
I have my own browser which makes it very easy to debug things like this. Not only does it never follow redirects and naver take cookies, but it makes it easy to examine the raw data returned by every HTTP transaction. I also use Linux Netscape 4.72, and have cookies enabled there all the time.
I discovered that expedia and msnbc have common GUIDs in my Netscape cookies file, and furthermore the expedia site uses the same triple-redirection technique shown on the pc-help.org article. It routes through expedia.msnbc.com and then back to expedia.com after attaching the GUID to the URL.
- Robert Munafo
Lawyers: The Other White Trash.
Server Name Status
msn.com MC1 disabled
msnbc.com MC1 disabled
Yet when I chose to view the properties of the cookie files their status was listed as enabled! Yet another deceptive practice from Microsoft. Who would have thunk it!