Home page logo
/

bugtraq logo Bugtraq mailing list archives

Barracuda CudaTel 2.6.02.04 - Persistent Web Vulnerability
From: Vulnerability Lab <research () vulnerability-lab com>
Date: Fri, 28 Jun 2013 00:47:46 +0100

Title:
======
Barracuda CudaTel 2.6.02.04 - Persistent Web Vulnerability


Date:
=====
2013-06-21


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

BARRACUDA NETWORK SECURITY ID: BNSEC-834


VL-ID:
=====
777


Common Vulnerability Scoring System:
====================================
3.5


Introduction:
=============
Designed to enable seamless voice and video communication, the CudaTel Communication Server is an easy-to-use, 
affordable, next-generation phone system for businesses. CudaTel Communication Server s enterprise-class 
feature set includes Voice over IP (VoIP) PBX services, conferencing, follow-me, automated attendant services, 
and more, controlled by an easy-to-use Web interface. CudaTel Communication Server is compatible with any SIP 
device and provider, and can be pre-configured for use with both analog and digital telephone networks. Powerful, 
Complete Solution With an expansive feature set and and no per user or phone licensing fees, the CudaTel 
Communication Server is equipped and priced for organizations of any size. Native High Definition audio support 
and integrated phone line (TDM) hardware produces an unparalleled audio experience. VOIP encryption protects calls 
from hackers and digital eavesdroppers.

(Copy of the Vendor Homepage: http://www.barracudanetworks.ca/cudatel.aspx )


Abstract:
=========
The Vulnerability Laboratory Research Team discovered a client side web vulnerability in Barracuda Networks CudaTel 
v2.6.002.040 appliance application.


Report-Timeline:
================
2012-11-26:     Researcher Notification & Coordination (Chokri Ben Achour)
2012-11-27:     Vendor Notification (Barracuda Networks Security Team - Bug Bounty Program)
2013-04-03:     Vendor Response/Feedback (Barracuda Networks Security Team - Bug Bounty Program)
2013-05-02:     Vendor Fix/Patch (Barracuda Networks Developer Team) [Coordination: Dave Farrow]
2012-06-00:     Public Disclosure (Vulnerability Laboratory)


Status:
========
Published


Affected Products:
==================
Barracuda Networks
Product: CudaTel - Communication Server 2.6.002.040


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


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


Details:
========
The vulnerability laboratory research team discovered a persistent web vulnerability  in Barracuda Networks CudaTel 
v2.6.002.040 appliance application.
The input validation vulnerability allows remote attackers to inject own malicious persistent script code on 
application side of the vulnerable module.

The vulnerability is located in the `find me` module of the `call forwarding` function when processing to request 
manipulated parameters via `add listing`.
Local low privilege application user accounts can inject persistent script code to exploit higher privilege web 
application accounts. 

The remote bug can be exploited by remote attacker with low privileged application user account and low required 
userinteraction. Successful exploitation 
of the vulnerabilities result in persistent session hijacking, persistent persistent external redirects to malware or 
malicious sites, persistent phishing 
and persistent web context manipulation (vulnerable module).

Vulnerable Section(s):
                                [+] Find Me

Vulnerable Module(s):
                                [+] Call Forwarding - Add

Vulnerable Parameter(s):
                                [+] Calling Sequence - Listing


Proof of Concept:
=================





Solution:
=========
The vulnerability can be patched  by parsing the listed (output) web context after processing to add.
restrict also the input fields and disallow special chars or wrong strings.

2013-05-02:     Vendor Fix/Patch (Barracuda Networks Developer Team) [Coordination: Dave Farrow]


Risk:
=====
The security risk of the persistent input validation vulnerability is estimated as medium.


Credits:
========
Vulnerability Laboratory [Research Team] - Chokri Ben Achour (meister () vulnerability-lab 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, source code, 
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 © 2013 | Vulnerability Laboratory



-- 
VULNERABILITY LABORATORY RESEARCH TEAM
DOMAIN: www.vulnerability-lab.com
CONTACT: research () vulnerability-lab com



  By Date           By Thread  

Current thread:
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]