Reflected cross-site scripting vulnerabilities arise when data is copied from a request and echoed into the application's immediate response in an unsafe way. An attacker can use the vulnerability to construct a request which, if issued by another application user, will cause JavaScript code supplied by the attacker to execute within the user's browser in the context of that user's session with the application.
The attacker-supplied code can perform a wide variety of actions, such as stealing the victim's session token or login credentials, performing arbitrary actions on the victim's behalf, and logging their keystrokes.
Users can be induced to issue the attacker's crafted request in various ways. For example, the attacker can send a victim a link containing a malicious URL in an email or instant message. They can submit the link to popular web sites that allow content authoring, for example in blog comments. And they can create an innocuous looking web site which causes anyone viewing it to make arbitrary cross-domain requests to the vulnerable application (using either the GET or the POST method).
The security impact of cross-site scripting vulnerabilities is dependent upon the nature of the vulnerable application, the kinds of data and functionality which it contains, and the other applications which belong to the same domain and organisation. If the application is used only to display non-sensitive public content, with no authentication or access control functionality, then a cross-site scripting flaw may be considered low risk. However, if the same application resides on a domain which can access cookies for other more security-critical applications, then the vulnerability could be used to attack those other applications, and so may be considered high risk. Similarly, if the organisation which owns the application is a likely target for phishing attacks, then the vulnerability could be leveraged to lend credibility to such attacks, by injecting Trojan functionality into the vulnerable application, and exploiting users' trust in the organisation in order to capture credentials for other applications which it owns. In many kinds of application, such as those providing online banking functionality, cross-site scripting should always be considered high risk.
Remediation background
In most situations where user-controllable data is copied into application responses, cross-site scripting attacks can be prevented using two layers of defences:
Input should be validated as strictly as possible on arrival, given the kind of content which it is expected to contain. For example, personal names should consist of alphabetical and a small range of typographical characters, and be relatively short; a year of birth should consist of exactly four numerals; email addresses should match a well-defined regular expression. Input which fails the validation should be rejected, not sanitised.
User input should be HTML-encoded at any point where it is copied into application responses. All HTML metacharacters, including < > " ' and =, should be replaced with the corresponding HTML entities (< > etc).
In cases where the application's functionality allows users to author content using a restricted subset of HTML tags and attributes (for example, blog comments which allow limited formatting and linking), it is necessary to parse the supplied HTML to validate that it does not use any dangerous syntax; this is a non-trivial task.
The value of the qcat request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload c8d20\'%3balert(1)//ff63f7f2300 was submitted in the qcat parameter. This input was echoed as c8d20\\';alert(1)//ff63f7f2300 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The application attempts to prevent termination of the quoted JavaScript string by placing a backslash character (\) before any quotation mark characters contained within the input. The purpose of this defence is to escape the quotation mark and prevent it from terminating the string. However, the application fails to escape any backslash characters that already appear within the input itself. This enables an attacker to supply their own backslash character before the quotation mark, which has the effect of escaping the backslash character added by the application, and so the quotation mark remains unescaped and succeeds in terminating the string. This technique is used in the attack demonstrated.
Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context. If it is unavoidable to echo user input into a quoted JavaScript string the the backslash character should be blocked, or escaped by replacing it with two backslashes.
Request
GET /dogpile/ws/redir/_iceUrlFlag=11?_IceUrl=true&qcat=webc8d20\'%3balert(1)//ff63f7f2300&qkw= HTTP/1.1 Host: www.dogpile.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" id="DocumentRoot"> <head>
...[SNIP]... , more"; var addthis_offset_top = 20; var addthis_hover_delay = 0; var addthis_append_data = true; var addthis_share_url = 'http://www.dogpile.com/info.dogpl.rss/Webc8d20\\';Alert(1)//Ff63f7f2300/'; var callback_server_url = 'http://www.dogpile.com/clickcallbackserver/_iceUrlFlag=1?0=&1=0&4=173.193.214.243&5=173.193.214.243&9=7d43bcdc3ae442d4896bc16a3af0cb01&10=1&11=info.dogpl&14=1220 ...[SNIP]...
The value of the icePage%24SearchBoxTop%24qcat request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload d72e6\'%3b75d0d1bef7c was submitted in the icePage%24SearchBoxTop%24qcat parameter. This input was echoed as d72e6\\';75d0d1bef7c in the application's response.
This behaviour demonstrates that it is possible to terminate the JavaScript string into which our data is being copied. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
The application attempts to prevent termination of the quoted JavaScript string by placing a backslash character (\) before any quotation mark characters contained within the input. The purpose of this defence is to escape the quotation mark and prevent it from terminating the string. However, the application fails to escape any backslash characters that already appear within the input itself. This enables an attacker to supply their own backslash character before the quotation mark, which has the effect of escaping the backslash character added by the application, and so the quotation mark remains unescaped and succeeds in terminating the string. This technique is used in the attack demonstrated.
Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context. If it is unavoidable to echo user input into a quoted JavaScript string the the backslash character should be blocked, or escaped by replacing it with two backslashes.
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" id="DocumentRoot"> <head>
...[SNIP]... , more"; var addthis_offset_top = 20; var addthis_hover_delay = 0; var addthis_append_data = true; var addthis_share_url = 'http://www.dogpile.com/info.dogpl.rss/Webd72e6\\';75d0d1bef7c/site%3axss.cx'; var callback_server_url = 'http://www.dogpile.com/clickcallbackserver/_iceUrlFlag=1?0=&1=0&4=173.193.214.243&5=173.193.214.243&9=a63d211eee26414d9dd7c16a3af0cb01&10=1&11=info. ...[SNIP]...
The value of the icePage%24SearchBoxTop%24qcat request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 96402\'%3balert(1)//a2498f1a00b was submitted in the icePage%24SearchBoxTop%24qcat parameter. This input was echoed as 96402\\';alert(1)//a2498f1a00b in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The application attempts to prevent termination of the quoted JavaScript string by placing a backslash character (\) before any quotation mark characters contained within the input. The purpose of this defence is to escape the quotation mark and prevent it from terminating the string. However, the application fails to escape any backslash characters that already appear within the input itself. This enables an attacker to supply their own backslash character before the quotation mark, which has the effect of escaping the backslash character added by the application, and so the quotation mark remains unescaped and succeeds in terminating the string. This technique is used in the attack demonstrated.
Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context. If it is unavoidable to echo user input into a quoted JavaScript string the the backslash character should be blocked, or escaped by replacing it with two backslashes.
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" id="DocumentRoot"> <head>
...[SNIP]... , more"; var addthis_offset_top = 20; var addthis_hover_delay = 0; var addthis_append_data = true; var addthis_share_url = 'http://www.dogpile.com/info.dogpl.rss/Web96402\\';alert(1)//a2498f1a00b/'; var callback_server_url = 'http://www.dogpile.com/clickcallbackserver/_iceUrlFlag=1?0=&1=0&4=173.193.214.243&5=173.193.214.243&9=3bbca414522d42f7bc54c16a3af0cb01&10=1&11=info.dogpl.other&1 ...[SNIP]...
The value of the qcat request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload dc191</ScRiPt%20>b4d651e87b1 was submitted in the qcat parameter. This input was echoed as dc191</ScRiPt >b4d651e87b1 in the application's response.
This behaviour demonstrates that it is possible to can close the open <SCRIPT> tag and return to a plain text context. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
The application attempts to block certain expressions that are often used in XSS attacks but this can be circumvented by varying the case of the blocked expressions - for example, by submitting "ScRiPt" instead of "script".
Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context. Blacklist-based filters designed to block known bad inputs are usually inadequate and should be replaced with more effective input and output validation.
Request
GET /dogpile_other/ws/redir/_iceUrlFlag=11?_IceUrl=true&qcat=dc191</ScRiPt%20>b4d651e87b1 HTTP/1.1 Host: www.dogpile.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" id="DocumentRoot"> <head>
...[SNIP]... pon, more"; var addthis_offset_top = 20; var addthis_hover_delay = 0; var addthis_append_data = true; var addthis_share_url = 'http://www.dogpile.com/info.dogpl.rss/Dc191</Script >B4d651e87b1/'; var callback_server_url = 'http://www.dogpile.com/clickcallbackserver/_iceUrlFlag=1?0=&1=0&4=173.193.214.243&5=173.193.214.243&9=88a9cb4e452045dfbbd8c16a3af0cb01&10=1&11=info.dogpl.other&1 ...[SNIP]...
The value of the qcat request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload bdc14</script><script>alert(1)</script>bc3b9419cd was submitted in the qcat parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /dogpile_rss/ws/redir/_iceUrlFlag=11?_IceUrl=true&qcat=bdc14</script><script>alert(1)</script>bc3b9419cd HTTP/1.1 Host: www.dogpile.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" id="DocumentRoot"> <head>
...[SNIP]... pon, more"; var addthis_offset_top = 20; var addthis_hover_delay = 0; var addthis_append_data = true; var addthis_share_url = 'http://www.dogpile.com/info.dogpl.rss/Bdc14</Script><Script>Alert(1)</Script>Bc3b9419cd/'; var callback_server_url = 'http://www.dogpile.com/clickcallbackserver/_iceUrlFlag=1?0=&1=0&4=173.193.214.243&5=173.193.214.243&9=c64a3d65c7ff4b7dbcdfc16a3af0cb01&10=1&11=info.dogpl.rss&14= ...[SNIP]...
The value of the qcat request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 1d46d\'%3b6b7e482d682 was submitted in the qcat parameter. This input was echoed as 1d46d\\';6b7e482d682 in the application's response.
This behaviour demonstrates that it is possible to terminate the JavaScript string into which our data is being copied. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
The application attempts to prevent termination of the quoted JavaScript string by placing a backslash character (\) before any quotation mark characters contained within the input. The purpose of this defence is to escape the quotation mark and prevent it from terminating the string. However, the application fails to escape any backslash characters that already appear within the input itself. This enables an attacker to supply their own backslash character before the quotation mark, which has the effect of escaping the backslash character added by the application, and so the quotation mark remains unescaped and succeeds in terminating the string. This technique is used in the attack demonstrated.
Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context. If it is unavoidable to echo user input into a quoted JavaScript string the the backslash character should be blocked, or escaped by replacing it with two backslashes.
Request
GET /dogpile_rss/ws/redir/_iceUrlFlag=11?qcat=1d46d\'%3b6b7e482d682&qkw=Go%20Daddy%20CEO%20Elephant&qcoll=relevance&zoom=off&bepersistence=true&newtxn=false&qi=21&qk=20&page=2&_IceUrl=true HTTP/1.1 Host: www.dogpile.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" id="DocumentRoot"> <head>
...[SNIP]... pon, more"; var addthis_offset_top = 20; var addthis_hover_delay = 0; var addthis_append_data = true; var addthis_share_url = 'http://www.dogpile.com/info.dogpl.rss/1d46d\\';6b7e482d682/Go+Daddy+CEO+Elephant'; var callback_server_url = 'http://www.dogpile.com/clickcallbackserver/_iceUrlFlag=1?0=&1=0&4=173.193.214.243&5=173.193.214.243&9=a7dbe50ac6c642a88691c16a3af0cb01&10=1& ...[SNIP]...
The value of the qcat request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 6c5ea\'%3balert(1)//e445c104ee1 was submitted in the qcat parameter. This input was echoed as 6c5ea\\';alert(1)//e445c104ee1 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The application attempts to prevent termination of the quoted JavaScript string by placing a backslash character (\) before any quotation mark characters contained within the input. The purpose of this defence is to escape the quotation mark and prevent it from terminating the string. However, the application fails to escape any backslash characters that already appear within the input itself. This enables an attacker to supply their own backslash character before the quotation mark, which has the effect of escaping the backslash character added by the application, and so the quotation mark remains unescaped and succeeds in terminating the string. This technique is used in the attack demonstrated.
Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context. If it is unavoidable to echo user input into a quoted JavaScript string the the backslash character should be blocked, or escaped by replacing it with two backslashes.
Request
GET /dogpile_rss/ws/redir/_iceUrlFlag=11?rfcp=TopNavigation&rfcid=407&qcat=Web6c5ea\'%3balert(1)//e445c104ee1&qkw=MLB%20Schedule&newtxn=false&qcoll=Relevance&_IceUrl=true HTTP/1.1 Host: www.dogpile.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" id="DocumentRoot"> <head>
...[SNIP]... , more"; var addthis_offset_top = 20; var addthis_hover_delay = 0; var addthis_append_data = true; var addthis_share_url = 'http://www.dogpile.com/info.dogpl.rss/Web6c5ea\\';Alert(1)//E445c104ee1/MLB+Schedule'; var callback_server_url = 'http://www.dogpile.com/clickcallbackserver/_iceUrlFlag=1?0=&1=0&4=173.193.214.243&5=173.193.214.243&9=fe86ba7b839e447e97c1c16a3af0cb01&10=1&11=info.d ...[SNIP]...
The value of the DomainSession cookie is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 54db6"-alert(1)-"a2bb9b9271 was submitted in the DomainSession cookie. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
The value of the DomainSession cookie is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 33fd5"-alert(1)-"768c24deab8 was submitted in the DomainSession cookie. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
The value of the DomainSession cookie is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 7b752"-alert(1)-"af835610013 was submitted in the DomainSession cookie. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
The value of the DomainSession cookie is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 7b37d"-alert(1)-"effb104696b was submitted in the DomainSession cookie. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
The value of the DomainSession cookie is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 55b30"-alert(1)-"3ee9c7682b4 was submitted in the DomainSession cookie. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
The value of the DomainSession cookie is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 172f4"-alert(1)-"a0abe5fa114 was submitted in the DomainSession cookie. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /dogpile_other/ws/bookmark/rfcid=1211/_iceUrlFlag=11?_IceUrl=true HTTP/1.1 Host: www.dogpile.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: wsTemp=bigIP+3792213258.20480.0000+cacheId+ms20:1301676964559; wsRecent=Go+Daddy+CEO+Elephant,Web,Relevance,&MLB+Schedule,Web,Relevance,; wsViewRecent=1; DomainSession=TransactionId=93618d10e4ac4e349df4c16a3af0cb01&SessionId=9f70fd7ba5d44939a525c16a3af0cb01&PrevActionId=86d1546926784d5188d2c16a3af0cb01&ActionId=f1e07d8163f9435e87f8c16a3af0cb01&CookieDomain=.dogpile.com172f4"-alert(1)-"a0abe5fa114; DomainUserProfile=AnonymousId=9586353d328349b18887c16a3af0cb01&LastSeenDateTime=4/1/2011 4:56:05 PM&IssueDateTime=4/1/2011 4:55:38 PM&CookieDomain=.dogpile.com
The value of the DomainSession cookie is copied into a JavaScript string which is encapsulated in double quotation marks. The payload a6232"-alert(1)-"0b9efa05740 was submitted in the DomainSession cookie. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
The value of the DomainSession cookie is copied into a JavaScript string which is encapsulated in double quotation marks. The payload da425"-alert(1)-"23f7cc263dd was submitted in the DomainSession cookie. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
The value of the DomainSession cookie is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 21ae4"-alert(1)-"eecc2711024 was submitted in the DomainSession cookie. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /dogpile_other/ws/index HTTP/1.1 Host: www.dogpile.com Proxy-Connection: keep-alive Referer: http://dogpile.com/dogpile/ws/index/qcat=wp/_iceUrlFlag=11?_IceUrl=true User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: DomainSession=TransactionId=93618d10e4ac4e349df4c16a3af0cb01&SessionId=9f70fd7ba5d44939a525c16a3af0cb01&PrevActionId=9ca43f5d994646fab1d4c16a3af0cb01&ActionId=bc343352182e410c9000c16a3af0cb01&CookieDomain=.dogpile.com21ae4"-alert(1)-"eecc2711024; DomainUserProfile=AnonymousId=9586353d328349b18887c16a3af0cb01&LastSeenDateTime=4/1/2011 4:55:56 PM&IssueDateTime=4/1/2011 4:55:38 PM&CookieDomain=.dogpile.com
The value of the DomainSession cookie is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 37a9f"-alert(1)-"9ff850e7c98 was submitted in the DomainSession cookie. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /dogpile_other/ws/index HTTP/1.1 Host: www.dogpile.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: wsTemp=bigIP+3792213258.20480.0000+cacheId+ms20:1301676964559; wsRecent=Go+Daddy+CEO+Elephant,Web,Relevance,&MLB+Schedule,Web,Relevance,; wsViewRecent=1; DomainSession=TransactionId=93618d10e4ac4e349df4c16a3af0cb01&SessionId=9f70fd7ba5d44939a525c16a3af0cb01&PrevActionId=86d1546926784d5188d2c16a3af0cb01&ActionId=f1e07d8163f9435e87f8c16a3af0cb01&CookieDomain=.dogpile.com37a9f"-alert(1)-"9ff850e7c98; DomainUserProfile=AnonymousId=9586353d328349b18887c16a3af0cb01&LastSeenDateTime=4/1/2011 4:56:05 PM&IssueDateTime=4/1/2011 4:55:38 PM&CookieDomain=.dogpile.com
The value of the DomainSession cookie is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 8f72c"-alert(1)-"f359c353bfe was submitted in the DomainSession cookie. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
The value of the DomainSession cookie is copied into a JavaScript string which is encapsulated in double quotation marks. The payload d91bc"-alert(1)-"8a6ce0e863e was submitted in the DomainSession cookie. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
The value of the DomainSession cookie is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 24062"-alert(1)-"3197989eac9 was submitted in the DomainSession cookie. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /dogpile_other/ws/preferences/rfcid=415/rfcp=TopNavigation/_iceUrlFlag=11?_IceUrl=true HTTP/1.1 Host: www.dogpile.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: wsTemp=bigIP+3741881610.20480.0000+cacheId+ms17:1301677814261; wsRecent=april+fools+day+pranks,Web,Relevance,&MLB+Schedule,Web,Relevance,&Go+Daddy+CEO+Elephant,Web,Relevance,; wsViewRecent=1; DomainUserProfile=AnonymousId=8304cc0b8ab744899107c16a3af0cb01&LastSeenDateTime=4/1/2011 5:14:31 PM&IssueDateTime=4/1/2011 5:08:07 PM&CookieDomain=.dogpile.com; DomainSession=TransactionId=ba3967d21c5c40fc92fdc16a3af0cb01&SessionId=ee7a38726f9f4b44b1a6c16a3af0cb01&PrevActionId=e0a2585a54c44613a05fc16a3af0cb01&ActionId=cbef8ee057aa45668e6fc16a3af0cb01&CookieDomain=.dogpile.com24062"-alert(1)-"3197989eac9
The value of the DomainSession cookie is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 868e6"-alert(1)-"815bb4494be was submitted in the DomainSession cookie. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
The value of the DomainSession cookie is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 17e70"-alert(1)-"8009d3e9d2 was submitted in the DomainSession cookie. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /dogpile_other/ws/redir/qcat=Web/qcoll=relevance/qkw=Dark%20Sites/qlnk=1/rfcp=RightNav/rfcid=302360/_iceUrlFlag=11?_IceUrl=true HTTP/1.1 Host: www.dogpile.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: DomainUserProfile=AnonymousId=8304cc0b8ab744899107c16a3af0cb01&LastSeenDateTime=4/1/2011 5:15:13 PM&IssueDateTime=4/1/2011 5:08:07 PM&CookieDomain=.dogpile.com; wsTemp=bigIP+3808990474.20480.0000+cacheId+ms21:1301678113917; wsRecent=Review+Sites,Web,Relevance,&site%3axss.cx,Web,Relevance,&april+fools+day+pranks,Web,Relevance,&MLB+Schedule,Web,Relevance,&Go+Daddy+CEO+Elephant,Web,Relevance,; wsViewRecent=1; DomainSession=TransactionId=40db304f9bea4e6394bcc16a3af0cb01&SessionId=ee7a38726f9f4b44b1a6c16a3af0cb01&PrevActionId=afded22df52249fea4b3c16a3af0cb01&ActionId=03e0e226b781481fa972c16a3af0cb01&CookieDomain=.dogpile.com17e70"-alert(1)-"8009d3e9d2
The value of the DomainSession cookie is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 5784a"-alert(1)-"4be09a1635c was submitted in the DomainSession cookie. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /dogpile_other/ws/redir/qcat=Web/qcoll=relevance/qkw=Review%20Sites/qlnk=1/rfcp=RightNav/rfcid=302357/_iceUrlFlag=11?_IceUrl=true HTTP/1.1 Host: www.dogpile.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: DomainUserProfile=AnonymousId=8304cc0b8ab744899107c16a3af0cb01&LastSeenDateTime=4/1/2011 5:14:52 PM&IssueDateTime=4/1/2011 5:08:07 PM&CookieDomain=.dogpile.com; wsTemp=bigIP+3741881610.20480.0000+cacheId+ms17:1301678093005; wsRecent=site%3axss.cx,Web,Relevance,&april+fools+day+pranks,Web,Relevance,&MLB+Schedule,Web,Relevance,&Go+Daddy+CEO+Elephant,Web,Relevance,; wsViewRecent=1; DomainSession=TransactionId=8a9366cfe41848d795bec16a3af0cb01&SessionId=ee7a38726f9f4b44b1a6c16a3af0cb01&PrevActionId=c1a8f04152fd49d4bbd5c16a3af0cb01&ActionId=afded22df52249fea4b3c16a3af0cb01&CookieDomain=.dogpile.com5784a"-alert(1)-"4be09a1635c
The value of the DomainSession cookie is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 35970"-alert(1)-"f277aa05b72 was submitted in the DomainSession cookie. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /dogpile_other/ws/redir/qcat=Web/qcoll=relevance/qkw=Submit%20Site/qlnk=1/rfcp=RightNav/rfcid=302362/_iceUrlFlag=11?_IceUrl=true HTTP/1.1 Host: www.dogpile.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: wsTemp=bigIP+3808990474.20480.0000+cacheId+ms21:1301678113917; wsRecent=Review+Sites,Web,Relevance,&site%3axss.cx,Web,Relevance,&april+fools+day+pranks,Web,Relevance,&MLB+Schedule,Web,Relevance,&Go+Daddy+CEO+Elephant,Web,Relevance,; wsViewRecent=1; DomainUserProfile=AnonymousId=8304cc0b8ab744899107c16a3af0cb01&LastSeenDateTime=4/1/2011 5:15:16 PM&IssueDateTime=4/1/2011 5:08:07 PM&CookieDomain=.dogpile.com; DomainSession=TransactionId=40db304f9bea4e6394bcc16a3af0cb01&SessionId=ee7a38726f9f4b44b1a6c16a3af0cb01&PrevActionId=14be2b84e19340ef829ac16a3af0cb01&ActionId=f99d27d203c74389a638c16a3af0cb01&CookieDomain=.dogpile.com35970"-alert(1)-"f277aa05b72
The value of the DomainSession cookie is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 93152"-alert(1)-"816df919a4f was submitted in the DomainSession cookie. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /dogpile_other/ws/results/Web/Submit%20Site/1/302362/RightNav/Relevance/iq=true/zoom=off/qlnk=1/_iceUrlFlag=7?_IceUrl=true HTTP/1.1 Host: www.dogpile.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: wsTemp=bigIP+3808990474.20480.0000+cacheId+ms21:1301678113917; wsRecent=Review+Sites,Web,Relevance,&site%3axss.cx,Web,Relevance,&april+fools+day+pranks,Web,Relevance,&MLB+Schedule,Web,Relevance,&Go+Daddy+CEO+Elephant,Web,Relevance,; wsViewRecent=1; DomainSession=TransactionId=5d61898cfb714cd0bcc4c16a3af0cb01&SessionId=ee7a38726f9f4b44b1a6c16a3af0cb01&PrevActionId=14be2b84e19340ef829ac16a3af0cb01&ActionId=f99d27d203c74389a638c16a3af0cb01&CookieDomain=.dogpile.com93152"-alert(1)-"816df919a4f; DomainUserProfile=AnonymousId=8304cc0b8ab744899107c16a3af0cb01&LastSeenDateTime=4/1/2011 5:15:18 PM&IssueDateTime=4/1/2011 5:08:07 PM&CookieDomain=.dogpile.com
The value of the DomainSession cookie is copied into a JavaScript string which is encapsulated in double quotation marks. The payload c7886"-alert(1)-"78b4217b136 was submitted in the DomainSession cookie. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /dogpile_rss/web/GE+Zero+Taxes HTTP/1.1 Host: www.dogpile.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: DomainUserProfile=AnonymousId=9586353d328349b18887c16a3af0cb01&LastSeenDateTime=4/1/2011 4:56:02 PM&IssueDateTime=4/1/2011 4:55:38 PM&CookieDomain=.dogpile.com; wsTemp=bigIP+3758658826.20480.0000+cacheId+ms18:1301676962746; wsRecent=MLB+Schedule,Web,Relevance,; wsViewRecent=1; DomainSession=TransactionId=93618d10e4ac4e349df4c16a3af0cb01&SessionId=9f70fd7ba5d44939a525c16a3af0cb01&PrevActionId=62fda6b6aa3440d49bc7c16a3af0cb01&ActionId=86d1546926784d5188d2c16a3af0cb01&CookieDomain=.dogpile.comc7886"-alert(1)-"78b4217b136
The value of the DomainSession cookie is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 66b73"-alert(1)-"6a66de51dba was submitted in the DomainSession cookie. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /dogpile_rss/web/Go+Daddy+CEO+Elephant HTTP/1.1 Host: www.dogpile.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: DomainSession=TransactionId=93618d10e4ac4e349df4c16a3af0cb01&SessionId=9f70fd7ba5d44939a525c16a3af0cb01&PrevActionId=62fda6b6aa3440d49bc7c16a3af0cb01&ActionId=86d1546926784d5188d2c16a3af0cb01&CookieDomain=.dogpile.com66b73"-alert(1)-"6a66de51dba; DomainUserProfile=AnonymousId=9586353d328349b18887c16a3af0cb01&LastSeenDateTime=4/1/2011 4:56:02 PM&IssueDateTime=4/1/2011 4:55:38 PM&CookieDomain=.dogpile.com; wsTemp=bigIP+3758658826.20480.0000+cacheId+ms18:1301676962746; wsRecent=MLB+Schedule,Web,Relevance,
The value of the DomainSession cookie is copied into a JavaScript string which is encapsulated in double quotation marks. The payload b56e7"-alert(1)-"2b8c3a90ea was submitted in the DomainSession cookie. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
The value of the DomainSession cookie is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 6a4fb"-alert(1)-"9c0762a1d15 was submitted in the DomainSession cookie. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /dogpile_rss/ws/faq/_iceUrlFlag=11?_IceUrl=true HTTP/1.1 Host: www.dogpile.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: DomainUserProfile=AnonymousId=9586353d328349b18887c16a3af0cb01&LastSeenDateTime=4/1/2011 4:59:34 PM&IssueDateTime=4/1/2011 4:55:38 PM&CookieDomain=.dogpile.com; wsTemp=bigIP+3725104394.20480.0000+cacheId+ms16:1301677190970; wsRecent=MLB+Schedule,Web,Relevance,&Go+Daddy+CEO+Elephant,Web,Relevance,; wsViewRecent=1; DomainSession=TransactionId=93618d10e4ac4e349df4c16a3af0cb01&SessionId=9f70fd7ba5d44939a525c16a3af0cb01&PrevActionId=0bca44db8e72477aac9fc16a3af0cb01&ActionId=fe86ba7b839e447e97c1c16a3af0cb01&CookieDomain=.dogpile.com6a4fb"-alert(1)-"9c0762a1d15
The value of the DomainSession cookie is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 193eb"-alert(1)-"b095a032310 was submitted in the DomainSession cookie. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /dogpile_rss/ws/index/?_IceUrl=true HTTP/1.1 Host: www.dogpile.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: wsTemp=bigIP+3725104394.20480.0000+cacheId+ms16:1301677190970; wsRecent=MLB+Schedule,Web,Relevance,&Go+Daddy+CEO+Elephant,Web,Relevance,; wsViewRecent=1; DomainUserProfile=AnonymousId=8304cc0b8ab744899107c16a3af0cb01&LastSeenDateTime=4/1/2011 5:08:30 PM&IssueDateTime=4/1/2011 5:08:07 PM&CookieDomain=.dogpile.com; DomainSession=TransactionId=26f28f0af78442bc9f5bc16a3af0cb01&SessionId=d357b6175b6f40c6abe8c16a3af0cb01&PrevActionId=efab2d4d5b684fe9b96cc16a3af0cb01&ActionId=fc23be7bf89f4d2eac78c16a3af0cb01&CookieDomain=.dogpile.com193eb"-alert(1)-"b095a032310
The value of the DomainSession cookie is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 55c43"-alert(1)-"46f043feb84 was submitted in the DomainSession cookie. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /favicon.ico HTTP/1.1 Host: www.dogpile.com Proxy-Connection: keep-alive Accept: */* User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 Safari/534.16 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: wsTemp=bigIP+3725104394.20480.0000+cacheId+ms16:1301677190970; wsRecent=MLB+Schedule,Web,Relevance,&Go+Daddy+CEO+Elephant,Web,Relevance,; wsViewRecent=1; DomainSession=TransactionId=93618d10e4ac4e349df4c16a3af0cb01&SessionId=9f70fd7ba5d44939a525c16a3af0cb01&PrevActionId=5b843be01d96476c9873c16a3af0cb01&ActionId=d139d0f78e1a40d2844cc16a3af0cb01&CookieDomain=.dogpile.com55c43"-alert(1)-"46f043feb84; DomainUserProfile=AnonymousId=9586353d328349b18887c16a3af0cb01&LastSeenDateTime=4/1/2011 5:07:45 PM&IssueDateTime=4/1/2011 4:55:38 PM&CookieDomain=.dogpile.com
The value of the DomainSession cookie is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 1df86"-alert(1)-"c22c881b4b3 was submitted in the DomainSession cookie. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /info.dogpl.rss/Web6c5ea//';Alert(%22Xss%22)//E445c104ee1/MLB+Schedule HTTP/1.1 Host: www.dogpile.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: wsTemp=bigIP+3725104394.20480.0000+cacheId+ms16:1301677190970; wsRecent=MLB+Schedule,Web,Relevance,&Go+Daddy+CEO+Elephant,Web,Relevance,; wsViewRecent=1; DomainUserProfile=AnonymousId=8304cc0b8ab744899107c16a3af0cb01&LastSeenDateTime=4/1/2011 5:08:30 PM&IssueDateTime=4/1/2011 5:08:07 PM&CookieDomain=.dogpile.com; DomainSession=TransactionId=26f28f0af78442bc9f5bc16a3af0cb01&SessionId=d357b6175b6f40c6abe8c16a3af0cb01&PrevActionId=efab2d4d5b684fe9b96cc16a3af0cb01&ActionId=fc23be7bf89f4d2eac78c16a3af0cb01&CookieDomain=.dogpile.com1df86"-alert(1)-"c22c881b4b3
The value of the DomainSession cookie is copied into a JavaScript string which is encapsulated in double quotation marks. The payload ae01e"-alert(1)-"a0d5d5414f7 was submitted in the DomainSession cookie. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /info.dogpl.rss/web/GE+Zero+Taxes HTTP/1.1 Host: www.dogpile.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: DomainUserProfile=AnonymousId=9586353d328349b18887c16a3af0cb01&LastSeenDateTime=4/1/2011 4:56:02 PM&IssueDateTime=4/1/2011 4:55:38 PM&CookieDomain=.dogpile.com; wsTemp=bigIP+3758658826.20480.0000+cacheId+ms18:1301676962746; wsRecent=MLB+Schedule,Web,Relevance,; wsViewRecent=1; DomainSession=TransactionId=93618d10e4ac4e349df4c16a3af0cb01&SessionId=9f70fd7ba5d44939a525c16a3af0cb01&PrevActionId=62fda6b6aa3440d49bc7c16a3af0cb01&ActionId=86d1546926784d5188d2c16a3af0cb01&CookieDomain=.dogpile.comae01e"-alert(1)-"a0d5d5414f7
The value of the DomainSession cookie is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 6cfb5"-alert(1)-"011a7e5ee80 was submitted in the DomainSession cookie. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /info.dogpl.rss/web/Go+Daddy+CEO+Elephant HTTP/1.1 Host: www.dogpile.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: DomainUserProfile=AnonymousId=9586353d328349b18887c16a3af0cb01&LastSeenDateTime=4/1/2011 4:55:44 PM&IssueDateTime=4/1/2011 4:55:38 PM&CookieDomain=.dogpile.com; DomainSession=TransactionId=93618d10e4ac4e349df4c16a3af0cb01&SessionId=9f70fd7ba5d44939a525c16a3af0cb01&PrevActionId=91f95e6548a4490186bdc16a3af0cb01&ActionId=62fda6b6aa3440d49bc7c16a3af0cb01&CookieDomain=.dogpile.com6cfb5"-alert(1)-"011a7e5ee80
The value of the DomainSession cookie is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 2f96a"-alert(1)-"0cf0cd42d43 was submitted in the DomainSession cookie. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /info.dogpl.rss/web/MLB+Schedule HTTP/1.1 Host: www.dogpile.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 Safari/534.16 Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: DomainUserProfile=AnonymousId=9586353d328349b18887c16a3af0cb01&LastSeenDateTime=4/1/2011 4:55:44 PM&IssueDateTime=4/1/2011 4:55:38 PM&CookieDomain=.dogpile.com; DomainSession=TransactionId=93618d10e4ac4e349df4c16a3af0cb01&SessionId=9f70fd7ba5d44939a525c16a3af0cb01&PrevActionId=91f95e6548a4490186bdc16a3af0cb01&ActionId=62fda6b6aa3440d49bc7c16a3af0cb01&CookieDomain=.dogpile.com2f96a"-alert(1)-"0cf0cd42d43