News for hackers. Stuff that matters.
Re:JSON is not as safe as people think it is by fmavituna on Wednesday March 27, 2013 @10:50AM (#5449700)
Yes it's indeed correct and document.

CORS safely solves this problem. http://en.wikipedia.org/wiki/Cross-origin_resource_sharing

Re:JSON is not as safe as people think it is by neya on Wednesday March 27, 2013 @10:57AM (#5449741)
Wow, thanks mate! I never knew of CORS before.. (I admit).
Re:JSON is not as safe as people think it is by jcampbell1 on Wednesday March 27, 2013 @11:11AM (#5449829)
CORS does nothing to address this problem. If you expose private data via CORS or JSONP you face the exact same problem.

CORS solves a different problem, in that you don't have to eval 3rd party code. If the remote service provider gets hacked, then your site may not get compromised.

Re:JSON is not as safe as people think it is by fmavituna on Wednesday March 27, 2013 @11:16AM (#5449870)
The issue is an external file can be called from a 3rd party website via "<script src=" and if the format is something that JavaScript interpreter understands then it's possible to hijack the data (so called JavaScript/JSON Hijacking).

CORS solves it because you can WHITELIST the domains that can access the data, which is huge! Just like crossdomain.xml in Flash and ContenPolicy in Silverlight.

You are right though if the format is still JSON you are still vulnerable to the same attack, however CORS doesn't require you to use any format particularly, so it's possibly to use any other data format.