Document Title:
===============
ATMAIL WebMail v6.3.4 - Multiple Web Vulnerabilities
References (Source):
====================
http://www.vulnerability-lab.com/get_content.php?id=375
Release Date:
=============
2012-01-06
Vulnerability Laboratory ID (VL-ID):
====================================
375
Product & Service Introduction:
===============================
Atmail is a commercial Linux messaging platform provider. The company was founded in 2001 and has its company headquarters located
in Peregian Beach, Australia. The company develops webmail, mail-server and groupware solutions built for Linux and other
Unix operating systems, and includes the source code under a commercial license.
Atmail provides 2 different web based application which are integrated on appliances or different software types.
The first service the the ATWebMail Application the second is the ATWebMail Admin Application.
(Copy of the Vendor Homepage: http://en.wikipedia.org/wiki/@Mail)
Abstract Advisory Information:
==============================
A Vulnerability-Lab researcher discovered multiple Web Vulnerabilities on the famous ATMAIL WebMail Application v6.3.4
Vulnerability Disclosure Timeline:
==================================
2012-01-06: Public or Non-Public Disclosure
Discovery Status:
=================
Published
Affected Product(s):
====================
ATMAIL
Product: WebMail 6.3.4.
Exploitation Technique:
=======================
Remote
Severity Level:
===============
Medium
Technical Details & Description:
================================
Multiple persistent input validation vulnerabilities are detected on the ATMAIl Web Application v6.3.4.
The vulnerability allows an remote attacker to inject persistent malicious script code. Successful exploitation
can results in persistent content manipulation, server-side session hijacking & module context manipulation.
Vulnerable Module(s):
[+] EMail -> Filter
[+] Calender -> Event Listing
Picture(s):
../1.png
../2.png
../3.png
Proof of Concept (PoC):
=======================
The vulnerabilities can be exploited by remote attacker with low required user inter action.
For demonstration or reproduce ...
Code Review: EMail -> Filter
<div id="event67398b25-59b7-491d-ab1a-1ca59ed259d8" class="eventListItem" style="width: 100%; height: 64px;">
<div class="checkboxHolder" style="top: 15px; left: 15px;">​​​​​<div class="checkboxBackground" style="background-color:
rgb(0, 2, 191);"></div><div class="checkboxFrame"></div></div><div class="eventListItemTitle">
>"<EXECUTION OF PERSISTENT SCRIPT CODE INJECT"></div><div class="eventListItemTime"></div><div class=
"eventListItemDate">Thursday 5th January 2012</div></div></iframe></div>​​​​​</div><div id="
event67398b25-59b7-491d-ab1a-1ca59ed259d8" class="eventListItem" style="width: 100%; height: 64px;"><div class="checkboxHolder"
style="top: 15px; left: 15px;">​​​​​<div class="checkboxBackground" style="background-color: rgb(0, 2, 191);"></div><div
class="checkboxFrame"></div>
</div><div class="eventListItemTitle">>"<iframe src="http://vulnerability-lab.com"></div><div class="eventListItemTime"></div>
<div class="eventListItemDate">Thursday 5th January 2012</div></div>
</iframe></div>​​​​​</div>
Code Review: Calender -> Event Listing
<tr class="divide">
<td class="td1">
<input style="margin-left: 8px; vertical-align: middle;" id="filterSelectedCheckbox" value=""
name="filtersId[]" type="checkbox">
</td>
<td class="td2">
<strong>from</strong> is ``><PERSISTENT SCRIPT CODE INJECTION!")'
<@mydomain.com"="" and=""
<strong="">from</strong> is ""
filters to <strong>Examples</strong>
</td>
<td class="td3">
<a class="filterDelete" href="#">Delete</a>
/<a class="filterModify" href="#">Modify</a>
</td>
</tr>
Reference(s):
../poc-calender-prv8.txt
../poc-filter.txt
Security Risk:
==============
The security risk of the persistent web vulnerabilities are estimated as medium(+).
Credits & Authors:
==================
Vulnerability Research Laboratory - Benjamin Kunz Mejri (Rem0ve) & Ucha Gobejishvili (longrifle0x)
Disclaimer & Information:
=========================
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 © 2012 | Vulnerability Laboratory