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

XSS in hoovers.com | Vulnerability Crawler Report

Report generated by CloudScan Vulnerability Crawler at Sun Jan 30 11:19:14 CST 2011.



DORK CWE-79 XSS Report

Loading

1. Cross-site scripting (reflected)

2. Flash cross-domain policy

3. Cookie scoped to parent domain

4. Cross-domain script include

5. Cookie without HttpOnly flag set

5.1. http://www.hoovers.com/business-information/--pageid__13823--/global-mktg-index.xhtml

5.2. http://www.hoovers.com/favicon.ico

6. Robots.txt file

7. HTML does not specify charset

8. Content type incorrectly stated



1. Cross-site scripting (reflected)  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.hoovers.com
Path:   /business-information/--pageid__13823--/global-mktg-index.xhtml

Issue detail

The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 7ffa5"%3balert(1)//4d5eca5bcd1 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 7ffa5";alert(1)//4d5eca5bcd1 in the application's response.

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

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.

Issue background

Reflected cross-site scripting vulnerabilities arise when data is copied from a request and echoed into the application's immediate response in an unsafe way. An attacker can use the vulnerability to construct a request which, if issued by another application user, will cause JavaScript code supplied by the attacker to execute within the user's browser in the context of that user's session with the application.

The attacker-supplied code can perform a wide variety of actions, such as stealing the victim's session token or login credentials, performing arbitrary actions on the victim's behalf, and logging their keystrokes.

Users can be induced to issue the attacker's crafted request in various ways. For example, the attacker can send a victim a link containing a malicious URL in an email or instant message. They can submit the link to popular web sites that allow content authoring, for example in blog comments. And they can create an innocuous looking web site which causes anyone viewing it to make arbitrary cross-domain requests to the vulnerable application (using either the GET or the POST method).

The security impact of cross-site scripting vulnerabilities is dependent upon the nature of the vulnerable application, the kinds of data and functionality which it contains, and the other applications which belong to the same domain and organisation. If the application is used only to display non-sensitive public content, with no authentication or access control functionality, then a cross-site scripting flaw may be considered low risk. However, if the same application resides on a domain which can access cookies for other more security-critical applications, then the vulnerability could be used to attack those other applications, and so may be considered high risk. Similarly, if the organisation which owns the application is a likely target for phishing attacks, then the vulnerability could be leveraged to lend credibility to such attacks, by injecting Trojan functionality into the vulnerable application, and exploiting users' trust in the organisation in order to capture credentials for other applications which it owns. In many kinds of application, such as those providing online banking functionality, cross-site scripting should always be considered high risk.

Remediation background

In most situations where user-controllable data is copied into application responses, cross-site scripting attacks can be prevented using two layers of defenses:In cases where the application's functionality allows users to author content using a restricted subset of HTML tags and attributes (for example, blog comments which allow limited formatting and linking), it is necessary to parse the supplied HTML to validate that it does not use any dangerous syntax; this is a non-trivial task.

Request

GET /business-information/--pageid__13823--/global-mktg-index.xhtml?7ffa5"%3balert(1)//4d5eca5bcd1=1 HTTP/1.1
Host: www.hoovers.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 500 Internal Server Error
Date: Sun, 30 Jan 2011 01:53:42 GMT
Server: Apache
Cache-Control: no-store, nocache, must-revalidate, private, post-check=0, pre-check=0
Expires: Sat, 26 Jul 1997 05:00:00 GMT
X-Powered-By: PHP/5.2.8
Last-Modified: Sun, 30 Jan 2011 01:53:42 GMT
Pragma: no-cache
Content-Type: text/html
Set-Cookie: HID=173.193.214.243.1296352422574219; path=/; expires=Fri, 29-Jan-16 01:53:42 GMT; domain=.hoovers.com
Set-Cookie: HID=10.1.1.227.151141296352422579; path=/; expires=Fri, 29-Jan-16 01:53:42 GMT; domain=.hoovers.com
Set-Cookie: BIGipServerholpriv-colo1=1342243082.20480.0000; path=/
P3P: CP="NON DSP COR ADM DEV CONo TELo DELo SAMo OTRo UNRo LEG PRE"
Connection: close
Set-Cookie: BIGipServerwww-1=1341968906.20480.0000; path=/
Content-Length: 4106

<!doctype html public "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html>
<head>
<title>We're Sorry</title>
<meta http-equiv="Expires" content="0" />
<meta h
...[SNIP]...
s.prop3=s.getTimeParting('w','-6',2011);
s.channel = "hoovers";
s.server = "hoovers.com";
s.prop4 = "paid";
s.prop8 = "500";
s.prop15 = "/global/mktg/index.xhtml?pageid=13823&7ffa5";alert(1)//4d5eca5bcd1=1";
s.prop49 = "";
s.prop44 = "Registered:Logged In";


buildOmnitureGeneric();
signifyError("500");
</script>
...[SNIP]...

2. Flash cross-domain policy  previous  next

Summary

Severity:   Low
Confidence:   Certain
Host:   http://www.hoovers.com
Path:   /crossdomain.xml

Issue detail

The application publishes a Flash cross-domain policy which uses a wildcard to specify allowed domains, and allows access from specific other domains.

Using a wildcard to specify allowed domains means that any domain matching the wildcard expression can perform two-way interaction with this application. You should only use this policy if you fully trust every possible web site that may reside on a domain which matches the wildcard expression.

Allowing access from specific domains means that web sites on those domains can perform two-way interaction with this application. You should only use this policy if you fully trust the specific domains allowed by the policy.

Issue background

The Flash cross-domain policy controls whether Flash client components running on other domains can perform two-way interaction with the domain which publishes the policy. If another domain is allowed by the policy, then that domain can potentially attack users of the application. If a user is logged in to the application, and visits a domain allowed by the policy, then any malicious content running on that domain can potentially gain full access to the application within the security context of the logged in user.

Even if an allowed domain is not overtly malicious in itself, security vulnerabilities within that domain could potentially be leveraged by a third-party attacker to exploit the trust relationship and attack the application which allows access.

Issue remediation

You should review the domains which are allowed by the Flash cross-domain policy and determine whether it is appropriate for the application to fully trust both the intentions and security posture of those domains.

Request

GET /crossdomain.xml HTTP/1.0
Host: www.hoovers.com

Response

HTTP/1.1 200 OK
Date: Sun, 30 Jan 2011 01:53:36 GMT
Server: Apache
Last-Modified: Fri, 21 Jan 2011 00:59:01 GMT
ETag: "bf"
Accept-Ranges: bytes
Content-Length: 191
Vary: Accept-Encoding
Content-Type: text/xml
Set-Cookie: HID=173.193.214.243.1296352416699562; path=/; expires=Fri, 29-Jan-16 01:53:36 GMT; domain=.hoovers.com
Set-Cookie: BIGipServerhaspriv-colo1=201052682.20480.0000; path=/
P3P: CP="NON DSP COR ADM DEV CONo TELo DELo SAMo OTRo UNRo LEG PRE"
Connection: close
Set-Cookie: BIGipServerwww-1=1341968906.20480.0000; path=/

<?xml version="1.0"?>
<cross-domain-policy>
       <allow-access-from domain="*.brightcove.com" secure="false"/>
       <allow-access-from domain="*.hoovers.com" secure="false"/>
</cross-domain-policy>

3. Cookie scoped to parent domain  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.hoovers.com
Path:   /business-information/--pageid__13823--/global-mktg-index.xhtml

Issue detail

The following cookies were issued by the application and is scoped to a parent of the issuing domain:The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.

Issue background

A cookie's domain attribute determines which domains can access the cookie. Browsers will automatically submit the cookie in requests to in-scope domains, and those domains will also be able to access the cookie via JavaScript. If a cookie is scoped to a parent domain, then that cookie will be accessible by the parent domain and also by any other subdomains of the parent domain. If the cookie contains sensitive data (such as a session token) then this data may be accessible by less trusted or less secure applications residing at those domains, leading to a security compromise.

Issue remediation

By default, cookies are scoped to the issuing domain and all subdomains. If you remove the explicit domain attribute from your Set-cookie directive, then the cookie will have this default scope, which is safe and appropriate in most situations. If you particularly need a cookie to be accessible by a parent domain, then you should thoroughly review the security of the applications residing on that domain and its subdomains, and confirm that you are willing to trust the people and systems which support those applications.

Request

GET /business-information/--pageid__13823--/global-mktg-index.xhtml HTTP/1.1
Host: www.hoovers.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Date: Sun, 30 Jan 2011 01:53:36 GMT
Server: Apache
Cache-Control: max-age=3600
Expires: Sun, 30 Jan 2011 02:53:36 GMT
X-Powered-By: PHP/5.2.8
Content-Type: text/html
Set-Cookie: HID=173.193.214.243.1296352416131983; path=/; expires=Fri, 29-Jan-16 01:53:36 GMT; domain=.hoovers.com
Set-Cookie: HID=10.1.1.227.283831296352416137; path=/; expires=Fri, 29-Jan-16 01:53:36 GMT; domain=.hoovers.com
Set-Cookie: BIGipServerholpriv-colo1=1140916490.20480.0000; path=/
P3P: CP="NON DSP COR ADM DEV CONo TELo DELo SAMo OTRo UNRo LEG PRE"
Connection: close
Set-Cookie: BIGipServerwww-1=1341968906.20480.0000; path=/
Content-Length: 18009

<!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>
<title>Take Th
...[SNIP]...

4. Cross-domain script include  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.hoovers.com
Path:   /business-information/--pageid__13823--/global-mktg-index.xhtml

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 /business-information/--pageid__13823--/global-mktg-index.xhtml HTTP/1.1
Host: www.hoovers.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Date: Sun, 30 Jan 2011 01:53:36 GMT
Server: Apache
Cache-Control: max-age=3600
Expires: Sun, 30 Jan 2011 02:53:36 GMT
X-Powered-By: PHP/5.2.8
Content-Type: text/html
Set-Cookie: HID=173.193.214.243.1296352416131983; path=/; expires=Fri, 29-Jan-16 01:53:36 GMT; domain=.hoovers.com
Set-Cookie: HID=10.1.1.227.283831296352416137; path=/; expires=Fri, 29-Jan-16 01:53:36 GMT; domain=.hoovers.com
Set-Cookie: BIGipServerholpriv-colo1=1140916490.20480.0000; path=/
P3P: CP="NON DSP COR ADM DEV CONo TELo DELo SAMo OTRo UNRo LEG PRE"
Connection: close
Set-Cookie: BIGipServerwww-1=1341968906.20480.0000; path=/
Content-Length: 18009

<!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>
<title>Take Th
...[SNIP]...
</script>

<script type="text/javascript" src="http://js.bizographics.com/convert_data.js?partner_id=169"></script>
...[SNIP]...

5. Cookie without HttpOnly flag set  previous  next
There are 2 instances of this issue:

Issue background

If the HttpOnly attribute is set on a cookie, then the cookie's value cannot be read or set by client-side JavaScript. This measure can prevent certain client-side attacks, such as cross-site scripting, from trivially capturing the cookie's value via an injected script.

Issue remediation

There is usually no good reason not to set the HttpOnly flag on all cookies. Unless you specifically require legitimate client-side scripts within your application to read or set a cookie's value, you should set the HttpOnly flag by including this attribute within the relevant Set-cookie directive.

You should be aware that the restrictions imposed by the HttpOnly flag can potentially be circumvented in some circumstances, and that numerous other serious attacks can be delivered by client-side script injection, aside from simple cookie stealing.



5.1. http://www.hoovers.com/business-information/--pageid__13823--/global-mktg-index.xhtml  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.hoovers.com
Path:   /business-information/--pageid__13823--/global-mktg-index.xhtml

Issue detail

The following cookies were issued by the application and do not have the HttpOnly flag set:The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.

Request

GET /business-information/--pageid__13823--/global-mktg-index.xhtml HTTP/1.1
Host: www.hoovers.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Date: Sun, 30 Jan 2011 01:53:36 GMT
Server: Apache
Cache-Control: max-age=3600
Expires: Sun, 30 Jan 2011 02:53:36 GMT
X-Powered-By: PHP/5.2.8
Content-Type: text/html
Set-Cookie: HID=173.193.214.243.1296352416131983; path=/; expires=Fri, 29-Jan-16 01:53:36 GMT; domain=.hoovers.com
Set-Cookie: HID=10.1.1.227.283831296352416137; path=/; expires=Fri, 29-Jan-16 01:53:36 GMT; domain=.hoovers.com
Set-Cookie: BIGipServerholpriv-colo1=1140916490.20480.0000; path=/
P3P: CP="NON DSP COR ADM DEV CONo TELo DELo SAMo OTRo UNRo LEG PRE"
Connection: close
Set-Cookie: BIGipServerwww-1=1341968906.20480.0000; path=/
Content-Length: 18009

<!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>
<title>Take Th
...[SNIP]...

5.2. http://www.hoovers.com/favicon.ico  previous

Summary

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

Issue detail

The following cookie was issued by the application and does not have the HttpOnly flag set:The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.

Request

GET /favicon.ico HTTP/1.1
Host: www.hoovers.com
Proxy-Connection: keep-alive
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.237 Safari/534.10
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: HID=10.1.1.227.122391296352471936; BIGipServerholpriv-colo1=1342243082.20480.0000; BIGipServerwww-1=1341968906.20480.0000; s_cc=true; s_nr=1296352492087; s_ats=undefinedburpburpReferrersReferrers; ctc2=1; s_sq=%5B%5BB%5D%5D; s_vi=[CS]v1|26A26274851D2CD5-60000130C044F459[CE]

Response

HTTP/1.1 200 OK
Date: Sun, 30 Jan 2011 01:54:56 GMT
Server: Apache
Last-Modified: Fri, 09 Oct 2009 00:43:07 GMT
ETag: "e36"
Accept-Ranges: bytes
Content-Length: 3638
Content-Type: text/plain; charset=UTF-8
Set-Cookie: BIGipServerhaspriv-colo1=251384330.20480.0000; path=/
P3P: CP="NON DSP COR ADM DEV CONo TELo DELo SAMo OTRo UNRo LEG PRE"

..............h...&... ..............(....... ...........@...........................Y*................................................................................................................
...[SNIP]...

6. Robots.txt file  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.hoovers.com
Path:   /business-information/--pageid__13823--/global-mktg-index.xhtml

Issue detail

The web server contains a robots.txt file.

Issue background

The file robots.txt is used to give instructions to web robots, such as search engine crawlers, about locations within the web site which robots are allowed, or not allowed, to crawl and index.

The presence of the robots.txt does not in itself present any kind of security vulnerability. However, it is often used to identify restricted or private areas of a site's contents. The information in the file may therefore help an attacker to map out the site's contents, especially if some of the locations identified are not linked from elsewhere in the site. If the application relies on robots.txt to protect access to these areas, and does not enforce proper access control over them, then this presents a serious vulnerability.

Issue remediation

The robots.txt file is not itself a security threat, and its correct use can represent good practice for non-security reasons. You should not assume that all web robots will honour the file's instructions. Rather, assume that attackers will pay close attention to any locations identified in the file. Do not rely on robots.txt to provide any kind of protection over unauthorised access.

Request

GET /robots.txt HTTP/1.0
Host: www.hoovers.com

Response

HTTP/1.1 200 OK
Date: Sun, 30 Jan 2011 01:53:37 GMT
Server: Apache
Last-Modified: Wed, 14 Jul 2010 18:11:37 GMT
ETag: "488"
Accept-Ranges: bytes
Content-Length: 1160
Vary: Accept-Encoding
Content-Type: text/plain; charset=UTF-8
Set-Cookie: HID=173.193.214.243.1296352417437192; path=/; expires=Fri, 29-Jan-16 01:53:37 GMT; domain=.hoovers.com
Set-Cookie: BIGipServerhaspriv-colo1=217829898.20480.0000; path=/
P3P: CP="NON DSP COR ADM DEV CONo TELo DELo SAMo OTRo UNRo LEG PRE"
Connection: close
Set-Cookie: BIGipServerwww-1=1341968906.20480.0000; path=/

# robots.txt for Hoover's Online http://www.hoovers.com/
# For information about Hoover's Online please contact
# webadmin@hoovers.com
#

User-agent: *
Disallow: /cgi-bin/ # Need to provide paramete
...[SNIP]...

7. HTML does not specify charset  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.hoovers.com
Path:   /business-information/--pageid__13823--/global-mktg-index.xhtml

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.

Request

GET /business-information/--pageid__13823--/global-mktg-index.xhtml HTTP/1.1
Host: www.hoovers.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Date: Sun, 30 Jan 2011 01:53:36 GMT
Server: Apache
Cache-Control: max-age=3600
Expires: Sun, 30 Jan 2011 02:53:36 GMT
X-Powered-By: PHP/5.2.8
Content-Type: text/html
Set-Cookie: HID=173.193.214.243.1296352416131983; path=/; expires=Fri, 29-Jan-16 01:53:36 GMT; domain=.hoovers.com
Set-Cookie: HID=10.1.1.227.283831296352416137; path=/; expires=Fri, 29-Jan-16 01:53:36 GMT; domain=.hoovers.com
Set-Cookie: BIGipServerholpriv-colo1=1140916490.20480.0000; path=/
P3P: CP="NON DSP COR ADM DEV CONo TELo DELo SAMo OTRo UNRo LEG PRE"
Connection: close
Set-Cookie: BIGipServerwww-1=1341968906.20480.0000; path=/
Content-Length: 18009

<!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>
<title>Take Th
...[SNIP]...

8. Content type incorrectly stated  previous

Summary

Severity:   Information
Confidence:   Firm
Host:   http://www.hoovers.com
Path:   /favicon.ico

Issue detail

The response contains the following Content-type statement:The response states that it contains plain text. However, it actually appears to contain unrecognised content.

Issue background

If a web response specifies an incorrect content type, then browsers may process the response in unexpected ways. If the specified content type is a renderable text-based format, then the browser will usually attempt to parse and render the response in that format. If the specified type is an image format, then the browser will usually detect the anomaly and will analyse the actual content and attempt to determine its MIME type. Either case can lead to unexpected results, and if the content contains any user-controllable data may lead to cross-site scripting or other client-side vulnerabilities.

In most cases, the presence of an incorrect content type statement 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 a message body, the application should include a single Content-type header which correctly and unambiguously states the MIME type of the content in the response body.

Request

GET /favicon.ico HTTP/1.1
Host: www.hoovers.com
Proxy-Connection: keep-alive
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.237 Safari/534.10
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: HID=10.1.1.227.122391296352471936; BIGipServerholpriv-colo1=1342243082.20480.0000; BIGipServerwww-1=1341968906.20480.0000; s_cc=true; s_nr=1296352492087; s_ats=undefinedburpburpReferrersReferrers; ctc2=1; s_sq=%5B%5BB%5D%5D; s_vi=[CS]v1|26A26274851D2CD5-60000130C044F459[CE]

Response

HTTP/1.1 200 OK
Date: Sun, 30 Jan 2011 01:54:56 GMT
Server: Apache
Last-Modified: Fri, 09 Oct 2009 00:43:07 GMT
ETag: "e36"
Accept-Ranges: bytes
Content-Length: 3638
Content-Type: text/plain; charset=UTF-8
Set-Cookie: BIGipServerhaspriv-colo1=251384330.20480.0000; path=/
P3P: CP="NON DSP COR ADM DEV CONo TELo DELo SAMo OTRo UNRo LEG PRE"

..............h...&... ..............(....... ...........@...........................Y*................................................................................................................
...[SNIP]...

Report generated by CloudScan Vulnerability Crawler at Sun Jan 30 11:19:14 CST 2011.