Hacker News Reader

Wait a second, could you not read my google login session cookie from this page with a seamless iframe to a google domain? Again, like the person above, I didn't really understand what's going on here.

View on HN

no cookie/XSS or any real vuln here involved. This is completely standard design problem of sandbox domain. Check out http://homakov.github.io/guc.html

Oh, btw, also, you may be interested in window.setTimeout.

i am js jedi, but don't spend much time on PoCs.

Google uses a different domain for user content, namely googleusercontent.com.

What's the definition of "user content"?

Untrustworthy scripts, HTML, images, email attachments.

But I'm logged in! It shows myname in the corner. So obviously you could get that cookie, right?

Part with yourname is other_origin. I change content of GUC Page 2 using GUC Page 1 through other_origin (translate.google.com). No XSS or cookies. Just standards :D

I seriously admire your patience in replying to comments.

I have no life.

I was only referring to your continuing lengthy, polite comments when replying to commenters' questions. :)

:) it's pleasant to explain hacks you discover.

actually PoC is fixed - http://homakov.blogspot.com.es/2013/07/googleusercontentcom-...

Reply on news.ycombinator.com