XSS, Cross Site Scripting, www.accuweather.com, CWE-79

CAPEC-86, XSS in www.accuweather.com | Vulnerability Crawler Report

Report generated by CloudScan Vulnerability Crawler at Fri Feb 04 13:07:25 CST 2011.

DORK CWE-79 XSS Report

Loading

1. Flash cross-domain policy

2. Cross-site scripting (reflected)

2.1. http://www.accuweather.com/index-radar.asp [Referer HTTP header]

2.2. http://www.accuweather.com/maps-satellite.asp [Referer HTTP header]

3. Cross-domain Referer leakage

4. Cross-domain script include

4.1. http://www.accuweather.com/us/NY/HONEOYE%20FALLS/14472/city-weather-forecast.asp

4.2. http://www.accuweather.com/us/satellite/ei/us_/satellite.asp

5. Cookie without HttpOnly flag set

5.1. http://www.accuweather.com/index-radar.asp

5.2. http://www.accuweather.com/maps-satellite.asp

5.3. http://www.accuweather.com/us/NY/HONEOYE%20FALLS/14472/city-weather-forecast.asp

5.4. http://www.accuweather.com/us/satellite/ei/us_/satellite.asp

6. Robots.txt file


1. Flash cross-domain policy  next

Summary

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

Issue detail

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

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.

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

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

Issue background

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

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

Issue remediation

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

Request

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

Response

HTTP/1.0 200 OK
Content-Length: 1403
Content-Type: text/xml
Last-Modified: Tue, 09 Feb 2010 20:00:39 GMT
Accept-Ranges: bytes
ETag: "c28f298dc2a9ca1:a74"
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Date: Thu, 03 Feb 2011 16:34:40 GMT
Connection: close

<?xml version="1.0"?>
<!DOCTYPE cross-domain-policy SYSTEM "http://www.macromedia.com/xml/dtds/cross-domain-policy.dtd">
<cross-domain-policy>
<allow-access-from domain="*" />
<allow-access-from domain="*.accuweather.com" />
<allow-access-from domain="*.accuweatherchannel.com" />
<allow-access-from domain="*.discovery.com" />
<allow-access-from domain="*.oddcast.com" />
<allow-access-from domain="*.ucview.com" />
<allow-access-from domain="*.2mdn.net" secure="true" />
...[SNIP]...
<allow-access-from domain="*.doubleclick.net" secure="true" />
...[SNIP]...
<allow-access-from domain="*.doubleclick.com" secure="true" />
...[SNIP]...
<allow-access-from domain="*.adcdn.com" secure="true" />
...[SNIP]...
<allow-access-from domain="*.dartmotif.com" secure="true" />
...[SNIP]...
<allow-access-from domain="*.aolcdn.com" secure="true" />
...[SNIP]...
<allow-access-from domain="maps.google.com" />
<allow-access-from domain="maps.yahooapis.com"/>
<allow-access-from domain="spm161.brinkster.net" />
<allow-access-from domain="www.dotglu.com" />
<allow-access-from domain="www.johnfrieda.com" />
<allow-access-from domain="www.travelboards.com" />
<allow-access-from domain="www.topix.com"/>
<allow-access-from domain="66.42.146.50" />
<allow-access-from domain="66.42.146.66" />
<allow-access-from domain="68.167.121.226" />
...[SNIP]...
2. Cross-site scripting (reflected)  previous  next
There are 2 instances of this issue:

Issue background

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

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

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

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

Remediation background

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

2.1. http://www.accuweather.com/index-radar.asp [Referer HTTP header]  next

Summary

Severity:   Low
Confidence:   Certain
Host:   http://www.accuweather.com
Path:   /index-radar.asp

Issue detail

The value of the Referer HTTP header is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 1f5bc</script><script>alert(1)</script>da526c0c2c2 was submitted in the Referer HTTP header. 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.

Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.

Because the user data that is copied into the response is submitted within a request header, the application's behaviour is not trivial to exploit in an attack against another user. In the past, methods have existed of using client-side technologies such as Flash to cause another user to make a request containing an arbitrary HTTP header. If you can use such a technique, you can probably leverage it to exploit the XSS flaw. This limitation partially mitigates the impact of the vulnerability.

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 /index-radar.asp HTTP/1.1
Host: www.accuweather.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Referer: http://www.google.com/search?hl=en&q=1f5bc</script><script>alert(1)</script>da526c0c2c2

Response (redirected)

HTTP/1.1 200 OK
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
p3p: CP="NOI DSP COR ADMa DEVa TAIa PSAa PSDa IVAa IVDa CONi HISa OUR IND CNT"
Content-Length: 64616
Content-Type: text/html
Cache-Control: public
Date: Thu, 03 Feb 2011 16:35:04 GMT
Connection: close
Set-Cookie: acm=ct1=Los+Angeles&uf0=nyc&lid=1&uf3=ord&zp2=33128&st0=NY&pty=accu&st2=FL&pt=accuweather&ct2=Miami&uf1=59l&zp0=10017&pti=&ins=aches%2Dpains&ct3=Chicago&uf2=mia&zp1=90012&inm=health&zp3=60605&st1=CA&ver=0&st3=Il&ct0=New+York&ptu=&mt=0; expires=Sat, 05-Mar-2011 00:00:00 GMT; path=/
Set-Cookie: aco=dbg=0; path=/


<!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">
<hea
...[SNIP]...
<script>var apgUserInfoObj={country:'US',city:'New York',state:'NY',metro:'',zip:'10017',partner:'accuweather',referer:'http://www.google.com/search?hl=en&q=1f5bc</script><script>alert(1)</script>da526c0c2c2'};var apgWxInfoObj={ut:'0',cu:{wx:'',hi:'',wd:'',hd:'',uv:''},fc:[{wx:'',hi:'',lo:''},{wx:'',hi:'',lo:''},{wx:'',hi:'',lo:''}],ix:{arthritis:'',asthma:'',bbq:'',cold:'',dogwalk:'',flu:'',indoor:'',law
...[SNIP]...
2.2. http://www.accuweather.com/maps-satellite.asp [Referer HTTP header]  previous  next

Summary

Severity:   Low
Confidence:   Certain
Host:   http://www.accuweather.com
Path:   /maps-satellite.asp

Issue detail

The value of the Referer HTTP header is copied into a JavaScript string which is encapsulated in single quotation marks. The payload ea202</script><script>alert(1)</script>53080030620 was submitted in the Referer HTTP header. 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.

Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.

Because the user data that is copied into the response is submitted within a request header, the application's behaviour is not trivial to exploit in an attack against another user. In the past, methods have existed of using client-side technologies such as Flash to cause another user to make a request containing an arbitrary HTTP header. If you can use such a technique, you can probably leverage it to exploit the XSS flaw. This limitation partially mitigates the impact of the vulnerability.

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 /maps-satellite.asp HTTP/1.1
Host: www.accuweather.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Referer: http://www.google.com/search?hl=en&q=ea202</script><script>alert(1)</script>53080030620

Response (redirected)

HTTP/1.1 200 OK
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
p3p: CP="NOI DSP COR ADMa DEVa TAIa PSAa PSDa IVAa IVDa CONi HISa OUR IND CNT"
Content-Length: 64040
Content-Type: text/html
Cache-Control: public
Date: Thu, 03 Feb 2011 16:35:14 GMT
Connection: close
Set-Cookie: acm=ct1=Los+Angeles&uf0=nyc&lid=1&uf3=ord&zp2=33128&st0=NY&pty=accu&st2=FL&pt=accuweather&ct2=Miami&uf1=59l&zp0=10017&pti=&ins=aches%2Dpains&ct3=Chicago&uf2=mia&zp1=90012&inm=health&zp3=60605&st1=CA&ver=0&st3=Il&ct0=New+York&ptu=&mt=0; expires=Sat, 05-Mar-2011 00:00:00 GMT; path=/
Set-Cookie: aco=dbg=0; path=/

<!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">
<head>
...[SNIP]...
<script>var apgUserInfoObj={country:'US',city:'New York',state:'NY',metro:'',zip:'10017',partner:'accuweather',referer:'http://www.google.com/search?hl=en&q=ea202</script><script>alert(1)</script>53080030620'};var apgWxInfoObj={ut:'0',cu:{wx:'',hi:'',wd:'',hd:'',uv:''},fc:[{wx:'',hi:'',lo:''},{wx:'',hi:'',lo:''},{wx:'',hi:'',lo:''}],ix:{arthritis:'',asthma:'',bbq:'',cold:'',dogwalk:'',flu:'',indoor:'',law
...[SNIP]...
3. Cross-domain Referer leakage  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.accuweather.com
Path:   /us/NY/HONEOYE%20FALLS/14472/city-weather-forecast.asp

Issue detail

The page was loaded from a URL containing a query string:The response contains the following links to other domains:

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 /us/NY/HONEOYE%20FALLS/14472/city-weather-forecast.asp?partner=accuweather&traveler=0 HTTP/1.1
Host: www.accuweather.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
p3p: CP="NOI DSP COR ADMa DEVa TAIa PSAa PSDa IVAa IVDa CONi HISa OUR IND CNT"
Content-Length: 80324
Content-Type: text/html
Cache-Control: public
Date: Thu, 03 Feb 2011 16:34:42 GMT
Connection: close
Set-Cookie: aco=hi2=36&lo1=16&dn0=day&lo2=25&wx0=03&wc0=04&lo0=8&isi=6&ifs=2&wx1=02&hi0=27&pl0=1&trv=1&wx2=22&hi1=28&dbg=0; path=/
Set-Cookie: acm=nm0=ROC&vi0=ROC&ob0=ROC&uf0=NY4475&ln0=%2D77%2E59&dy0=1&gm0=5&ct1=New+York&st4=Il&lid=1&ns0=NY%5F&lt0=42%2E97&st0=NY&zp2=90012&uf3=mia&ct4=Chicago&pty=accu&sc0=NYC055&st2=CA&zp4=60605&pt=accuweather&fz0=&wn0=%40NY&ar0=14472&zp0=14472&uf1=nyc&ct2=Los+Angeles&pti=&ins=aches%2Dpains&nx0=KBUF&cl0=ROC&zp1=10017&uf2=59l&ct3=Miami&inm=health&st1=NY&zp3=33128&uf4=ord&ver=0&nr0=NE&sz0=NYZ003&ct0=Honeoye+Falls&st3=FL&ptu=&mt=0; expires=Sat, 05-Mar-2011 00:00:00 GMT; path=/


<!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">
<hea
...[SNIP]...
<noscript><a href="http://www.omniture.com" title="Web Analytics"><img
src="http://accuweather.122.2o7.net/b/ss/accuweatherdev/1/H.16--NS/0"
height="1" width="1" border="0" alt="" /></a>
...[SNIP]...
</h4>
<a href="http://www.adci.com/" class="rt" target="_blank"><img src="http://vortex.accuweather.com/adc2010/images/misc/adci-world-map_83x35.png" style="margin-left:5px;" width="83" height="35" alt="ADCi World Map" />
...[SNIP]...
<a href="http://www.accuweather.com/video/655578741001/winter-visits-texas.asp" class="wrap">
<img src="http://brightcove.vo.llnwd.net/d13/unsecured/media/1612802193/1612802193_775344727001_20110203070300-wntrexprt-thumb.jpg?pubId=1612802193" width="120" height="90" alt="Winter Visits Texas" /></a>
...[SNIP]...
<a href="http://www.accuweather.com/video/44297808001/super-bowl-xlv-to-play-under-roof.asp" class="wrap">
<img src="http://brightcove.vo.llnwd.net/d13/unsecured/media/1612802193/1612802193_775319820001_20110203050000-sportswx-thumb.jpg?pubId=1612802193" width="120" height="90" alt="Super Bowl XLV to Play Under Roof" /></a>
...[SNIP]...
<a href="http://www.accuweather.com/video/1670024770/breaking-weather-southern-snow.asp" class="wrap">
<img src="http://brightcove.vo.llnwd.net/d13/unsecured/media/1612802193/1612802193_775576142001_20110203105100-breaking-thumb.jpg?pubId=1612802193" width="120" height="90" alt="Breaking Weather: Southern Snow" /></a>
...[SNIP]...
<a href="http://www.accuweather.com/video/90811342001/phil-aside-more-cold-and-snow-on-the-way.asp" class="wrap">
<img src="http://brightcove.vo.llnwd.net/d13/unsecured/media/1612802193/1612802193_775351099001_20110203064900-vblundbj-thumb.jpg?pubId=1612802193" width="120" height="90" alt="Phil Aside, More Cold and Snow on the Way" /></a>
...[SNIP]...
<li class="last"> <a href="http://www.weatherdata.com/products/skyguard.php" class="wrap" target="_blank"><img src="http://vortex.accuweather.com/adc2010/images/features/Tornado_120x180.jpg" width="120" height="180" alt="SkyGuard" />
...[SNIP]...
<h4><a href="http://www.weatherdata.com/products/skyguard.php" target="_blank"><em>
...[SNIP]...
<h4>
           <a href="http://www.wishgreaterpa.org" target="_blank">

            <br /><a href="http://www.wishgreaterpa.org" target="_blank"><em>
...[SNIP]...
</p>

<a href="http://www.wishgreaterpa.org" target="_blank" class="logo"><img width="120" height="60" src="http://vortex.accuweather.com/adc2010/ads/images/accuweather_makeAwish.png" alt="" />
...[SNIP]...
<li><a href="http://www.accumall.com">Shop</a>
...[SNIP]...
<p> This page may contain Mapping and <a href="http://www.mobiumgps.com/">GPS Navigation Systems</a>
...[SNIP]...
</script>
<script type="text/javascript" src="http://edge.quantserve.com/quant.js"></script>
<noscript>
<a href="http://www.quantcast.com/p-4b4gl_1fWISuU" target="_blank"><img src="http://pixel.quantserve.com/pixel/p-4b4gl_1fWISuU.gif" style="display: none" border="0" height="1" width="1" alt="Quantcast"/></a>
...[SNIP]...
<noscript>
<img src="http://b.scorecardresearch.com/b?c1=&c2=6005068&c3=6005068&c4=http://www.accuweather.com/city-weather-forecast.asp&c5=&c6=&c7=/city-weather-forecast.asp&c15=C67BD3C1&cv=1.3&cj=1" style="display:none" width="0" height="0" alt="" />
</noscript>
...[SNIP]...
<noscript>
<img style="display:none;" src="//secure-us.imrworldwide.com/cgi-bin/m?ci=us-accuweather&amp;cg=0&amp;cc=1&amp;ts=noscript" width="1" height="1" alt="" />
</noscript>


<img style="display:none;" height="1" width="1" src="http://tags.bluekai.com/site/2470" alt="" />

</body>
...[SNIP]...
4. Cross-domain script include  previous  next
There are 2 instances of this issue:

Issue background

When an application includes a script from an external domain, this script is executed by the browser within the security context of the invoking application. The script can therefore do anything that the application's own scripts can do, such as accessing application data and performing actions within the context of the current user.

If you include a script from an external domain, then you are trusting that domain with the data and functionality of your application, and you are trusting the domain's own security to prevent an attacker from modifying the script to perform malicious actions within your application.

Issue remediation

Scripts should not be included from untrusted domains. If you have a requirement which a third-party script appears to fulfil, then you should ideally copy the contents of that script onto your own domain and include it from there. If that is not possible (e.g. for licensing reasons) then you should consider reimplementing the script's functionality within your own code.

4.1. http://www.accuweather.com/us/NY/HONEOYE%20FALLS/14472/city-weather-forecast.asp  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.accuweather.com
Path:   /us/NY/HONEOYE%20FALLS/14472/city-weather-forecast.asp

Issue detail

The response dynamically includes the following script from another domain:

Request

GET /us/NY/HONEOYE%20FALLS/14472/city-weather-forecast.asp HTTP/1.1
Host: www.accuweather.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
p3p: CP="NOI DSP COR ADMa DEVa TAIa PSAa PSDa IVAa IVDa CONi HISa OUR IND CNT"
Content-Length: 79770
Content-Type: text/html
Cache-Control: public
Date: Thu, 03 Feb 2011 16:34:38 GMT
Connection: close
Set-Cookie: acm=nm0=ROC&vi0=ROC&ob0=ROC&uf0=NY4475&ln0=%2D77%2E59&dy0=1&gm0=5&ct1=New+York&st4=Il&lid=1&ns0=NY%5F&lt0=42%2E97&st0=NY&zp2=90012&uf3=mia&ct4=Chicago&pty=accu&sc0=NYC055&st2=CA&zp4=60605&pt=accuweather&fz0=&wn0=%40NY&ar0=14472&zp0=14472&uf1=nyc&ct2=Los+Angeles&pti=&ins=aches%2Dpains&nx0=KBUF&cl0=ROC&zp1=10017&uf2=59l&ct3=Miami&inm=health&st1=NY&zp3=33128&uf4=ord&ver=0&nr0=NE&sz0=NYZ003&ct0=Honeoye+Falls&st3=FL&ptu=&mt=0; expires=Sat, 05-Mar-2011 00:00:00 GMT; path=/
Set-Cookie: aco=hi2=36&lo2=25&wx0=03&wc0=04&lo0=8&isi=6&lo1=16&dn0=day&icd=2&wx1=02&hi0=27&pl0=1&trv=1&wx2=22&hi1=28&dbg=0; path=/


<!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">
<hea
...[SNIP]...
</script>
<script type="text/javascript" src="http://edge.quantserve.com/quant.js"></script>
...[SNIP]...
4.2. http://www.accuweather.com/us/satellite/ei/us_/satellite.asp  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.accuweather.com
Path:   /us/satellite/ei/us_/satellite.asp

Issue detail

The response dynamically includes the following script from another domain:

Request

GET /us/satellite/ei/us_/satellite.asp HTTP/1.1
Host: www.accuweather.com
Proxy-Connection: keep-alive
Referer: http://burp/show/65
Cache-Control: max-age=0
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.10 (KHTML, like Gecko) Chrome/8.0.552.237 Safari/534.10
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: __utmz=256067995.1296754760.1.1.utmcsr=burp|utmccn=(referral)|utmcmd=referral|utmcct=/show/64; s_cc=true; s_sq=%5B%5BB%5D%5D; s_vi=[CS]v1|26A57416051D2589-4000012C8000F930[CE]; __qca=P0-1763970855-1296754771965; __utma=256067995.1249143252.1296754760.1296754760.1296754760.1; __utmc=256067995; __utmb=256067995.7.6.1296754772036; acm=ct1=Los+Angeles&uf0=nyc&lid=1&uf3=ord&zp2=33128&st0=NY&pty=accu&st2=FL&pt=accuweather&ct2=Miami&uf1=59l&zp0=10017&pti=&ins=aches%2Dpains&ct3=Chicago&uf2=mia&zp1=90012&inm=health&zp3=60605&st1=CA&ver=0&st3=Il&ct0=New+York&ptu=&mt=0; aco=dbg=0

Response

HTTP/1.1 200 OK
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
p3p: CP="NOI DSP COR ADMa DEVa TAIa PSAa PSDa IVAa IVDa CONi HISa OUR IND CNT"
Content-Type: text/html
Cache-Control: public
Vary: Accept-Encoding
Date: Thu, 03 Feb 2011 17:39:07 GMT
Connection: close
Set-Cookie: aco=dbg=0; path=/
Set-Cookie: acm=ptu=&mt=0&ct0=New+York&st3=Il&ver=0&st1=CA&zp3=60605&inm=health&zp1=90012&uf2=mia&ct3=Chicago&pti=&ins=aches%2Dpains&zp0=10017&uf1=59l&ct2=Miami&pt=accuweather&st2=FL&pty=accu&st0=NY&zp2=33128&uf3=ord&lid=1&uf0=nyc&ct1=Los+Angeles; expires=Sat, 05-Mar-2011 00:00:00 GMT; path=/
Content-Length: 64023

<!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">
<head>
...[SNIP]...
</script>
<script type="text/javascript" src="http://edge.quantserve.com/quant.js"></script>
...[SNIP]...
5. Cookie without HttpOnly flag set  previous  next
There are 4 instances of this issue:

Issue background

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

Issue remediation

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

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

5.1. http://www.accuweather.com/index-radar.asp  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.accuweather.com
Path:   /index-radar.asp

Issue detail

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

Request

GET /index-radar.asp HTTP/1.1
Host: www.accuweather.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 301 Moved Permanently
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
p3p: CP="NOI DSP COR ADMa DEVa TAIa PSAa PSDa IVAa IVDa CONi HISa OUR IND CNT"
Location: http://www.accuweather.com/us/radar/sir/us_/radar.asp
Content-Length: 0
Content-Type: text/html
Cache-Control: public
Vary: Accept-Encoding
Date: Thu, 03 Feb 2011 16:34:42 GMT
Connection: close
Set-Cookie: acm=ct1=Los+Angeles&uf0=nyc&lid=1&uf3=ord&zp2=33128&st0=NY&pty=accu&st2=FL&pt=accuweather&ct2=Miami&uf1=59l&zp0=10017&pti=&ins=aches%2Dpains&ct3=Chicago&uf2=mia&zp1=90012&inm=health&zp3=60605&st1=CA&ver=0&st3=Il&ct0=New+York&ptu=&mt=0; expires=Sat, 05-Mar-2011 00:00:00 GMT; path=/
Set-Cookie: aco=dbg=0; path=/

5.2. http://www.accuweather.com/maps-satellite.asp  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.accuweather.com
Path:   /maps-satellite.asp

Issue detail

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

Request

GET /maps-satellite.asp HTTP/1.1
Host: www.accuweather.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 301 Moved Permanently
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
p3p: CP="NOI DSP COR ADMa DEVa TAIa PSAa PSDa IVAa IVDa CONi HISa OUR IND CNT"
Location: http://www.accuweather.com/us/satellite/ei/us_/satellite.asp
Content-Length: 0
Content-Type: text/html
Cache-Control: public
Vary: Accept-Encoding
Date: Thu, 03 Feb 2011 16:34:42 GMT
Connection: close
Set-Cookie: acm=ct1=Los+Angeles&uf0=nyc&lid=1&uf3=ord&zp2=33128&st0=NY&pty=accu&st2=FL&pt=accuweather&ct2=Miami&uf1=59l&zp0=10017&pti=&ins=aches%2Dpains&ct3=Chicago&uf2=mia&zp1=90012&inm=health&zp3=60605&st1=CA&ver=0&st3=Il&ct0=New+York&ptu=&mt=0; expires=Sat, 05-Mar-2011 00:00:00 GMT; path=/
Set-Cookie: aco=dbg=0; path=/

5.3. http://www.accuweather.com/us/NY/HONEOYE%20FALLS/14472/city-weather-forecast.asp  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.accuweather.com
Path:   /us/NY/HONEOYE%20FALLS/14472/city-weather-forecast.asp

Issue detail

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

Request

GET /us/NY/HONEOYE%20FALLS/14472/city-weather-forecast.asp HTTP/1.1
Host: www.accuweather.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
p3p: CP="NOI DSP COR ADMa DEVa TAIa PSAa PSDa IVAa IVDa CONi HISa OUR IND CNT"
Content-Length: 79770
Content-Type: text/html
Cache-Control: public
Date: Thu, 03 Feb 2011 16:34:38 GMT
Connection: close
Set-Cookie: acm=nm0=ROC&vi0=ROC&ob0=ROC&uf0=NY4475&ln0=%2D77%2E59&dy0=1&gm0=5&ct1=New+York&st4=Il&lid=1&ns0=NY%5F&lt0=42%2E97&st0=NY&zp2=90012&uf3=mia&ct4=Chicago&pty=accu&sc0=NYC055&st2=CA&zp4=60605&pt=accuweather&fz0=&wn0=%40NY&ar0=14472&zp0=14472&uf1=nyc&ct2=Los+Angeles&pti=&ins=aches%2Dpains&nx0=KBUF&cl0=ROC&zp1=10017&uf2=59l&ct3=Miami&inm=health&st1=NY&zp3=33128&uf4=ord&ver=0&nr0=NE&sz0=NYZ003&ct0=Honeoye+Falls&st3=FL&ptu=&mt=0; expires=Sat, 05-Mar-2011 00:00:00 GMT; path=/
Set-Cookie: aco=hi2=36&lo2=25&wx0=03&wc0=04&lo0=8&isi=6&lo1=16&dn0=day&icd=2&wx1=02&hi0=27&pl0=1&trv=1&wx2=22&hi1=28&dbg=0; path=/


<!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">
<hea
...[SNIP]...
5.4. http://www.accuweather.com/us/satellite/ei/us_/satellite.asp  previous

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.accuweather.com
Path:   /us/satellite/ei/us_/satellite.asp

Issue detail

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

Request

GET /us/satellite/ei/us_/satellite.asp HTTP/1.1
Host: www.accuweather.com
Proxy-Connection: keep-alive
Referer: http://burp/show/65
Cache-Control: max-age=0
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.10 (KHTML, like Gecko) Chrome/8.0.552.237 Safari/534.10
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: __utmz=256067995.1296754760.1.1.utmcsr=burp|utmccn=(referral)|utmcmd=referral|utmcct=/show/64; s_cc=true; s_sq=%5B%5BB%5D%5D; s_vi=[CS]v1|26A57416051D2589-4000012C8000F930[CE]; __qca=P0-1763970855-1296754771965; __utma=256067995.1249143252.1296754760.1296754760.1296754760.1; __utmc=256067995; __utmb=256067995.7.6.1296754772036; acm=ct1=Los+Angeles&uf0=nyc&lid=1&uf3=ord&zp2=33128&st0=NY&pty=accu&st2=FL&pt=accuweather&ct2=Miami&uf1=59l&zp0=10017&pti=&ins=aches%2Dpains&ct3=Chicago&uf2=mia&zp1=90012&inm=health&zp3=60605&st1=CA&ver=0&st3=Il&ct0=New+York&ptu=&mt=0; aco=dbg=0

Response

HTTP/1.1 200 OK
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
p3p: CP="NOI DSP COR ADMa DEVa TAIa PSAa PSDa IVAa IVDa CONi HISa OUR IND CNT"
Content-Type: text/html
Cache-Control: public
Vary: Accept-Encoding
Date: Thu, 03 Feb 2011 17:39:07 GMT
Connection: close
Set-Cookie: aco=dbg=0; path=/
Set-Cookie: acm=ptu=&mt=0&ct0=New+York&st3=Il&ver=0&st1=CA&zp3=60605&inm=health&zp1=90012&uf2=mia&ct3=Chicago&pti=&ins=aches%2Dpains&zp0=10017&uf1=59l&ct2=Miami&pt=accuweather&st2=FL&pty=accu&st0=NY&zp2=33128&uf3=ord&lid=1&uf0=nyc&ct1=Los+Angeles; expires=Sat, 05-Mar-2011 00:00:00 GMT; path=/
Content-Length: 64023

<!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">
<head>
...[SNIP]...
6. Robots.txt file  previous

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.accuweather.com
Path:   /us/NY/HONEOYE%20FALLS/14472/city-weather-forecast.asp

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

Response

HTTP/1.0 200 OK
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Content-Length: 1819
Content-Type: text/html
Cache-Control: private
Date: Thu, 03 Feb 2011 16:34:40 GMT
Connection: close

User-agent: *
Disallow: /_mm/
Disallow: /_notes/
Disallow: /_baks/
Disallow: /adc2004/
Disallow: /MMWIP/
Disallow: /m/storm.aspx
Disallow: /m/US/weather.aspx
Disallow: /m/US/radar.aspx
Disall
...[SNIP]...
Report generated by CloudScan Vulnerability Crawler at Fri Feb 04 13:07:25 CST 2011.