[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Full-disclosure] VMware Vendor Service - Multiple Web Vulnerabilities



Title:
======
VMware Vendor Service - Multiple Web Vulnerabilities


Date:
=====
2012-05-16


References:
===========
http://www.vulnerability-lab.com/get_content.php?id=419


VL-ID:
=====
419


Common Vulnerability Scoring System:
====================================
5.2


Introduction:
=============
VMware, Inc. (NYSE: VMW) is a company providing virtualization software, 
founded in 1998 and based in Palo Alto, 
California, USA. The company was acquired by EMC Corporation in 2004, and 
operates as a separate software subsidiary.
VMware s desktop software runs on Microsoft Windows, Linux, and Mac OS X, while 
VMware s enterprise software hypervisors 
for servers, VMware ESX and VMware ESXi, are bare-metal embedded hypervisors 
that run directly on server hardware without 
requiring an additional underlying operating system.

(Copy of the Vendor Homepage: http://en.wikipedia.org/wiki/VMware)


Abstract:
=========
A Vulnerability Lab Researcher discovered multiple persistent web 
vulnerabilities on the VMware vendor website service application.


Report-Timeline:
================
2012-05-03:     Vendor Notification
2012-05-03:     Vendor Response/Feedback
2012-05-14:     Vendor Fix/Patch 
2012-05-16:     Public or Non-Public Disclosure


Status:
========
Published


Exploitation-Technique:
=======================
Remote


Severity:
=========
High


Details:
========
Multiple persistent input validation vulnerabilities are detected on the VMware 
vendor website service application. 
The vulnerability allows an remote attacker to hijack customer sessions with 
low required user inter action. 
The vulnerability is located in the username and profil input fields and the 
output display listings.
Successful exploitation can result in account steal or execution of malicious 
persistent context.

Vulnerable Module(s):
                                                [+] Profil

Vulnerable Parameter(s):
                                                [+] Username, Welcome & Title

Proof of Concept:
=================
The vulnerabilities can be exploited by remote attackers with low required user 
inter action.
For demonstration or reproduce ...

1.1

<div id="header" class="proServices">
<h1>Support Contracts & Incidents</h1>
<ul id="navSession" class="navSession">
<li>Welcome,"><[SCRIPT CODE 
EXECUTION!]></li></ul></div></div></div></div></body></html>


1.2
<link type="text/css" rel="StyleSheet" 
href="productRegistration.do_files/accountserialskin.css">
<ul class="navSession" id="navSession">
<li>      
Welcome ">>"<[SCRIPT CODE EXECUTION!]>
</li></ul></div></div></div></body></html>


Reference(s):
                        ../contracts.portal.html
                        ../productRegistration.do


Also affected:
                        
https://www.vmware.com/mysupport/order.portal?vmware=searchOrders&qn=0


Solution:
=========
To fix the vulnerability parse the input field when processing to save profile 
content.
Sanitize the output listing of the user profile and title were the context is 
getting executed.
Restrict the input field also with a char mask or secure filter as 
exception-handling.


Risk:
=====
The security risk of the persistent input validation vulnerabilities are 
estimated as high(-).


Credits:
========
Vulnerability Laboratory [Research Team] -    Benjamion Kunz Mejri 
(bkm@xxxxxxxxxxxxxxxxxxxxx)


Disclaimer:
===========
The information provided in this advisory is provided as it is without any 
warranty. Vulnerability-Lab disclaims all warranties, 
either expressed or implied, including the warranties of merchantability and 
capability for a particular purpose. Vulnerability-
Lab or its suppliers are not liable in any case of damage, including direct, 
indirect, incidental, consequential loss of business 
profits or special damages, even if Vulnerability-Lab or its suppliers have 
been advised of the possibility of such damages. Some 
states do not allow the exclusion or limitation of liability for consequential 
or incidental damages so the foregoing limitation 
may not apply. We do not approve or encourage anybody to break any vendor 
licenses, policies, deface websites, hack into databases 
or trade with fraud/stolen material.

Domains:    www.vulnerability-lab.com           - www.vuln-lab.com              
               - www.vulnerability-lab.com/register
Contact:    admin@xxxxxxxxxxxxxxxxxxxxx         - support@xxxxxxxxxxxxxxxxxxxxx 
               - research@xxxxxxxxxxxxxxxxxxxxx
Section:    video.vulnerability-lab.com         - forum.vulnerability-lab.com   
               - news.vulnerability-lab.com
Social:     twitter.com/#!/vuln_lab             - facebook.com/VulnerabilityLab 
               - youtube.com/user/vulnerability0lab
Feeds:      vulnerability-lab.com/rss/rss.php   - 
vulnerability-lab.com/rss/rss_upcoming.php   - 
vulnerability-lab.com/rss/rss_news.php

Any modified copy or reproduction, including partially usages, of this file 
requires authorization from Vulnerability Laboratory. 
Permission to electronically redistribute this alert in its unmodified form is 
granted. All other rights, including the use of other 
media, are reserved by Vulnerability-Lab Research Team or its suppliers. All 
pictures, texts, advisories, sourcecode, videos and 
other information on this website is trademark of vulnerability-lab team & the 
specific authors or managers. To record, list (feed), 
modify, use or edit our material contact (admin@xxxxxxxxxxxxxxxxxxxxx or 
support@xxxxxxxxxxxxxxxxxxxxx) to get a permission.

                                        Copyright © 2012 | Vulnerability 
Laboratory



-- 
VULNERABILITY RESEARCH LABORATORY
LABORATORY RESEARCH TEAM
CONTACT: research@xxxxxxxxxxxxxxxxxxxxx


_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/