Title:

Barracuda CudaTel 2.6.02.04 - Multiple Client Side Cross Site Vulnerabilities (Bug Bounty #17)

Date:

2013-07-17

References:

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

BARRACUDA NETWORK SECURITY ID: BNSEC-815

VL-ID:

779

Common Vulnerability Scoring System:

2.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.cudatel.com )

Abstract:

The Vulnerability Laboratory Research Team discovered multiple client side web vulnerabilities in Barracuda Networks CudaTel v2.6.002.040 appliance application.

Report-Timeline:

2012-11-26: Researcher Notification & Coordination (Benjamin Kunz Mejri)
2012-11-29: Vendor Notification (Barracuda Networks Security Team - Bug Bounty Program)
2012-12-01: Vendor Response/Feedback (Barracuda Networks Security Team)
2013-04-07: Vendor Fix/Patch (Barracuda Networks Developer Team) [Manager: Dave Farrow]
2012-07-17: Public Disclosure (Vulnerability Laboratory)

Status:

Published

Affected Products:

Barracuda Networks
Product: CudaTel - Communication Server 2.6.002.040

Exploitation-Technique:

Remote

Severity:

Medium

Details:

Multiple client side input validation vulnerabilities are detected in Barracuda Networks CudaTel v2.6.002.040 appliance application.
The non-persistent vulnerabilities allows an attacker (remote) to manipulate client side application to browser requests.

The first vulnerability (client side) is located in the gui route module when processing to request the vulnerable
bbx_outbound_route_name parameter & affected listing. The route module allows remote attackers via bbx_outbound_route_flag_locked
parameter to request and execute script codes in the bbx_outbound_route_name listing.

The secound vulnerability (client side) is located in the ajax - html module when processing to request the vulnerable
queues_wall_stub file and the ops opOpenQueueWallboard link parameters. The vulnerability allows remote attackers (client side)
to change the link of the Queue Monitor Board on requests to redirect.

The third vulnerability (client side) is located in the Web login attempt fail exception-handling of eventlog module when
processing to load the manipulated bbx_eventlog_message parameter. The vulnerability allows remote attackers to execute own
script code (client side) in the queues_wall_stub.html file from the exception-handling location for Web login attempt fails.

Exploitation of the vulnerability requires a low privilege application user account and medium or high user interaction.
Successful exploitation of the vulnerabilities result in client side phishing, client side session hijacking, client side
external redirects to malware or evil websites and client side module context manipulation.

Vulnerable Section(s):
[+] GUI - ROUTE
[+] AJAX - HTML
[+] Eventlog

Vulnerable Module(s):
[+] route - Listing
[+] queues_wall_stub - Monitor Queue Link
[+] eventlog - Web login attempt fail (Exception Handling) - Listing

Vulnerable Parameter(s):
[+] bbx_outbound_route_flag_locked > bbx_outbound_route_name
[+] ops opOpenQueueWallboard
[+] bbx_eventlog_message

Proof of Concept:

The client side input validation vulnerabilities can be exploited by remote attackers without required application user account and with
medium or high required user interaction. For demonstration or reproduce …

1.1
Review: GUI - ROUTE > route - Listing > bbx_outbound_route_flag_locked [PARAMETER]> bbx_outbound_route_name [LISTING]

bbx_domain_id: 6
bbx_outbound_route_flag_locked: 0
bbx_outbound_route_id: 14
bbx_outbound_route_name: [CLIENT-SIDE SCRIPT CODE!]
bbx_outbound_route_regex: "^\\d{10}$"
bbx_outbound_route_type: national
</pre></body></html></iframe>​​​​​</pre>

PoC:
http://cudatel.127.0.0.1:1338/gui/route/route?&#37;3C[CLIENT-SIDE SCRIPT CODE!]%20%3C
http://cudatel.127.0.0.1:1338/gui/route/route?_=1354073910062&amp;bbx_outbound_route_flag_locked=&#37;3C[CLIENT-SIDE SCRIPT CODE!]%20%3C

1.2
Review: AJAX - HTML > queues_wall_stub - Monitor Queue Link > ops opOpenQueueWallboard

<h3>Queue Monitor <a class="ops opOpenQueueWallboard" href="#">Large View in New Window</a></h3>

PoC:
http://cudatel.127.0.0.1:1338/ajax-html/queues_wall_stub.html?_=1354074247075&#37;20&#37;3C[CLIENT-SIDE SCRIPT CODE!]%20%3C#

1.3
Review: Eventlog > eventlog - Web login attempt fail (Exception Handling) - Listing > bbx_eventlog_message

bbx_eventlog_date_time: 2012-11-26 15:25:59
bbx_eventlog_email_sent: 0
bbx_eventlog_fullname: Admin
bbx_eventlog_id: 2823
bbx_eventlog_ip_addr: 178.200.236.201
bbx_eventlog_message: Web login attempt fail for <[x]>%20%20split%20%20"><[CLIENT-SIDE SCRIPT CODE!]") < from 178.200.236.201
bbx_eventlog_priority: notice
bbx_eventlog_user_agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Firefox/17.0
bbx_user_id: 1

PoC:
http://cudatel.127.0.0.1:1338/gui/eventlog/eventlog?&#37;3Cx&#37;3E&#37;20&#37;20&#37;20&#37;20&#37;22&#37;3E&#37;3C[CLIENT-SIDE SCRIPT CODE!]%20%3C

Reference(s):
http://cudatel.ptest.cudasvc.com/gui/route/route
http://cudatel.ptest.cudasvc.com/ajax-html/queues_wall_stub.html
http://cudatel.ptest.cudasvc.com/gui/eventlog/eventlog

Risk:

The security risk of the (multiple) client side input validation vulnerabilities are estimated as medium.

Credits:

Vulnerability Laboratory [Research Team] - Benjamin Kunz Mejri ([email protected])

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.evolution-sec.com
Contact: [email protected] - [email protected] - [email protected]
Section: www.vulnerability-lab.com/dev - forum.vulnerability-db.com - magazine.vulnerability-db.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 ([email protected] or [email protected]) to get a permission.

			Copyright © 2013 | Vulnerability Laboratory [Evolution Security]

– VULNERABILITY LABORATORY RESEARCH TEAM DOMAIN: www.vulnerability-lab.com CONTACT: [email protected]