XSS, Reflected Cross Site Scripting, CWE-79, CAPEC-86, DORK, GHDB, BHDB, api.mywot.com

Report generated by XSS.CX at Thu Sep 15 21:53:35 GMT-06:00 2011.

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

1. Cross-site scripting (reflected)

2. Email addresses disclosed

2.1. http://api.mywot.com/widgets/ratings.js

2.2. http://api.mywot.com/widgets/ratingwidget.js

1. Cross-site scripting (reflected) next

Summary

Severity:	High
Confidence:	Certain
Host:	http://api.mywot.com
Path:	/0.4/public_link_json

Issue detail

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

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.

Request

GET /0.4/public_link_json?hosts=www.topspot.fi/www.fambit.com/www.consultantbox.com/www.translizer.com/&callback=jQuery152028631591401062906_1316132905299ff384<script>alert(1)</script>0046f50ec52&_=1316132905483 HTTP/1.1
Host: api.mywot.com
Proxy-Connection: keep-alive
Referer: http://www.mywot.com/en/trustseal
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 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: SESSf6ce7e3db235723091e59a653e7d96f2=n1adbhiatrep1c3k5lvva32fh4; __utma=90529926.1433214644.1316132805.1316132805.1316132805.1; __utmb=90529926.2.10.1316132805; __utmc=90529926; __utmz=90529926.1316132805.1.1.utmcsr=google|utmccn=(organic)|utmcmd=organic|utmctr=web%20of%20trust

Response

HTTP/1.1 200 OK
Date: Thu, 15 Sep 2011 19:28:31 GMT
Server: Apache
Cache-Control: no-store, max-age=0
Expires: Thu, 15 Sep 2011 19:28:31 GMT
Vary: Accept-Encoding
Content-Length: 565
Connection: close
Content-Type: application/x-javascript

jQuery152028631591401062906_1316132905299ff384<script>alert(1)</script>0046f50ec52({ "www.topspot.fi": { "target": "topspot.fi", "0": [ 95, 17 ], "1": [ 96, 17 ], "2": [ 95, 17 ], "4": [ 95, 18 ] }, "www.fambit.com": { "target": "fambit.com", "0": [ 92, 34 ], "1": [ 91, 31 ], "2": [
...[SNIP]...

2. Email addresses disclosed previous
There are 2 instances of this issue:

/widgets/ratings.js
/widgets/ratingwidget.js

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).

2.1. http://api.mywot.com/widgets/ratings.js next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://api.mywot.com
Path:	/widgets/ratings.js

Issue detail

The following email address was disclosed in the response:

info@mywot.com

Request

GET /widgets/ratings.js HTTP/1.1
Host: api.mywot.com
Proxy-Connection: keep-alive
Referer: http://www.mywot.com/en/scorecard/xss.cx
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 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: SESSf6ce7e3db235723091e59a653e7d96f2=n1adbhiatrep1c3k5lvva32fh4; __utma=90529926.1433214644.1316132805.1316132805.1316132805.1; __utmb=90529926.1.10.1316132805; __utmc=90529926; __utmz=90529926.1316132805.1.1.utmcsr=google|utmccn=(organic)|utmcmd=organic|utmctr=web%20of%20trust

Response

HTTP/1.1 200 OK
Date: Thu, 15 Sep 2011 19:26:46 GMT
Server: Apache
Last-Modified: Mon, 17 Jan 2011 10:04:03 GMT
Accept-Ranges: bytes
Cache-Control: max-age=259200
Expires: Sun, 18 Sep 2011 19:26:46 GMT
Vary: Accept-Encoding
Content-Length: 449
Connection: close
Content-Type: application/javascript

/* Copyright .. 2008 WOT Services Oy <info@mywot.com> */
var wotprotocol = (document.location.protocol == "https:") ? "https://" : "http://";
var wotbase = wotprotocol + "api.mywot.com/widgets";
var
...[SNIP]...

2.2. http://api.mywot.com/widgets/ratingwidget.js previous

Summary

Severity:	Information
Confidence:	Certain
Host:	http://api.mywot.com
Path:	/widgets/ratingwidget.js

Issue detail

The following email address was disclosed in the response:

info@mywot.com

Request

GET /widgets/ratingwidget.js HTTP/1.1
Host: api.mywot.com
Proxy-Connection: keep-alive
Referer: http://www.mywot.com/en/scorecard/xss.cx
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.220 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: SESSf6ce7e3db235723091e59a653e7d96f2=n1adbhiatrep1c3k5lvva32fh4; __utma=90529926.1433214644.1316132805.1316132805.1316132805.1; __utmb=90529926.1.10.1316132805; __utmc=90529926; __utmz=90529926.1316132805.1.1.utmcsr=google|utmccn=(organic)|utmcmd=organic|utmctr=web%20of%20trust

Response

HTTP/1.1 200 OK
Date: Thu, 15 Sep 2011 19:26:47 GMT
Server: Apache
Last-Modified: Mon, 17 Jan 2011 10:04:03 GMT
Accept-Ranges: bytes
Cache-Control: max-age=259200
Expires: Sun, 18 Sep 2011 19:26:47 GMT
Vary: Accept-Encoding
Content-Length: 4474
Connection: close
Content-Type: application/javascript

/* Copyright .. 2011 WOT Services Oy <info@mywot.com> */
eval(function(p,a,c,k,e,r){e=function(c){return(c<a?'':e(parseInt(c/a)))+((c=c%a)>35?String.fromCharCode(c+29):c.toString(36))};if(!''.replace
...[SNIP]...

Report generated by XSS.CX at Thu Sep 15 21:53:35 GMT-06:00 2011.