121 lines
No EOL
4.7 KiB
Text
Executable file
121 lines
No EOL
4.7 KiB
Text
Executable file
Title:
|
||
======
|
||
Inout Mobile Webmail APP - Multiple Web Vulnerabilities
|
||
|
||
|
||
Date:
|
||
=====
|
||
2012-06-08
|
||
|
||
|
||
References:
|
||
===========
|
||
http://www.vulnerability-lab.com/get_content.php?id=609
|
||
|
||
|
||
VL-ID:
|
||
=====
|
||
609
|
||
|
||
|
||
Common Vulnerability Scoring System:
|
||
====================================
|
||
3.5
|
||
|
||
|
||
Abstract:
|
||
=========
|
||
The Vulnerability Laboratory Research Team discovered multiple web vulnerabilities in the inoutscripts mobile Inoutmail Webmail CMS 2012.
|
||
|
||
|
||
Report-Timeline:
|
||
================
|
||
2012-06-08: Public or Non-Public Disclosure
|
||
|
||
|
||
Status:
|
||
========
|
||
Published
|
||
|
||
|
||
Exploitation-Technique:
|
||
=======================
|
||
Remote
|
||
|
||
|
||
Severity:
|
||
=========
|
||
Medium
|
||
|
||
|
||
Details:
|
||
========
|
||
Multiple persistent input validation vulnerabilities are detected in the inoutscripts mobile Inoutmail CMS 2012.
|
||
The bugs allow remote attackers to implement/inject malicious script code on the application side (persistent).
|
||
Successful exploitation of the vulnerability can lead to session hijacking (manager/admin) or stable (persistent)
|
||
context manipulation. Exploitation requires low user inter action & privileged user account. The persistent valiation
|
||
vulnerabilities are located in the new mail & contacts modules with the bound values to, bcc, cc. The bug can be
|
||
exploited by remote attackers. The attacker is sending a malicious mail with vulnerable script code values as content.
|
||
The admin or customer is watching the arriving mail and the persistent script code in To or Bcc inputs. The context will
|
||
be executed (persistent) when the user,customer or admin is processing to check his mails. A privileged user account can
|
||
also use the bug to save it persistent for higher privileged user account exploitation.
|
||
|
||
Vulnerable Module(s):
|
||
[+] New Mail
|
||
[+] Contacts
|
||
|
||
Vulnerable Parameter(s):
|
||
[+] To
|
||
[+] Cc
|
||
[+] Bcc
|
||
|
||
|
||
Proof of Concept:
|
||
=================
|
||
The persistent vulnerabilities can be exploited by remote attackers with low required user inter action. For demonstration or reproduce ...
|
||
|
||
Insert the demonstration string to the Bcc, Cc & To of the send new mail.
|
||
Secound possibility is to send a mail from outside to the inout webmail with the string code values.
|
||
|
||
PoC:
|
||
>>"<iframe src=http://vuln-lab.com onload=alert("VL") <
|
||
|
||
|
||
Risk:
|
||
=====
|
||
The security risk of the persistent input validation vulnerabilities are estimated as medium(+).
|
||
|
||
|
||
Credits:
|
||
========
|
||
Vulnerability Laboratory [Research Team] - snup (snup@vulnerability-lab.com [http://snup1.blogspot.com]
|
||
|
||
|
||
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@vulnerability-lab.com - support@vulnerability-lab.com - research@vulnerability-lab.com
|
||
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@vulnerability-lab.com or support@vulnerability-lab.com) to get a permission.
|
||
|
||
Copyright <20> 2012 | Vulnerability Laboratory
|
||
|
||
--
|
||
VULNERABILITY RESEARCH LABORATORY
|
||
LABORATORY RESEARCH TEAM
|
||
CONTACT: research@vulnerability-lab.com |