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 72d13"><script>alert(1)</script>fac055fa699 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.
Issue background
Reflected cross-site scripting vulnerabilities arise when data is copied from a request and echoed into the application's immediate response in an unsafe way. An attacker can use the vulnerability to construct a request which, if issued by another application user, will cause JavaScript code supplied by the attacker to execute within the user's browser in the context of that user's session with the application.
The attacker-supplied code can perform a wide variety of actions, such as stealing the victim's session token or login credentials, performing arbitrary actions on the victim's behalf, and logging their keystrokes.
Users can be induced to issue the attacker's crafted request in various ways. For example, the attacker can send a victim a link containing a malicious URL in an email or instant message. They can submit the link to popular web sites that allow content authoring, for example in blog comments. And they can create an innocuous looking web site which causes anyone viewing it to make arbitrary cross-domain requests to the vulnerable application (using either the GET or the POST method).
The security impact of cross-site scripting vulnerabilities is dependent upon the nature of the vulnerable application, the kinds of data and functionality which it contains, and the other applications which belong to the same domain and organisation. If the application is used only to display non-sensitive public content, with no authentication or access control functionality, then a cross-site scripting flaw may be considered low risk. However, if the same application resides on a domain which can access cookies for other more security-critical applications, then the vulnerability could be used to attack those other applications, and so may be considered high risk. Similarly, if the organisation which owns the application is a likely target for phishing attacks, then the vulnerability could be leveraged to lend credibility to such attacks, by injecting Trojan functionality into the vulnerable application, and exploiting users' trust in the organisation in order to capture credentials for other applications which it owns. In many kinds of application, such as those providing online banking functionality, cross-site scripting should always be considered high risk.
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 defenses:
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.
Request
GET /sso/google_apps?72d13"><script>alert(1)</script>fac055fa699=1 HTTP/1.1 Host: www.box.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmx=53496891.; __utmx_k_147955694=1; __utmz=53496891.1299807297.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); box_visitor_id=4d797bf5992305.74609987; referrer=; __utmxx=53496891.; visit_from_google=1; PHPSESSID=a6usvrpbj4tkvq9blhp12vj9e7; __utmx_k_189357682=1; __utma=53496891.1731721280.1299807297.1299807297.1299807297.1; __utmc=53496891; _jsuid=6977154960276415854; __utmb=53496891.16.10.1299807297;
Response
HTTP/1.1 200 OK Server: nginx/0.6.39 Date: Fri, 11 Mar 2011 01:39:09 GMT Content-Type: text/html; charset=utf-8 Connection: close p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT" Cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Expires: Thu, 19 Nov 1981 08:52:00 GMT Pragma: no-cache Content-Length: 1785
The application publishes a Flash cross-domain policy which uses a wildcard to specify allowed domains, and allows access from specific other domains.
Using a wildcard to specify allowed domains means that any domain matching the wildcard expression can perform two-way interaction with this application. You should only use this policy if you fully trust every possible web site that may reside on a domain which matches the wildcard expression.
Allowing access from specific domains means that web sites on those domains can perform two-way interaction with this application. You should only use this policy if you fully trust the specific domains allowed by the policy.
Issue background
The Flash cross-domain policy controls whether Flash client components running on other domains can perform two-way interaction with the domain which publishes the policy. If another domain is allowed by the policy, then that domain can potentially attack users of the application. If a user is logged in to the application, and visits a domain allowed by the policy, then any malicious content running on that domain can potentially gain full access to the application within the security context of the logged in user.
Even if an allowed domain is not overtly malicious in itself, security vulnerabilities within that domain could potentially be leveraged by a third-party attacker to exploit the trust relationship and attack the application which allows access.
Issue remediation
You should review the domains which are allowed by the Flash cross-domain policy and determine whether it is appropriate for the application to fully trust both the intentions and security posture of those domains.
Request
GET /crossdomain.xml HTTP/1.0 Host: www.box.net
Response
HTTP/1.1 200 OK Server: nginx/0.6.39 Date: Fri, 11 Mar 2011 01:34:39 GMT Content-Type: application/xml Connection: close Last-Modified: Fri, 28 Jan 2011 03:14:03 GMT ETag: "508135-436-4d42347b" Accept-Ranges: bytes Content-Length: 1078
3. Password field with autocomplete enabledpreviousnext
Summary
Severity:
Low
Confidence:
Certain
Host:
https://www.box.net
Path:
/login
Issue detail
The page contains a form with the following action URL:
https://www.box.net/login
The form contains the following password field with autocomplete enabled:
password
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).
Request
GET /login HTTP/1.1 Host: www.box.net 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.127 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: PHPSESSID=a6usvrpbj4tkvq9blhp12vj9e7; box_visitor_id=4d797bf5992305.74609987; __utmx=53496891.; __utmxx=53496891.; __utmz=53496891.1299807297.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); referrer=; __utma=53496891.1731721280.1299807297.1299807297.1299807297.1; __utmc=53496891; __utmb=53496891.3.10.1299807297
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"> <head>
The POSTing of data between domains does not necessarily constitute a security vulnerability. You should review the contents of the information that is being transmitted between domains, and determine whether the originating application should be trusting the receiving domain with this information.
The page contains a form which POSTs data to the domain www.salesforce.com. The form contains the following fields:
first_name
email
phone
submit1
Request
GET / HTTP/1.1 Host: www.box.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmx=53496891.; __utmx_k_147955694=1; __utmz=53496891.1299807297.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); box_visitor_id=4d797bf5992305.74609987; referrer=; __utmxx=53496891.; visit_from_google=1; PHPSESSID=a6usvrpbj4tkvq9blhp12vj9e7; __utmx_k_189357682=1; __utma=53496891.1731721280.1299807297.1299807297.1299807297.1; __utmc=53496891; _jsuid=6977154960276415854; __utmb=53496891.16.10.1299807297;
Response
HTTP/1.1 200 OK Server: nginx/0.6.39 Date: Fri, 11 Mar 2011 01:38:34 GMT Content-Type: text/html; charset=utf-8 Connection: close p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT" Cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Expires: Thu, 19 Nov 1981 08:52:00 GMT Pragma: no-cache Content-Length: 33543
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"> <head>
The page contains a form which POSTs data to the domain www.salesforce.com. The form contains the following fields:
first_name
email
phone
submit1
Request
GET /0168474161/goal HTTP/1.1 Host: www.box.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmx=53496891.; __utmx_k_147955694=1; __utmz=53496891.1299807297.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); box_visitor_id=4d797bf5992305.74609987; referrer=; __utmxx=53496891.; visit_from_google=1; PHPSESSID=a6usvrpbj4tkvq9blhp12vj9e7; __utmx_k_189357682=1; __utma=53496891.1731721280.1299807297.1299807297.1299807297.1; __utmc=53496891; _jsuid=6977154960276415854; __utmb=53496891.16.10.1299807297;
Response
HTTP/1.1 200 OK Server: nginx/0.6.39 Date: Fri, 11 Mar 2011 01:38:37 GMT Content-Type: text/html; charset=utf-8 Connection: close p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT" Cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Expires: Thu, 19 Nov 1981 08:52:00 GMT Pragma: no-cache Content-Length: 33721
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"> <head>
The page contains a form which POSTs data to the domain www.salesforce.com. The form contains the following fields:
first_name
email
phone
submit1
Request
GET /0698161564/test HTTP/1.1 Host: www.box.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmx=53496891.; __utmx_k_147955694=1; __utmz=53496891.1299807297.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); box_visitor_id=4d797bf5992305.74609987; referrer=; __utmxx=53496891.; visit_from_google=1; PHPSESSID=a6usvrpbj4tkvq9blhp12vj9e7; __utmx_k_189357682=1; __utma=53496891.1731721280.1299807297.1299807297.1299807297.1; __utmc=53496891; _jsuid=6977154960276415854; __utmb=53496891.16.10.1299807297;
Response
HTTP/1.1 200 OK Server: nginx/0.6.39 Date: Fri, 11 Mar 2011 01:38:40 GMT Content-Type: text/html; charset=utf-8 Connection: close p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT" Cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Expires: Thu, 19 Nov 1981 08:52:00 GMT Pragma: no-cache Content-Length: 33721
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"> <head>
The page contains a form which POSTs data to the domain www.salesforce.com. The form contains the following fields:
first_name
email
phone
submit1
Request
GET /2767692731/goal HTTP/1.1 Host: www.box.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmx=53496891.; __utmx_k_147955694=1; __utmz=53496891.1299807297.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); box_visitor_id=4d797bf5992305.74609987; referrer=; __utmxx=53496891.; visit_from_google=1; PHPSESSID=a6usvrpbj4tkvq9blhp12vj9e7; __utmx_k_189357682=1; __utma=53496891.1731721280.1299807297.1299807297.1299807297.1; __utmc=53496891; _jsuid=6977154960276415854; __utmb=53496891.16.10.1299807297;
Response
HTTP/1.1 200 OK Server: nginx/0.6.39 Date: Fri, 11 Mar 2011 01:38:36 GMT Content-Type: text/html; charset=utf-8 Connection: close p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT" Cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Expires: Thu, 19 Nov 1981 08:52:00 GMT Pragma: no-cache Content-Length: 33721
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"> <head>
The page contains a form which POSTs data to the domain www.salesforce.com. The form contains the following fields:
first_name
email
phone
submit1
Request
GET /2857954063/test HTTP/1.1 Host: www.box.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmx=53496891.; __utmx_k_147955694=1; __utmz=53496891.1299807297.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); box_visitor_id=4d797bf5992305.74609987; referrer=; __utmxx=53496891.; visit_from_google=1; PHPSESSID=a6usvrpbj4tkvq9blhp12vj9e7; __utmx_k_189357682=1; __utma=53496891.1731721280.1299807297.1299807297.1299807297.1; __utmc=53496891; _jsuid=6977154960276415854; __utmb=53496891.16.10.1299807297;
Response
HTTP/1.1 200 OK Server: nginx/0.6.39 Date: Fri, 11 Mar 2011 01:38:38 GMT Content-Type: text/html; charset=utf-8 Connection: close p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT" Cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Expires: Thu, 19 Nov 1981 08:52:00 GMT Pragma: no-cache Content-Length: 33721
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"> <head>
The page contains a form which POSTs data to the domain www.salesforce.com. The form contains the following fields:
first_name
email
phone
submit1
Request
GET /4160166265/test HTTP/1.1 Host: www.box.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmx=53496891.; __utmx_k_147955694=1; __utmz=53496891.1299807297.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); box_visitor_id=4d797bf5992305.74609987; referrer=; __utmxx=53496891.; visit_from_google=1; PHPSESSID=a6usvrpbj4tkvq9blhp12vj9e7; __utmx_k_189357682=1; __utma=53496891.1731721280.1299807297.1299807297.1299807297.1; __utmc=53496891; _jsuid=6977154960276415854; __utmb=53496891.16.10.1299807297;
Response
HTTP/1.1 200 OK Server: nginx/0.6.39 Date: Fri, 11 Mar 2011 01:38:41 GMT Content-Type: text/html; charset=utf-8 Connection: close p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT" Cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Expires: Thu, 19 Nov 1981 08:52:00 GMT Pragma: no-cache Content-Length: 33717
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"> <head>
The page contains a form which POSTs data to the domain www.salesforce.com. The form contains the following fields:
first_name
email
phone
submit1
Request
GET /home HTTP/1.1 Host: www.box.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmx=53496891.; __utmx_k_147955694=1; __utmz=53496891.1299807297.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); box_visitor_id=4d797bf5992305.74609987; referrer=; __utmxx=53496891.; visit_from_google=1; PHPSESSID=a6usvrpbj4tkvq9blhp12vj9e7; __utmx_k_189357682=1; __utma=53496891.1731721280.1299807297.1299807297.1299807297.1; __utmc=53496891; _jsuid=6977154960276415854; __utmb=53496891.16.10.1299807297;
Response
HTTP/1.1 200 OK Server: nginx/0.6.39 Date: Fri, 11 Mar 2011 01:38:20 GMT Content-Type: text/html; charset=utf-8 Connection: close p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT" Cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Expires: Thu, 19 Nov 1981 08:52:00 GMT Pragma: no-cache Content-Length: 33539
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"> <head>
The page contains a form which POSTs data to the domain www.salesforce.com. The form contains the following fields:
first_name
email
phone
submit1
Request
GET /siteopt.js HTTP/1.1 Host: www.box.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmx=53496891.; __utmx_k_147955694=1; __utmz=53496891.1299807297.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); box_visitor_id=4d797bf5992305.74609987; referrer=; __utmxx=53496891.; visit_from_google=1; PHPSESSID=a6usvrpbj4tkvq9blhp12vj9e7; __utmx_k_189357682=1; __utma=53496891.1731721280.1299807297.1299807297.1299807297.1; __utmc=53496891; _jsuid=6977154960276415854; __utmb=53496891.16.10.1299807297;
Response
HTTP/1.1 404 Not Found Server: nginx/0.6.39 Date: Fri, 11 Mar 2011 01:38:30 GMT Content-Type: text/html; charset=utf-8 Connection: close p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT" Cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Expires: Thu, 19 Nov 1981 08:52:00 GMT Pragma: no-cache Content-Length: 33721
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"> <head>
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 /siteopt.js?v=1&utmxkey= HTTP/1.1 Host: www.box.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmx=53496891.; __utmx_k_147955694=1; __utmz=53496891.1299807297.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); box_visitor_id=4d797bf5992305.74609987; referrer=; __utmxx=53496891.; visit_from_google=1; PHPSESSID=a6usvrpbj4tkvq9blhp12vj9e7; __utmx_k_189357682=1; __utma=53496891.1731721280.1299807297.1299807297.1299807297.1; __utmc=53496891; _jsuid=6977154960276415854; __utmb=53496891.16.10.1299807297;
Response
HTTP/1.1 404 Not Found Server: nginx/0.6.39 Date: Fri, 11 Mar 2011 01:38:31 GMT Content-Type: text/html; charset=utf-8 Connection: close p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT" Cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Expires: Thu, 19 Nov 1981 08:52:00 GMT Pragma: no-cache Content-Length: 33721
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"> <head>
When an application includes a script from an external domain, this script is executed by the browser within the security context of the invoking application. The script can therefore do anything that the application's own scripts can do, such as accessing application data and performing actions within the context of the current user.
If you include a script from an external domain, then you are trusting that domain with the data and functionality of your application, and you are trusting the domain's own security to prevent an attacker from modifying the script to perform malicious actions within your application.
Issue remediation
Scripts should not be included from untrusted domains. If you have a requirement which a third-party script appears to fulfil, then you should ideally copy the contents of that script onto your own domain and include it from there. If that is not possible (e.g. for licensing reasons) then you should consider reimplementing the script's functionality within your own code.
GET / HTTP/1.1 Host: www.box.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmx=53496891.; __utmx_k_147955694=1; __utmz=53496891.1299807297.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); box_visitor_id=4d797bf5992305.74609987; referrer=; __utmxx=53496891.; visit_from_google=1; PHPSESSID=a6usvrpbj4tkvq9blhp12vj9e7; __utmx_k_189357682=1; __utma=53496891.1731721280.1299807297.1299807297.1299807297.1; __utmc=53496891; _jsuid=6977154960276415854; __utmb=53496891.16.10.1299807297;
Response
HTTP/1.1 200 OK Server: nginx/0.6.39 Date: Fri, 11 Mar 2011 01:38:34 GMT Content-Type: text/html; charset=utf-8 Connection: close p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT" Cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Expires: Thu, 19 Nov 1981 08:52:00 GMT Pragma: no-cache Content-Length: 33543
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"> <head>
GET /0168474161/goal HTTP/1.1 Host: www.box.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmx=53496891.; __utmx_k_147955694=1; __utmz=53496891.1299807297.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); box_visitor_id=4d797bf5992305.74609987; referrer=; __utmxx=53496891.; visit_from_google=1; PHPSESSID=a6usvrpbj4tkvq9blhp12vj9e7; __utmx_k_189357682=1; __utma=53496891.1731721280.1299807297.1299807297.1299807297.1; __utmc=53496891; _jsuid=6977154960276415854; __utmb=53496891.16.10.1299807297;
Response
HTTP/1.1 200 OK Server: nginx/0.6.39 Date: Fri, 11 Mar 2011 01:38:37 GMT Content-Type: text/html; charset=utf-8 Connection: close p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT" Cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Expires: Thu, 19 Nov 1981 08:52:00 GMT Pragma: no-cache Content-Length: 33721
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"> <head>
GET /0698161564/test HTTP/1.1 Host: www.box.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmx=53496891.; __utmx_k_147955694=1; __utmz=53496891.1299807297.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); box_visitor_id=4d797bf5992305.74609987; referrer=; __utmxx=53496891.; visit_from_google=1; PHPSESSID=a6usvrpbj4tkvq9blhp12vj9e7; __utmx_k_189357682=1; __utma=53496891.1731721280.1299807297.1299807297.1299807297.1; __utmc=53496891; _jsuid=6977154960276415854; __utmb=53496891.16.10.1299807297;
Response
HTTP/1.1 200 OK Server: nginx/0.6.39 Date: Fri, 11 Mar 2011 01:38:40 GMT Content-Type: text/html; charset=utf-8 Connection: close p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT" Cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Expires: Thu, 19 Nov 1981 08:52:00 GMT Pragma: no-cache Content-Length: 33721
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"> <head>
GET /2767692731/goal HTTP/1.1 Host: www.box.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmx=53496891.; __utmx_k_147955694=1; __utmz=53496891.1299807297.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); box_visitor_id=4d797bf5992305.74609987; referrer=; __utmxx=53496891.; visit_from_google=1; PHPSESSID=a6usvrpbj4tkvq9blhp12vj9e7; __utmx_k_189357682=1; __utma=53496891.1731721280.1299807297.1299807297.1299807297.1; __utmc=53496891; _jsuid=6977154960276415854; __utmb=53496891.16.10.1299807297;
Response
HTTP/1.1 200 OK Server: nginx/0.6.39 Date: Fri, 11 Mar 2011 01:38:36 GMT Content-Type: text/html; charset=utf-8 Connection: close p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT" Cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Expires: Thu, 19 Nov 1981 08:52:00 GMT Pragma: no-cache Content-Length: 33721
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"> <head>
GET /2857954063/test HTTP/1.1 Host: www.box.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmx=53496891.; __utmx_k_147955694=1; __utmz=53496891.1299807297.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); box_visitor_id=4d797bf5992305.74609987; referrer=; __utmxx=53496891.; visit_from_google=1; PHPSESSID=a6usvrpbj4tkvq9blhp12vj9e7; __utmx_k_189357682=1; __utma=53496891.1731721280.1299807297.1299807297.1299807297.1; __utmc=53496891; _jsuid=6977154960276415854; __utmb=53496891.16.10.1299807297;
Response
HTTP/1.1 200 OK Server: nginx/0.6.39 Date: Fri, 11 Mar 2011 01:38:38 GMT Content-Type: text/html; charset=utf-8 Connection: close p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT" Cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Expires: Thu, 19 Nov 1981 08:52:00 GMT Pragma: no-cache Content-Length: 33721
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"> <head>
GET /4160166265/test HTTP/1.1 Host: www.box.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmx=53496891.; __utmx_k_147955694=1; __utmz=53496891.1299807297.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); box_visitor_id=4d797bf5992305.74609987; referrer=; __utmxx=53496891.; visit_from_google=1; PHPSESSID=a6usvrpbj4tkvq9blhp12vj9e7; __utmx_k_189357682=1; __utma=53496891.1731721280.1299807297.1299807297.1299807297.1; __utmc=53496891; _jsuid=6977154960276415854; __utmb=53496891.16.10.1299807297;
Response
HTTP/1.1 200 OK Server: nginx/0.6.39 Date: Fri, 11 Mar 2011 01:38:41 GMT Content-Type: text/html; charset=utf-8 Connection: close p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT" Cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Expires: Thu, 19 Nov 1981 08:52:00 GMT Pragma: no-cache Content-Length: 33717
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"> <head>
GET /home HTTP/1.1 Host: www.box.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmx=53496891.; __utmx_k_147955694=1; __utmz=53496891.1299807297.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); box_visitor_id=4d797bf5992305.74609987; referrer=; __utmxx=53496891.; visit_from_google=1; PHPSESSID=a6usvrpbj4tkvq9blhp12vj9e7; __utmx_k_189357682=1; __utma=53496891.1731721280.1299807297.1299807297.1299807297.1; __utmc=53496891; _jsuid=6977154960276415854; __utmb=53496891.16.10.1299807297;
Response
HTTP/1.1 200 OK Server: nginx/0.6.39 Date: Fri, 11 Mar 2011 01:38:20 GMT Content-Type: text/html; charset=utf-8 Connection: close p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT" Cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Expires: Thu, 19 Nov 1981 08:52:00 GMT Pragma: no-cache Content-Length: 33539
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"> <head>
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"> <head>
GET /signup HTTP/1.1 Host: www.box.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmx=53496891.; __utmx_k_147955694=1; __utmz=53496891.1299807297.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); box_visitor_id=4d797bf5992305.74609987; referrer=; __utmxx=53496891.; visit_from_google=1; PHPSESSID=a6usvrpbj4tkvq9blhp12vj9e7; __utmx_k_189357682=1; __utma=53496891.1731721280.1299807297.1299807297.1299807297.1; __utmc=53496891; _jsuid=6977154960276415854; __utmb=53496891.16.10.1299807297;
Response
HTTP/1.1 200 OK Server: nginx/0.6.39 Date: Fri, 11 Mar 2011 01:38:35 GMT Content-Type: text/html; charset=utf-8 Connection: close p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT" Cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Expires: Thu, 19 Nov 1981 08:52:00 GMT Pragma: no-cache Content-Length: 27650
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"> <head>
GET /signup/business HTTP/1.1 Host: www.box.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmx=53496891.; __utmx_k_147955694=1; __utmz=53496891.1299807297.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); box_visitor_id=4d797bf5992305.74609987; referrer=; __utmxx=53496891.; visit_from_google=1; PHPSESSID=a6usvrpbj4tkvq9blhp12vj9e7; __utmx_k_189357682=1; __utma=53496891.1731721280.1299807297.1299807297.1299807297.1; __utmc=53496891; _jsuid=6977154960276415854; __utmb=53496891.16.10.1299807297;
Response
HTTP/1.1 200 OK Server: nginx/0.6.39 Date: Fri, 11 Mar 2011 01:38:19 GMT Content-Type: text/html; charset=utf-8 Connection: close p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT" Cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Expires: Thu, 19 Nov 1981 08:52:00 GMT Pragma: no-cache Content-Length: 28157
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"> <head>
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"> <head>
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"> <head>
GET /siteopt.js HTTP/1.1 Host: www.box.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmx=53496891.; __utmx_k_147955694=1; __utmz=53496891.1299807297.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); box_visitor_id=4d797bf5992305.74609987; referrer=; __utmxx=53496891.; visit_from_google=1; PHPSESSID=a6usvrpbj4tkvq9blhp12vj9e7; __utmx_k_189357682=1; __utma=53496891.1731721280.1299807297.1299807297.1299807297.1; __utmc=53496891; _jsuid=6977154960276415854; __utmb=53496891.16.10.1299807297;
Response
HTTP/1.1 404 Not Found Server: nginx/0.6.39 Date: Fri, 11 Mar 2011 01:38:30 GMT Content-Type: text/html; charset=utf-8 Connection: close p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT" Cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Expires: Thu, 19 Nov 1981 08:52:00 GMT Pragma: no-cache Content-Length: 33721
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"> <head>
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).
The following email addresses were disclosed in the response:
legal@box.net
sales@box.net
support@box.net
Request
GET /static/html/terms.html HTTP/1.1 Host: www.box.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmx=53496891.; __utmx_k_147955694=1; __utmz=53496891.1299807297.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); box_visitor_id=4d797bf5992305.74609987; referrer=; __utmxx=53496891.; visit_from_google=1; PHPSESSID=a6usvrpbj4tkvq9blhp12vj9e7; __utmx_k_189357682=1; __utma=53496891.1731721280.1299807297.1299807297.1299807297.1; __utmc=53496891; _jsuid=6977154960276415854; __utmb=53496891.16.10.1299807297;
Response
HTTP/1.1 200 OK Server: nginx/0.6.39 Date: Fri, 11 Mar 2011 01:38:33 GMT Content-Type: text/html Content-Length: 40462 Last-Modified: Thu, 10 Mar 2011 00:12:55 GMT Connection: close Expires: Thu, 31 Dec 2037 23:55:55 GMT Cache-Control: max-age=315360000 Accept-Ranges: bytes
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <head> <title>Box.net :: Terms</title>
<meta http-equiv="Content-Type" co ...[SNIP]... time to respond to your message. Delays in our support system do not qualify as a reason to extend your trial period, or excuse canceling after 14 days. Cancellation requests sent via email to either sales@box.net or support@box.net will not be processed and will be replied to with an automatic response. You must use our form to process your cancellation.</p> ...[SNIP]... <a href="mailto:legal@box.net">legal@box.net</a> ...[SNIP]...
The file robots.txt is used to give instructions to web robots, such as search engine crawlers, about locations within the web site which robots are allowed, or not allowed, to crawl and index.
The presence of the robots.txt does not in itself present any kind of security vulnerability. However, it is often used to identify restricted or private areas of a site's contents. The information in the file may therefore help an attacker to map out the site's contents, especially if some of the locations identified are not linked from elsewhere in the site. If the application relies on robots.txt to protect access to these areas, and does not enforce proper access control over them, then this presents a serious vulnerability.
Issue remediation
The robots.txt file is not itself a security threat, and its correct use can represent good practice for non-security reasons. You should not assume that all web robots will honour the file's instructions. Rather, assume that attackers will pay close attention to any locations identified in the file. Do not rely on robots.txt to provide any kind of protection over unauthorised access.
Request
GET /robots.txt HTTP/1.0 Host: www.box.net
Response
HTTP/1.1 200 OK Server: nginx/0.6.39 Date: Fri, 11 Mar 2011 01:34:40 GMT Content-Type: text/plain Content-Length: 133 Last-Modified: Thu, 10 Mar 2011 00:13:04 GMT Connection: close Expires: Thu, 31 Dec 2037 23:55:55 GMT Cache-Control: max-age=315360000 Accept-Ranges: bytes
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 states that it contains HTML content but does not specify a character set, then the browser may analyse the HTML and attempt to determine which character set it appears to be using. Even if the majority of the HTML actually employs a standard character set such as UTF-8, the presence of non-standard characters anywhere in the response may cause the browser to interpret the content using a different character set. This can have unexpected results, and can lead to cross-site scripting vulnerabilities in which non-standard encodings like UTF-7 can be used to bypass the application's defensive filters.
In most cases, the absence of a charset directive 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 HTML content, the application should include within the Content-type header a directive specifying a standard recognised character set, for example charset=ISO-8859-1.
Request
GET /static/html/privacy.html HTTP/1.1 Host: www.box.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: __utmx=53496891.; __utmx_k_147955694=1; __utmz=53496891.1299807297.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); box_visitor_id=4d797bf5992305.74609987; referrer=; __utmxx=53496891.; visit_from_google=1; PHPSESSID=a6usvrpbj4tkvq9blhp12vj9e7; __utmx_k_189357682=1; __utma=53496891.1731721280.1299807297.1299807297.1299807297.1; __utmc=53496891; _jsuid=6977154960276415854; __utmb=53496891.16.10.1299807297;
Response
HTTP/1.1 200 OK Server: nginx/0.6.39 Date: Fri, 11 Mar 2011 01:38:34 GMT Content-Type: text/html Content-Length: 13996 Last-Modified: Thu, 10 Mar 2011 00:14:25 GMT Connection: close Expires: Thu, 31 Dec 2037 23:55:55 GMT Cache-Control: max-age=315360000 Accept-Ranges: bytes
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <head> <title> Box.net :: Privacy Policy </title>
The server presented a valid, trusted SSL certificate. This issue is purely informational.
The server presented the following certificates:
Server certificate
Issued to:
*.box.net
Issued by:
Network Solutions Certificate Authority
Valid from:
Fri May 02 19:00:00 CDT 2008
Valid to:
Sat Oct 22 18:59:59 CDT 2011
Certificate chain #1
Issued to:
Network Solutions Certificate Authority
Issued by:
UTN-USERFirst-Hardware
Valid from:
Sun Apr 09 19:00:00 CDT 2006
Valid to:
Sat May 30 05:48:38 CDT 2020
Certificate chain #2
Issued to:
UTN-USERFirst-Hardware
Issued by:
UTN-USERFirst-Hardware
Valid from:
Fri Jul 09 13:10:42 CDT 1999
Valid to:
Tue Jul 09 13:19:22 CDT 2019
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 Research Blog at Fri Mar 11 06:51:26 CST 2011.