Re:CSRF protection bypass due to Google analytics and weird ...
by brlewis on Monday May 04, 2015 @04:22PM
(#9488903)
They should both pay a bounty. But if you had to assign blame only one place it would be ECMAscript. Setting the value of an unintended cookie should not be so easy to do by accident.
Re:CSRF protection bypass due to Google analytics and weird ...
by ycitm on Monday May 04, 2015 @06:41PM
(#9489729)
Nitpick: strictly speaking setting cookies is not part of ECMAScript, it's part of the DOM api.
Re:CSRF protection bypass due to Google analytics and weird ...
by billyhoffman on Monday May 04, 2015 @11:37PM
(#9490733)
Cookies are, without a doubt, the worst "API" in the DOM.
Here's the entire API: document.cookie
That's it. That one property.To add cookies, modified cookies, delete cookies, whatever, you do an assignment. To read all the cookies, you do a read.
That's it. That's the API.
Re:CSRF protection bypass due to Google analytics and weird ...
by sarciszewski on Tuesday May 05, 2015 @01:36AM
(#9491028)
This is correct, and it's a source of madness.
One more thing: Cookies are limited to 4KB total due to the HTTP/1.1 specification.
Re:CSRF protection bypass due to Google analytics and weird ...
by BlackFan on Tuesday May 05, 2015 @05:47AM
(#9491658)
Hi, i am the author of this report.
I sent information about this vulnerability to: 1) Google (2 fix in Google Analytics) 2) Django / Python (https://hg.python.org/cpython/rev/270f61ec1157) 3) Twitter (changed CSRF protection) 4) Instagram [Facebook] (sent me to Django)
Seeing as how it's a combination of an issue in the web server parsing cookies, and the client setting malicious cookies, I'm not sure which party should be responsible for the bounty.