lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sat, 15 Mar 2014 09:46:27 -0700 From: Michal Zalewski <lcamtuf@...edump.cx> To: M Kirschbaum <pr0ix@...oo.co.uk> Cc: "full-disclosure@...ts.grok.org.uk" <full-disclosure@...ts.grok.org.uk> Subject: Re: Fwd: Google vulnerabilities with PoC > As a professional penetration tester, [...] > The JSON service responds to GET requests , and there is a good chance that > the service is also vulnerable to JSON Hijacking attacks. That's... not how XSSI works. To have a script inclusion vulnerability, you need to have a vanilla GET response that contains some user-specific secrets that are returned to the caller based on HTTP cookies (or, less likely, other "ambient" credentials). For example, a script response that discloses the contents of your mailbox or the list of private contacts would be of concern. Further, the response must be in a format that can be not only loaded, but also inspected by another site opened in your browser; most types of JSONP fall into this category, but JSON generally does not, essentially because of how the meaning of "{" is overloaded in JS depending on where it appears in a block of code. Last but not least, the final piece of the puzzle is that the response must be served at a URL that can be guessed by third parties who don't have access to your account. /mz _______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.grok.org.uk/full-disclosure-charter.html Hosted and sponsored by Secunia - http://secunia.com/
Powered by blists - more mailing lists