XSS, Reflected Cross Site Scripting, CWE-79, CAPEC-86, DORK, GHDB, BHDB, vivu.tv

The value of the id request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 7351a"%3balert(1)//abc08766de5 was submitted in the id parameter. This input was echoed as 7351a";alert(1)//abc08766de5 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.

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.

Request

GET /portal/archive.jsp?flow=948-295-2887&id=12894091672287351a"%3balert(1)//abc08766de5 HTTP/1.1
Host: vivu.tv
Proxy-Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.187 Safari/535.1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Referer: http://aws.amazon.com/officehours/
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: Sun, 02 Oct 2011 01:41:47 GMT
Server: Apache/2.2.9 (Fedora)
Pragma: No-cache
Cache-Control: no-cache
Expires: Mon, 01 Oct 2012 01:41:47 GMT
P3P: CP='NOI ADM DEV PSAi COM NAV OUR OTR STP IND DEM'
Content-Length: 5194
Connection: close
Content-Type: text/html;charset=ISO-8859-1

<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" xml:
...[SNIP]...
shvars.unique = "1.1.3268";
       flashvars.flow = "948-295-2887";
       flashvars.email = "null";
       flashvars.recordPlayerMode = "true";
       flashvars.serverDomain = "null";
       flashvars.id = "12894091672287351a";alert(1)//abc08766de5";
       flashvars.http_cdn = "";
       flashvars.skins = "default";
       flashvars.titleColor = "0xFFFFFF";
       flashvars.bwDone = "null";
       flashvars.downbw = "null";
       flashvars.upbw = "null";
       flashvars
...[SNIP]...

2. Source code disclosure previous next

Summary

Severity:	Low
Confidence:	Tentative
Host:	http://vivu.tv
Path:	/portal/javascript/consoles/common.js

Issue detail

The application appears to disclose some server-side source code written in ASP.

Issue background

Server-side source code may contain sensitive information which can help an attacker formulate attacks against the application.

Issue remediation

Server-side source code is normally disclosed to clients as a result of typographical errors in scripts or because of misconfiguration, such as failing to grant executable permissions to a script or directory. You should review the cause of the code disclosure and prevent it from happening.

Request

GET /portal/javascript/consoles/common.js HTTP/1.1
Host: vivu.tv
Proxy-Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.187 Safari/535.1
Accept: */*
Referer: http://vivu.tv/portal/archive.jsp?flow=948-295-2887&id=1289409167228
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: JSESSIONID=98AA6E835650C2E66F4641D21E6BA278.worker2

Response

HTTP/1.1 200 OK
Date: Sun, 02 Oct 2011 01:41:42 GMT
Server: Apache/2.2.9 (Fedora)
Pragma: No-cache
Cache-Control: no-cache
Expires: Mon, 01 Oct 2012 01:41:43 GMT
Accept-Ranges: bytes
ETag: W/"26973-1314923992000"
Last-Modified: Fri, 02 Sep 2011 00:39:52 GMT
Content-Length: 26973
Connection: close
Content-Type: text/javascript

var desktopStartedFromJS = false;
var desktopSharingURL = "";
var desktopSharingStreamName = "";
var listener = null;

//hq tool javascript
var pluginPresent = false;
var systemCapable = "Unava
...[SNIP]...
direct?locale=en&host=java.com:80');
   }
   else{
       if(getBrowserIndependentApplet() == null)
       {
           addApplet("hqtool","com.vivu.browserplugin.ViVuHQTool","/ViVuFlashWeb/plugin/browserplugin.jar?t=<%=(new Date()).getTime()%>",0,0,"enable Java",'installVHDriver');
       }
       else
       {
           try
           {
               getBrowserIndependentApplet().jsInstallVHdriver();
               vhDriverInstallActive = true;
           }
           catch(err)
           {
               vhDri
...[SNIP]...

3. Cross-domain Referer leakage previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://vivu.tv
Path:	/portal/archive.jsp

Issue detail

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

http://vivu.tv/portal/archive.jsp?flow=948-295-2887&id=1289409167228

The response contains the following links to other domains:

http://www.adobe.com/images/shared/download_buttons/get_flash_player.gif
http://www.macromedia.com/go/getflash/

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 /portal/archive.jsp?flow=948-295-2887&id=1289409167228 HTTP/1.1
Host: vivu.tv
Proxy-Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.187 Safari/535.1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Referer: http://aws.amazon.com/officehours/
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: Sun, 02 Oct 2011 01:41:42 GMT
Server: Apache/2.2.9 (Fedora)
Pragma: No-cache
Cache-Control: no-cache
Expires: Mon, 01 Oct 2012 01:41:42 GMT
P3P: CP='NOI ADM DEV PSAi COM NAV OUR OTR STP IND DEM'
Content-Length: 5404
Connection: close
Content-Type: text/html;charset=ISO-8859-1

<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" xml:
...[SNIP]...
<br>     <a href="http://www.macromedia.com/go/getflash/" target="_blank"><img src="http://www.adobe.com/images/shared/download_buttons/get_flash_player.gif"/></a>

Get <a href="http://www.macromedia.com/go/getflash/" target="_blank">latest Flash Player</a>
...[SNIP]...

4. Cross-domain script include previous next
There are 2 instances of this issue:

/vivuweb/
/vivuweb/products/vucast/request/

Issue background

When an application includes a script from an external domain, this script is executed by the browser within the security context of the invoking application. The script can therefore do anything that the application's own scripts can do, such as accessing application data and performing actions within the context of the current user.

If you include a script from an external domain, then you are trusting that domain with the data and functionality of your application, and you are trusting the domain's own security to prevent an attacker from modifying the script to perform malicious actions within your application.

Issue remediation

Scripts should not be included from untrusted domains. If you have a requirement which a third-party script appears to fulfil, then you should ideally copy the contents of that script onto your own domain and include it from there. If that is not possible (e.g. for licensing reasons) then you should consider reimplementing the script's functionality within your own code.

4.1. http://vivu.tv/vivuweb/ next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://vivu.tv
Path:	/vivuweb/

Issue detail

The response dynamically includes the following script from another domain:

http://www.google.com/jsapi?key=AB

Request

GET /vivuweb/ HTTP/1.1
Host: vivu.tv
Proxy-Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.187 Safari/535.1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Referer: http://vivu.tv/
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: __utma=66968105.1713489603.1317519750.1317519750.1317519750.1; __utmb=66968105.1.10.1317519750; __utmc=66968105; __utmz=66968105.1317519750.1.1.utmcsr=aws.amazon.com|utmccn=(referral)|utmcmd=referral|utmcct=/officehours/

Response

HTTP/1.1 200 OK
Date: Sun, 02 Oct 2011 01:46:04 GMT
Server: Apache/2.2.9 (Fedora)
Content-Length: 48214
Connection: close
Content-Type: text/html;charset=ISO-8859-1

<!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">

<!--

ViVu Technologies -
...[SNIP]...
</script>
<script language="javascript" type="text/javascript" src="http://www.google.com/jsapi?key=AB"></script>
...[SNIP]...

4.2. http://vivu.tv/vivuweb/products/vucast/request/ previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://vivu.tv
Path:	/vivuweb/products/vucast/request/

Issue detail

The response dynamically includes the following script from another domain:

http://s7.addthis.com/js/250/addthis_widget.js

Request

GET /vivuweb/products/vucast/request/ HTTP/1.1
Host: vivu.tv
Proxy-Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.187 Safari/535.1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Referer: http://vivu.tv/vivuweb/
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: JSESSIONID=52C09E2038E3B5E245FAA55A8756D835.worker2; __utma=66968105.1713489603.1317519750.1317519750.1317519750.1; __utmb=66968105.2.10.1317519750; __utmc=66968105; __utmz=66968105.1317519750.1.1.utmcsr=aws.amazon.com|utmccn=(referral)|utmcmd=referral|utmcct=/officehours/; kvcd=1317520013864; km_ai=ALemYfPbGpC9WzQgbNrfvrNjHx0%3D; km_vs=1; km_lv=1317520014; km_uq=

Response

HTTP/1.1 200 OK
Date: Sun, 02 Oct 2011 01:46:23 GMT
Server: Apache/2.2.9 (Fedora)
Content-Length: 25859
Connection: close
Content-Type: text/html;charset=ISO-8859-1

<!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">

<!--

ViVu Technologies -
...[SNIP]...
</div>
<script type="text/javascript" src="http://s7.addthis.com/js/250/addthis_widget.js#username=tandav"></script>
...[SNIP]...

5. Email addresses disclosed previous next
There are 4 instances of this issue:

/vivuweb/js/common/en.js
/vivuweb/js/common/formcheck.js
/vivuweb/js/common/mootools-1.2.4.4-more.js
/vivuweb/products/vucast/request/

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

5.1. http://vivu.tv/vivuweb/js/common/en.js previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://vivu.tv
Path:	/vivuweb/js/common/en.js

Issue detail

The following email address was disclosed in the response:

yourname@domain.com

Request

GET /vivuweb/js/common/en.js HTTP/1.1
Host: vivu.tv
Proxy-Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.187 Safari/535.1
Accept: */*
Referer: http://vivu.tv/vivuweb/products/vucast/request/
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: JSESSIONID=52C09E2038E3B5E245FAA55A8756D835.worker2; __utma=66968105.1713489603.1317519750.1317519750.1317519750.1; __utmb=66968105.2.10.1317519750; __utmc=66968105; __utmz=66968105.1317519750.1.1.utmcsr=aws.amazon.com|utmccn=(referral)|utmcmd=referral|utmcct=/officehours/; kvcd=1317520013864; km_ai=ALemYfPbGpC9WzQgbNrfvrNjHx0%3D; km_vs=1; km_lv=1317520014; km_uq=

Response

HTTP/1.1 200 OK
Date: Sun, 02 Oct 2011 01:46:23 GMT
Server: Apache/2.2.9 (Fedora)
Accept-Ranges: bytes
ETag: W/"1350-1272607484000"
Last-Modified: Fri, 30 Apr 2010 06:04:44 GMT
Content-Length: 1350
Connection: close
Content-Type: text/javascript
X-Pad: avoid browser bug

formcheckLanguage = {
   required: "This field is required.",
   alpha: "This field accepts alphabetic characters only.",
   alphanum: "This field accepts alphanumeric characters only.",
   nodigit: "No digit
...[SNIP]...
<span>E.g. yourname@domain.com</span>
...[SNIP]...

5.2. http://vivu.tv/vivuweb/js/common/formcheck.js previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://vivu.tv
Path:	/vivuweb/js/common/formcheck.js

Issue detail

The following email address was disclosed in the response:

yourname@domain.com

Request

GET /vivuweb/js/common/formcheck.js HTTP/1.1
Host: vivu.tv
Proxy-Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.187 Safari/535.1
Accept: */*
Referer: http://vivu.tv/vivuweb/products/vucast/request/
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: JSESSIONID=52C09E2038E3B5E245FAA55A8756D835.worker2; __utma=66968105.1713489603.1317519750.1317519750.1317519750.1; __utmb=66968105.2.10.1317519750; __utmc=66968105; __utmz=66968105.1317519750.1.1.utmcsr=aws.amazon.com|utmccn=(referral)|utmcmd=referral|utmcct=/officehours/; kvcd=1317520013864; km_ai=ALemYfPbGpC9WzQgbNrfvrNjHx0%3D; km_vs=1; km_lv=1317520014; km_uq=

Response

HTTP/1.1 200 OK
Date: Sun, 02 Oct 2011 01:46:23 GMT
Server: Apache/2.2.9 (Fedora)
Accept-Ranges: bytes
ETag: W/"40570-1294970362000"
Last-Modified: Fri, 14 Jan 2011 01:59:22 GMT
Content-Length: 40570
Connection: close
Content-Type: text/javascript
X-Pad: avoid browser bug

/*
   Class: FormCheck
       Performs different tests on forms and indicates errors.

   Usage:
       Works with these types of fields :
       - input (text, radio, checkbox)
       - textarea
       - select

       You just n
...[SNIP]...
<span>E.g. yourname@domain.com</span>
...[SNIP]...
re accepted.",
           digit : "Please enter a valid integer.",
           digitltd : "The value must be between %0 and %1",
           number : "Please enter a valid number.",
           email : "Please enter a valid email. eg., yourname@domain.com",
           image : 'This field should only contain image types',
           phone : "Please enter a valid phone number",
           phone_inter : "Please enter a valid international phone number.",
           url : "Please enter
...[SNIP]...

5.3. http://vivu.tv/vivuweb/js/common/mootools-1.2.4.4-more.js previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://vivu.tv
Path:	/vivuweb/js/common/mootools-1.2.4.4-more.js

Issue detail

The following email addresses were disclosed in the response:

erik@domain.com
espen@domene.no
fred@domain.com
fred@domaine.com
fred@domein.nl
jan@domena.pl
maria@bernasconi.ch
max@mustermann.de
name@domain.com
nome@dominio.com

Request

GET /vivuweb/js/common/mootools-1.2.4.4-more.js HTTP/1.1
Host: vivu.tv
Proxy-Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.187 Safari/535.1
Accept: */*
Referer: http://vivu.tv/vivuweb/
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: JSESSIONID=52C09E2038E3B5E245FAA55A8756D835.worker2; __utma=66968105.1713489603.1317519750.1317519750.1317519750.1; __utmb=66968105.1.10.1317519750; __utmc=66968105; __utmz=66968105.1317519750.1.1.utmcsr=aws.amazon.com|utmccn=(referral)|utmcmd=referral|utmcct=/officehours/

Response

HTTP/1.1 200 OK
Date: Sun, 02 Oct 2011 01:46:06 GMT
Server: Apache/2.2.9 (Fedora)
Accept-Ranges: bytes
ETag: W/"277183-1271670652000"
Last-Modified: Mon, 19 Apr 2010 09:50:52 GMT
Content-Length: 277183
Connection: close
Content-Type: text/javascript

//MooTools More, <http://mootools.net/more>. Copyright (c) 2006-2009 Aaron Newton <http://clientcide.com/>, Valerio Proietti <http://mad4milk.net> & the MooTools team <http://mootools.net/developers>,
...[SNIP]...
',
   dateSuchAs:'Please enter a valid date such as {date}',
   dateInFormatMDY:'Please enter a valid date such as MM/DD/YYYY (i.e. "12/31/1999")',
   email:'Please enter a valid email address. For example "fred@domain.com".',
   url:'Please enter a valid URL such as http://www.google.com.',
   currencyDollar:'Please enter a valid $ amount. For example $100.00 .',
   oneRequired:'Please enter something for at least one of the
...[SNIP]...
ta valida com {date}',
   dateInFormatMDY:'Per favor introdueix una data valida com DD/MM/YYYY (p.e. "31/12/1999")',
   email:'Per favor, introdueix una adre..a de correu electronic valida. Per exemple, "fred@domain.com".',
   url:'Per favor introdueix una URL valida com http://www.google.com.',
   currencyDollar:'Per favor introdueix una quantitat valida de .... Per exemple ...100,00 .',
   oneRequired:'Per favor introdue
...[SNIP]...
As:'Zadejte pros..m platn.. datum jako {date}',
   dateInFormatMDY:'Zadejte pros..m platn.. datum jako MM / DD / RRRR (tj. "12/31/1999")',
   email:'Zadejte pros..m platnou e-mailovou adresu. Nap....klad "fred@domain.com".',
   url:'Zadejte pros..m platnou URL adresu jako http://www.google.com.',
   currencyDollar:'Zadejte pros..m platnou ....stku. Nap....klad $100.00.',
   oneRequired:'Zadejte pros..m alespo.. jednu hodnot
...[SNIP]...
:'.......................................{date}...',
   dateInFormatMDY:'..........................................MM/DD/YYYY ("12/31/1999")...',
   email:'................................................"fred@domain.com"...',
   url:'.................. Url ..................http://www.google.com...',
   currencyDollar:'.............................................',
   oneRequired:'........................',
   errorPrefix:
...[SNIP]...
:'.......................................{date}...',
   dateInFormatMDY:'..........................................MM/DD/YYYY ("12/31/1999")...',
   email:'................................................"fred@domain.com"...',
   url:'.................. Url ..................http://www.google.com...',
   currencyYuan:'.............................................',
   oneRequired:'........................',
   errorPrefix: '.
...[SNIP]...
teSuchAs:'Vul een geldige datum in, zoals {date}',
   dateInFormatMDY:'Vul een geldige datum, in het formaat MM/DD/YYYY (bijvoorbeeld "12/31/1999")',
   email:'Vul een geldig e-mailadres in. Bijvoorbeeld "fred@domein.nl".',
   url:'Vul een geldige URL in, zoals http://www.google.nl.',
   currencyDollar:'Vul een geldig $ bedrag in. Bijvoorbeeld $100.00 .',
   oneRequired:'Vul iets in bij minimaal een van de invoervelden.',

...[SNIP]...
Palun sisestage kehtiv kuup..ev kujul {date}',
   dateInFormatMDY:'Palun sisestage kehtiv kuup..ev kujul MM.DD.YYYY (n..iteks: "12.31.1999").',
   email:'Palun sisestage kehtiv e-maili aadress (n..iteks: "fred@domain.com").',
   url:'Palun sisestage kehtiv URL (n..iteks: http://www.google.com).',
   currencyDollar:'Palun sisestage kehtiv $ summa (n..iteks: $100.00).',
   oneRequired:'Palun sisestage midagi v..hemalt ..hele
...[SNIP]...
quot;).',
   dateInFormatMDY: 'Geben Sie bitte ein gültiges Datum im Format TT.MM.JJJJ ein (z.B. "31.12.1999").',
   email: 'Geben Sie bitte eine gültige E-Mail-Adresse ein (z.B. "max@mustermann.de").',
   url: 'Geben Sie bitte eine gültige URL ein (z.B. "http://www.google.de").',
   currencyDollar: 'Geben Sie bitte einen gültigen Betrag in EURO ein (z.B. 100.00€).',

...[SNIP]...
ormatMDY:'Geben Sie bitte ein gültiges Datum ein. Wie zum Beispiel TT.MM.JJJJ (z.B. "31.12.1999")',
email:'Geben Sie bitte eine gültige E-Mail Adresse ein. Wie zum Beispiel "maria@bernasconi.ch".',
url:'Geben Sie bitte eine gültige URL ein. Wie zum Beispiel http://www.google.ch.',
currencyDollar:'Geben Sie bitte einen gültigen Betrag in Schweizer Franken ein. Wie zum Beisp
...[SNIP]...
ecte comme {date}',
dateInFormatMDY:'Veuillez saisir une date correcte, au format JJ/MM/AAAA (ex : "31/11/1999").',
email:'Veuillez saisir une adresse de courrier électronique. Par example "fred@domaine.com".',
url:'Veuillez saisir une URL, comme http://www.google.com.',
currencyDollar:'Veuillez saisir une quantité correcte. Par example 100,00€.',
oneRequired:'Veuillez sélectionn
...[SNIP]...
   dateSuchAs:'Inserire una data valida del tipo {date}',
   dateInFormatMDY:'Inserire una data valida nel formato MM/GG/AAAA (es.: "12/31/1999")',
   email:'Inserire un indirizzo email valido. Per esempio "nome@dominio.com".',
   url:'Inserire un indirizzo valido. Per esempio "http://www.dominio.com".',
   currencyDollar:'Inserire un importo valido. Per esempio "$100.00".',
   oneRequired:'Completare almeno uno dei campi rich
...[SNIP]...
ldig dato, som {date}',
dateInFormatMDY:'Vennligst skriv inn en gyldig dato, i formatet MM/DD/YYYY (for eksempel "12/31/1999")',
email:'Vennligst skriv inn en gyldig epost-adresse. For eksempel "espen@domene.no".',
url:'Vennligst skriv inn en gyldig URL, for eksempel http://www.google.no.',
currencyDollar:'Vennligst fyll ut et gyldig $ bel....p. For eksempel $100.00 .',
oneRequired:'Vennligst fyll u
...[SNIP]...
Prosimy poda.. prawid..ow.. dat.. w formacie: {date}',
   dateInFormatMDY:'Prosimy poda.. poprawn.. date w formacie DD.MM.RRRR (i.e. "12.01.2009")',
   email:'Prosimy poda.. prawid..owy adres e-mail, np. "jan@domena.pl".',
   url:'Prosimy poda.. prawid..owy adres URL, np. http://www.google.pl.',
   currencyDollar:'Prosimy poda.. prawid..ow.. sum.. w PLN. Dla przyk..adu: 100.00 PLN.',
   oneRequired:'Prosimy wype..ni.. cho
...[SNIP]...
idos.',
   dateSuchAs:'Digite uma data v..lida, como {date}',
   dateInFormatMDY:'Digite uma data v..lida, como DD/MM/YYYY (p.ex. "31/12/1999")',
   email:'Digite um endere..o de email v..lido. Por exemplo "fred@domain.com".',
   url:'Digite uma URL v..lida, como http://www.google.com.',
   currencyDollar:'Digite um valor v..lido $. Por exemplo $ 100,00. ',
   oneRequired:'Digite algo para pelo menos um desses insumos.',
   err
...[SNIP]...
ateSuchAs: 'Digite uma data v..lida, como {date}',
   dateInFormatMDY: 'Digite uma data v..lida, como DD/MM/YYYY (por exemplo, "31/12/1999")',
   email: 'Digite um endere..o de email v..lido. Por exemplo "nome@dominio.com".',
   url: 'Digite uma URL v..lida. Exemplo: http://www.google.com.',
   currencyDollar: 'Digite um valor em dinheiro v..lido. Exemplo: R$100,00 .',
   oneRequired: 'Digite algo para pelo menos um desses c
...[SNIP]...
........ ........ .. .............. ..../..../........ (................ "12/31/1999")',
   email:'...................., .............. .................... ..........-........... ...... .............. "fred@domain.com".',
   url:'...................., .............. .................... ............ ........ http://www.google.com.',
   currencyDollar:'...................., .............. .......... .. .................
...[SNIP]...
........ ........ .. .............. ..../..../........ (................ "12/31/1999")',
   email:'...................., .............. .................... ..........-........... ...... .............. "fred@domain.com".',
   url:'...................., .............. .................... ............ ........ http://www.google.com.',
   currencyDollar:'...................., .............. .......... .. .................
...[SNIP]...
mo {date}',
   dateInFormatMDY:'Por favor introduce una fecha válida como DD/MM/YYYY (p.e. "31/12/1999")',
   email:'Por favor, introduce una dirección de email válida. Por ejemplo, "fred@domain.com".',
   url:'Por favor introduce una URL válida como http://www.google.com.',
   currencyDollar:'Por favor introduce una cantidad válida de .... Por ejemplo ...100,00 .',
   oneRequired:'Por fa
...[SNIP]...
ll..tna.',
   dateSuchAs:'Ange ett giltigt datum som t.ex. {date}',
   dateInFormatMDY:'Ange ett giltigt datum som t.ex. YYYY-MM-DD (i.e. "1999-12-31")',
   email:'Ange en giltig e-postadress. Till exempel "erik@domain.com".',
   url:'Ange en giltig webbadress som http://www.google.com.',
   currencyDollar:'Ange en giltig belopp. Exempelvis 100,00.',
   oneRequired:'V..nligen ange minst ett av dessa alternativ.',
   errorPrefix
...[SNIP]...
......... ........ .. .............. ..../..../........ (.................. "12/31/2009").',
   email:'.............. ................ ............ ...................... .......... (.................. "name@domain.com").',
   url:'.............. ................ ................-.................. (.................. http://www.google.com).',
   currencyDollar:'.............. ........ .. .............. (...............
...[SNIP]...

5.4. http://vivu.tv/vivuweb/products/vucast/request/ previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://vivu.tv
Path:	/vivuweb/products/vucast/request/

Issue detail

The following email address was disclosed in the response:

sales@vivu.tv

Request

Response

6. Private IP addresses disclosed previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://vivu.tv
Path:	/crossdomain.xml

Issue detail

The following RFC 1918 IP address was disclosed in the response:

192.168.0.105

Issue background

RFC 1918 specifies ranges of IP addresses that are reserved for use in private networks and cannot be routed on the public Internet. Although various methods exist by which an attacker can determine the public IP addresses in use by an organisation, the private addresses used internally cannot usually be determined in the same ways.

Discovering the private addresses used within an organisation can help an attacker in carrying out network-layer attacks aiming to penetrate the organisation's internal infrastructure.

Issue remediation

There is not usually any good reason to disclose the internal IP addresses used within an organisation's infrastructure. If these are being returned in service banners or debug messages, then the relevant services should be configured to mask the private addresses. If they are being used to track back-end servers for load balancing purposes, then the addresses should be rewritten with innocuous identifiers from which an attacker cannot infer any useful information about the infrastructure.

Request

GET /crossdomain.xml HTTP/1.1
Host: vivu.tv
Proxy-Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.187 Safari/535.1
Accept: */*
Referer: http://cdn.vivu.tv/ViVuFlashWeb/desktop/Preloader1.1.3268.swf?unique=1.1.3268
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: __utma=66968105.1713489603.1317519750.1317519750.1317519750.1; __utmb=66968105.1.10.1317519750; __utmc=66968105; __utmz=66968105.1317519750.1.1.utmcsr=aws.amazon.com|utmccn=(referral)|utmcmd=referral|utmcct=/officehours/

Response

HTTP/1.1 200 OK
Date: Sun, 02 Oct 2011 01:41:49 GMT
Server: Apache/2.2.9 (Fedora)
Last-Modified: Wed, 16 Mar 2011 12:28:43 GMT
ETag: "c14f-2c4-49e98af78f4c0"
Accept-Ranges: bytes
Content-Length: 708
Connection: close
Content-Type: text/xml

<?xml version="1.0"?>
<!DOCTYPE cross-domain-policy
SYSTEM "http://www.macromedia.com/xml/dtds/cross-domain-policy.dtd">
<cross-domain-policy>
<allow-access-from domain="ec2-67-202-58-2.compu
...[SNIP]...
<allow-access-from domain="192.168.0.105"/>
...[SNIP]...

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

/vivuweb/fonts/MuseoSans/MuseoSans_700.otf
/vivuweb/js/common/mootools-1.2.4.4-more.js

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.

7.1. http://vivu.tv/vivuweb/fonts/MuseoSans/MuseoSans_700.otf previous next

Summary

Severity:	Information
Confidence:	Firm
Host:	http://vivu.tv
Path:	/vivuweb/fonts/MuseoSans/MuseoSans_700.otf

Issue detail

The response contains the following Content-type statement:

Content-Type: text/plain; charset=ISO-8859-1

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

Request

GET /vivuweb/fonts/MuseoSans/MuseoSans_700.otf HTTP/1.1
Host: vivu.tv
Proxy-Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.187 Safari/535.1
Accept: */*
Referer: http://vivu.tv/vivuweb/
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: JSESSIONID=52C09E2038E3B5E245FAA55A8756D835.worker2; __utma=66968105.1713489603.1317519750.1317519750.1317519750.1; __utmb=66968105.1.10.1317519750; __utmc=66968105; __utmz=66968105.1317519750.1.1.utmcsr=aws.amazon.com|utmccn=(referral)|utmcmd=referral|utmcct=/officehours/

Response

HTTP/1.1 200 OK
Date: Sun, 02 Oct 2011 01:46:07 GMT
Server: Apache/2.2.9 (Fedora)
Accept-Ranges: bytes
ETag: W/"63568-1309807464000"
Last-Modified: Mon, 04 Jul 2011 19:24:24 GMT
Content-Length: 63568
Connection: close
Content-Type: text/plain; charset=ISO-8859-1

OTTO.......0CFF r..i.. .....GPOSk..#......%.GSUB...\........OS/2.x.... ...`cmap.e.........4head..=........6hhea...........$hmtx.VS,...0... maxp..P.........name..$........4post...2....... .........!..
...[SNIP]...

7.2. http://vivu.tv/vivuweb/js/common/mootools-1.2.4.4-more.js previous

Summary

Severity:	Information
Confidence:	Firm
Host:	http://vivu.tv
Path:	/vivuweb/js/common/mootools-1.2.4.4-more.js

Issue detail

The response contains the following Content-type statement:

Content-Type: text/javascript

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

Request

Response

Report generated by XSS.CX at Sun Oct 02 18:17:47 CDT 2011.