wikia.com, XSS, Cross Site Scripting, CWe-79

The value of the actionName request parameter is copied into the HTML document as text between TITLE tags. The payload b2c83</title><script>alert(1)</script>95be19a1de3 was submitted in the actionName 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 defenses:

Input should be validated as strictly as possible on arrival, given the kind of content which it is expected to contain. For example, personal names should consist of alphabetical and a small range of typographical characters, and be relatively short; a year of birth should consist of exactly four numerals; email addresses should match a well-defined regular expression. Input which fails the validation should be rejected, not sanitised.
User input should be HTML-encoded at any point where it is copied into application responses. All HTML metacharacters, including < > " ' and =, should be replaced with the corresponding HTML entities (< > etc).

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 /index.php?action=ajax&rs=moduleProxy&moduleName=LatestActivity&actionName=Indexb2c83</title><script>alert(1)</script>95be19a1de3&outputType=html HTTP/1.1
Host: www.wikia.com
Proxy-Connection: keep-alive
Referer: http://www.wikia.com/Wikia
X-Requested-With: XMLHttpRequest
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.98 Safari/534.13
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: Geo={"city":"Dallas","country":"US","continent":"NA"}; varnish-stat=/server/ASH/varnish-v11-ASH/HIT/; loadtime=S1297646556.728570461,VS0,VE0; __utmz=251085184.1297646598.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); LUC1=1; qcseg=%7B%22segments%22%3A%5B%7B%22id%22%3A%222495%22%7D%2C%7B%22id%22%3A%222464%22%7D%2C%7B%22id%22%3A%222462%22%7D%2C%7B%22id%22%3A%222459%22%7D%2C%7B%22id%22%3A%222457%22%7D%2C%7B%22id%22%3A%222456%22%7D%2C%7B%22id%22%3A%222453%22%7D%5D%7D; qcsegupdate=1297646595773; __qca=P0-876301846-1297646601771; OAGEO=CO%7C33%7CBogot%C3%A1%7C%7C4.6%7C-74.0833%7C%7C%7C%7C%7C; __utma=251085184.1785666727.1297646598.1297646598.1297646598.1; __utmc=251085184; __utmb=251085184.6.10.1297646598; OAID=ef5275f8036c435efa51b6a3c2ce74fc

Response

HTTP/1.1 500 Internal Server Error
Server: Varnish
Retry-After: 0
X-Selected-Backend: iowa_apache
X-Restarts: 4
Content-Length: 543
Date: Mon, 14 Feb 2011 01:28:08 GMT
Connection: close
X-Served-By: varnish-v12-ASH
X-Cache: MISS
X-Cache-Hits: 0
X-Timer: S1297646887.207281351,VS0,VE1645
Set-Cookie: Geo = {"city":"Dallas","country":"US","continent":"NA"}; path=/
X-Age: 2
X-Varnish-Config: $Revision: 19021 $

<html>
<head>
<title> www.wikia.com/index.php?action=ajax&rs=moduleProxy&moduleName=LatestActivity&actionName=Indexb2c83</title><script>alert(1)</script>95be19a1de3&outputType=html</title>
<script sr
...[SNIP]...

2. Cleartext submission of password previous next

Summary

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

Issue detail

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

http://www.wikia.com/Wikia

The form contains the following password field:

wpPassword

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

Request

GET /Wikia HTTP/1.1
Host: www.wikia.com
Proxy-Connection: keep-alive
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.98 Safari/534.13
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: Geo={"city":"Dallas","country":"US","continent":"NA"}; varnish-stat=/server/ASH/varnish-v11-ASH/HIT/; loadtime=S1297646555.288983345,VS0,VE0

Response

HTTP/1.1 200 OK
Server: Apache
Content-language: en
Last-Modified: Mon, 14 Feb 2011 00:14:48 GMT
Content-Type: text/html; charset=utf-8
X-Cacheable: YES
Date: Mon, 14 Feb 2011 01:26:21 GMT
Connection: keep-alive
X-Served-By: varnish-s3-SJC, varnish-v11-ASH
X-Cache: HIT, HIT
X-Cache-Hits: 19, 31
X-Timer: S1297646781.670613527,VS0,VE0
Vary: Accept-Encoding,Cookie
X-Age: 1698
Set-Cookie: varnish-stat=/server/ASH/varnish-v11-ASH/HIT/; path=/
Set-Cookie: loadtime=S1297646781.670613527,VS0,VE0; path=/
X-Varnish-Config: $Revision: 19021 $
Cache-Control: private, s-maxage=0, max-age=0, must-revalidate
Content-Length: 38557

<!doctype html>
<html lang="en" dir="ltr">
<head>
   <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
   <meta name="viewport" content="width=1200">
   <meta name="description" content="W
...[SNIP]...
</div>
<form action="" method="post" name="userajaxloginform" id="userajaxloginformhide" style="display: none">
           <input type="text" name="wpName" id="wpName1Ajax" tabindex="101" size="20" />
           <input type="password" name="wpPassword" id="wpPassword1Ajax" tabindex="102" size="20" />
           <input type="checkbox" name="wpRemember" id="wpRemember1Ajax" tabindex="104" value="1" />
...[SNIP]...

3. Password field with autocomplete enabled previous next

Summary

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

Issue detail

The page contains a form with the following action URL:

http://www.wikia.com/Wikia

The form contains the following password field with autocomplete enabled:

wpPassword

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

Request

Response

4. Cookie scoped to parent domain previous next
There are 2 instances of this issue:

/__spotlights/lg.php
/__spotlights/spc.php

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.

4.1. http://www.wikia.com/__spotlights/lg.php next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.wikia.com
Path:	/__spotlights/lg.php

Issue detail

The following cookie was issued by the application and is scoped to a parent of the issuing domain:

OAID=ef5275f8036c435efa51b6a3c2ce74fc; expires=Tue, 14-Feb-2012 01:22:47 GMT; path=/; domain=wikia.com

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 /__spotlights/lg.php?bannerid=1449&campaignid=50&zoneid=21&loc=http%3A%2F%2Fwww.wikia.com%2FSpecial%3ALandingPage&referer=http%3A%2F%2Fharrypotter.wikia.com%2Fwiki%2FPoppy_Pomfrey%2527s_wand&cb=5765068cd9 HTTP/1.1
Host: www.wikia.com
Proxy-Connection: keep-alive
Referer: http://www.wikia.com/Wikia
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.98 Safari/534.13
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: Geo={"city":"Dallas","country":"US","continent":"NA"}; varnish-stat=/server/ASH/varnish-v11-ASH/HIT/; loadtime=S1297646556.728570461,VS0,VE0; __utmz=251085184.1297646598.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); LUC1=1; qcseg=%7B%22segments%22%3A%5B%7B%22id%22%3A%222495%22%7D%2C%7B%22id%22%3A%222464%22%7D%2C%7B%22id%22%3A%222462%22%7D%2C%7B%22id%22%3A%222459%22%7D%2C%7B%22id%22%3A%222457%22%7D%2C%7B%22id%22%3A%222456%22%7D%2C%7B%22id%22%3A%222453%22%7D%5D%7D; qcsegupdate=1297646595773; __qca=P0-876301846-1297646601771; OAGEO=CO%7C33%7CBogot%C3%A1%7C%7C4.6%7C-74.0833%7C%7C%7C%7C%7C; OAID=ef5275f8036c435efa51b6a3c2ce74fc; __utma=251085184.1785666727.1297646598.1297646598.1297646598.1; __utmc=251085184; __utmb=251085184.6.10.1297646598

Response

HTTP/1.1 200 OK
Server: Apache
Pragma: no-cache
P3P: CP="CUR ADM OUR NOR STA NID"
Set-Cookie: OAID=ef5275f8036c435efa51b6a3c2ce74fc; expires=Tue, 14-Feb-2012 01:22:47 GMT; path=/; domain=wikia.com
Content-Type: image/gif
X-Cacheable: NO:Cache-Control=private
Content-Length: 43
Date: Mon, 14 Feb 2011 01:22:47 GMT
Connection: keep-alive
X-Served-By: varnish-v11-ASH
X-Cache: MISS
X-Cache-Hits: 0
X-Timer: S1297646567.179046154,VS0,VE74
X-Age: 0
X-Varnish-Config: $Revision: 19021 $
Cache-Control: private, s-maxage=0, max-age=0, must-revalidate

GIF89a.............!.......,...........D..;

4.2. http://www.wikia.com/__spotlights/spc.php previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.wikia.com
Path:	/__spotlights/spc.php

Issue detail

The following cookies were issued by the application and is scoped to a parent of the issuing domain:

OAGEO=US%7CTX%7CDallas%7C75207%7C32.7825%7C-96.8207%7C623%7C214%7C%7C%7C; path=/; domain=wikia.com
OAID=2d492e32b2be365fd4cf9e8ee258b8f6; expires=Tue, 14-Feb-2012 01:26:26 GMT; path=/; domain=wikia.com

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 /__spotlights/spc.php?zones=14|15|16|17|18|19|20|21|22&source=&r=36660656&loc=http%3A//www.wikia.com/Wikia&referer=&target=_top&cb=83643676&hub=wikia&skin_name=oasis&cont_lang=en&user_lang=en&dbname=wikiaglobal&tags=xbox_360%2Cwikia%2Cfrontline%2Cwidget%2Cwidget_frontline&block=1&charset=UTF-8 HTTP/1.1
Host: www.wikia.com
Proxy-Connection: keep-alive
Referer: http://www.wikia.com/Wikia
X-Requested-With: XMLHttpRequest
Accept: text/javascript, application/javascript, */*; q=0.01
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.98 Safari/534.13
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: Geo={"city":"Dallas","country":"US","continent":"NA"}; varnish-stat=/server/ASH/varnish-v11-ASH/HIT/; loadtime=S1297646556.728570461,VS0,VE0; __utmz=251085184.1297646598.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=251085184.1785666727.1297646598.1297646598.1297646598.1; __utmc=251085184; __utmb=251085184.4.10.1297646598; LUC1=1

Response

HTTP/1.1 200 OK
Server: Apache
Pragma: no-cache
P3P: CP="CUR ADM OUR NOR STA NID"
Set-Cookie: OAGEO=US%7CTX%7CDallas%7C75207%7C32.7825%7C-96.8207%7C623%7C214%7C%7C%7C; path=/; domain=wikia.com
Set-Cookie: OAID=2d492e32b2be365fd4cf9e8ee258b8f6; expires=Tue, 14-Feb-2012 01:26:26 GMT; path=/; domain=wikia.com
Content-Size: 7613
Content-Type: application/x-javascript; charset=UTF-8
X-Cacheable: YES - FORCED
Date: Mon, 14 Feb 2011 01:26:26 GMT
Connection: keep-alive
X-Served-By: varnish-v11-ASH
X-Cache: MISS
X-Cache-Hits: 0
X-Timer: S1297646786.671192646,VS0,VE280
Vary: Accept-Encoding
X-Age: 0
X-Varnish-Config: $Revision: 19021 $
Cache-Control: private, s-maxage=0, max-age=0, must-revalidate
Content-Length: 7613

var OA_output = new Array();
OA_output['14'] = '';
OA_output['14'] += "<"+"a href=\'/__spotlights/ck.php?oaparams=2__bannerid=1708__zoneid=14__cb=20cffdb904__oadest=http%3A%2F%2Flyrics.wikia.com%2FUs
...[SNIP]...

5. Cross-domain Referer leakage previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.wikia.com
Path:	/index.php

Issue detail

The page was loaded from a URL containing a query string:

http://www.wikia.com/index.php?action=ajax&rs=moduleProxy&moduleName=LatestActivity&actionName=Index&outputType=html

The response contains the following link to another domain:

http://images1.wikia.nocookie.net/__cb33398/common/skins/common/blank.gif

Issue background

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

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

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

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

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

Issue remediation

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

Request

GET /index.php?action=ajax&rs=moduleProxy&moduleName=LatestActivity&actionName=Index&outputType=html HTTP/1.1
Host: www.wikia.com
Proxy-Connection: keep-alive
Referer: http://www.wikia.com/Wikia
X-Requested-With: XMLHttpRequest
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.98 Safari/534.13
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: Geo={"city":"Dallas","country":"US","continent":"NA"}; varnish-stat=/server/ASH/varnish-v11-ASH/HIT/; loadtime=S1297646556.728570461,VS0,VE0; __utmz=251085184.1297646598.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); LUC1=1; qcseg=%7B%22segments%22%3A%5B%7B%22id%22%3A%222495%22%7D%2C%7B%22id%22%3A%222464%22%7D%2C%7B%22id%22%3A%222462%22%7D%2C%7B%22id%22%3A%222459%22%7D%2C%7B%22id%22%3A%222457%22%7D%2C%7B%22id%22%3A%222456%22%7D%2C%7B%22id%22%3A%222453%22%7D%5D%7D; qcsegupdate=1297646595773; __qca=P0-876301846-1297646601771; OAGEO=CO%7C33%7CBogot%C3%A1%7C%7C4.6%7C-74.0833%7C%7C%7C%7C%7C; __utma=251085184.1785666727.1297646598.1297646598.1297646598.1; __utmc=251085184; __utmb=251085184.6.10.1297646598; OAID=ef5275f8036c435efa51b6a3c2ce74fc

Response

HTTP/1.1 200 OK
Server: Apache
Status: 200 OK
Last-Modified: Mon, 14 Feb 2011 01:14:08 GMT
Pragma: no-cache
Content-Type: text/html; charset=utf-8
X-Cacheable: YES - FORCED
Date: Mon, 14 Feb 2011 01:26:35 GMT
Connection: keep-alive
X-Served-By: varnish-s3-SJC, varnish-v11-ASH
X-Cache: HIT, HIT
X-Cache-Hits: 11, 57
X-Timer: S1297646795.460254908,VS0,VE0
Vary: Accept-Encoding
X-Age: 478
Set-Cookie: varnish-stat=/server/ASH/varnish-v11-ASH/HIT/; path=/
Set-Cookie: loadtime=S1297646795.460254908,VS0,VE0; path=/
X-Varnish-Config: $Revision: 19021 $
Cache-Control: private, s-maxage=0, max-age=0, must-revalidate
Content-Length: 1391

<section class="WikiaActivityModule module ">
   <h1 class="activity-heading">Recent Wiki Activity</h1>
   <ul>
       <li>
           <img src="http://images1.wikia.nocookie.net/__cb33398/common/skins/common/blank.gif" class="sprite edit" height="20" width="20">
           <em>
...[SNIP]...
<li>
           <img src="http://images1.wikia.nocookie.net/__cb33398/common/skins/common/blank.gif" class="sprite edit" height="20" width="20">
           <em>
...[SNIP]...
<li>
           <img src="http://images1.wikia.nocookie.net/__cb33398/common/skins/common/blank.gif" class="sprite edit" height="20" width="20">
           <em>
...[SNIP]...
<li>
           <img src="http://images1.wikia.nocookie.net/__cb33398/common/skins/common/blank.gif" class="sprite edit" height="20" width="20">
           <em>
...[SNIP]...

6. Cross-domain script include previous next

Summary

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

Issue detail

The response dynamically includes the following scripts from other domains:

http://edge.quantserve.com/quant.js
http://www.google-analytics.com/ga.js

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

Response

HTTP/1.1 200 OK
Server: Apache
Content-language: en
Last-Modified: Mon, 14 Feb 2011 00:14:48 GMT
Content-Type: text/html; charset=utf-8
X-Cacheable: YES
Date: Mon, 14 Feb 2011 01:26:21 GMT
Connection: keep-alive
X-Served-By: varnish-s3-SJC, varnish-v11-ASH
X-Cache: HIT, HIT
X-Cache-Hits: 19, 31
X-Timer: S1297646781.670613527,VS0,VE0
Vary: Accept-Encoding,Cookie
X-Age: 1698
Set-Cookie: varnish-stat=/server/ASH/varnish-v11-ASH/HIT/; path=/
Set-Cookie: loadtime=S1297646781.670613527,VS0,VE0; path=/
X-Varnish-Config: $Revision: 19021 $
Cache-Control: private, s-maxage=0, max-age=0, must-revalidate
Content-Length: 38557

<!doctype html>
<html lang="en" dir="ltr">
<head>
   <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
   <meta name="viewport" content="width=1200">
   <meta name="description" content="W
...[SNIP]...

<script type="text/javascript" src="http://www.google-analytics.com/ga.js"></script>
...[SNIP]...

<script type="text/javascript" src="http://edge.quantserve.com/quant.js"></script>
...[SNIP]...

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

/
/Wikia
/__spotlights/lg.php
/__spotlights/spc.php
/index.php

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.

7.1. http://www.wikia.com/ previous next

Summary

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

Issue detail

The following cookies were issued by the application and do not have the HttpOnly flag set:

Geo = {"city":"Dallas","country":"US","continent":"NA"}; path=/
varnish-stat=/server/ASH/varnish-v11-ASH/HIT/; path=/
loadtime=S1297646555.288983345,VS0,VE0; path=/

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 / HTTP/1.1
Host: www.wikia.com
Proxy-Connection: keep-alive
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.98 Safari/534.13
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 301 Moved Permanently
Server: Apache
Last-Modified: Mon, 14 Feb 2011 00:49:13 GMT
Location: http://www.wikia.com/Wikia
Content-Type: text/html; charset=utf-8
X-Cacheable: YES
Date: Mon, 14 Feb 2011 01:22:35 GMT
Connection: keep-alive
X-Served-By: varnish-s1-SJC, varnish-v11-ASH
X-Cache: HIT, HIT
X-Cache-Hits: 8, 12
X-Timer: S1297646555.288983345,VS0,VE0
Vary: Accept-Encoding,Cookie
Set-Cookie: Geo = {"city":"Dallas","country":"US","continent":"NA"}; path=/
X-Age: 1161
Set-Cookie: varnish-stat=/server/ASH/varnish-v11-ASH/HIT/; path=/
Set-Cookie: loadtime=S1297646555.288983345,VS0,VE0; path=/
X-Varnish-Config: $Revision: 19021 $
Cache-Control: private, s-maxage=0, max-age=0, must-revalidate
Content-Length: 0

7.2. http://www.wikia.com/Wikia previous next

Summary

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

Issue detail

The following cookies were issued by the application and do not have the HttpOnly flag set:

varnish-stat=/server/ASH/varnish-v11-ASH/HIT/; path=/
loadtime=S1297646781.670613527,VS0,VE0; path=/

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

Response

7.3. http://www.wikia.com/__spotlights/lg.php previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.wikia.com
Path:	/__spotlights/lg.php

Issue detail

The following cookie was issued by the application and does not have the HttpOnly flag set:

OAID=ef5275f8036c435efa51b6a3c2ce74fc; expires=Tue, 14-Feb-2012 01:22:47 GMT; path=/; domain=wikia.com

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

Response

7.4. http://www.wikia.com/__spotlights/spc.php previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.wikia.com
Path:	/__spotlights/spc.php

Issue detail

The following cookies were issued by the application and do not have the HttpOnly flag set:

OAGEO=US%7CTX%7CDallas%7C75207%7C32.7825%7C-96.8207%7C623%7C214%7C%7C%7C; path=/; domain=wikia.com
OAID=2d492e32b2be365fd4cf9e8ee258b8f6; expires=Tue, 14-Feb-2012 01:26:26 GMT; path=/; domain=wikia.com

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

Response

7.5. http://www.wikia.com/index.php previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.wikia.com
Path:	/index.php

Issue detail

The following cookies were issued by the application and do not have the HttpOnly flag set:

varnish-stat=/server/ASH/varnish-v11-ASH/HIT/; path=/
loadtime=S1297646795.460254908,VS0,VE0; path=/

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

Response

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

/index.php
/opensearch_desc.php

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://www.wikia.com/index.php previous next

Summary

Severity:	Information
Confidence:	Firm
Host:	http://www.wikia.com
Path:	/index.php

Issue detail

The response contains the following Content-type statement:

Content-Type: text/html; charset=utf-8

The response states that it contains HTML. However, it actually appears to contain XML.

Request

Response

8.2. http://www.wikia.com/opensearch_desc.php previous

Summary

Severity:	Information
Confidence:	Firm
Host:	http://www.wikia.com
Path:	/opensearch_desc.php

Issue detail

The response contains the following Content-type statement:

Content-Type: application/opensearchdescription+xml

The response states that it contains script. However, it actually appears to contain XML.

Request

GET /opensearch_desc.php HTTP/1.1
Host: www.wikia.com
Proxy-Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.98 Safari/534.13
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: Geo={"city":"Dallas","country":"US","continent":"NA"}; __utmz=251085184.1297646598.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); LUC1=1; qcseg=%7B%22segments%22%3A%5B%7B%22id%22%3A%222495%22%7D%2C%7B%22id%22%3A%222464%22%7D%2C%7B%22id%22%3A%222462%22%7D%2C%7B%22id%22%3A%222459%22%7D%2C%7B%22id%22%3A%222457%22%7D%2C%7B%22id%22%3A%222456%22%7D%2C%7B%22id%22%3A%222453%22%7D%5D%7D; qcsegupdate=1297646595773; __qca=P0-876301846-1297646601771; OAGEO=CO%7C33%7CBogot%C3%A1%7C%7C4.6%7C-74.0833%7C%7C%7C%7C%7C; __utma=251085184.1785666727.1297646598.1297646598.1297646598.1; __utmc=251085184; __utmb=251085184.6.10.1297646598; OAID=ef5275f8036c435efa51b6a3c2ce74fc; varnish-stat=/server/ASH/varnish-v11-ASH/HIT/; loadtime=S1297646569.935566902,VS0,VE0

Response

HTTP/1.1 200 OK
Server: Apache
X-Pass-Expires: Sun, 13 Feb 2011 07:21:52 GMT
X-Pass-Cache-Control: max-age=86400
Content-Type: application/opensearchdescription+xml
X-Cacheable: YES
Date: Mon, 14 Feb 2011 01:26:37 GMT
Connection: keep-alive
X-Served-By: varnish-s3-SJC, varnish-v11-ASH
X-Cache: HIT, HIT
X-Cache-Hits: 547, 593
X-Timer: S1297646797.319349527,VS0,VE0
Vary: Accept-Encoding
X-Age: 69189
X-Varnish-Config: $Revision: 19021 $
Cache-Control: max-age=86400
Content-Length: 706

<?xml version="1.0"?><OpenSearchDescription xmlns="http://a9.com/-/spec/opensearch/1.1/" xmlns:moz="http://www.mozilla.org/2006/browser/search/"><ShortName>Wikia (en)</ShortName><Description>Wikia (en
...[SNIP]...

Report generated by CloudScan Vulnerability Crawler at Sun Feb 13 19:50:10 CST 2011.