exploit the possibilities
Home Files News &[SERVICES_TAB]About Contact Add New

Barracuda Firewall Exception Handling Cross Site Scripting

Barracuda Firewall Exception Handling Cross Site Scripting
Posted Feb 22, 2014
Authored by Benjamin Kunz Mejri, Vulnerability Laboratory | Site vulnerability-lab.com

Barracuda Firewall suffers from a cross site scripting vulnerability in the exception handling functionality.

tags | exploit, xss
SHA-256 | dc40815561f66aa5a2bb21a7ca2b1f03cd6c36a9519c40953253af410f5f16d2

Barracuda Firewall Exception Handling Cross Site Scripting

Change Mirror Download
Document Title:
===============
Barracuda Bug Bounty #36 Firewall - Client Side Exception Handling Web Vulnerability



References (Source):
====================
http://www.vulnerability-lab.com/get_content.php?id=1102

Barracuda Networks Security ID (BNSEC): BNSEC-2398

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

View Video: http://www.youtube.com/watch?v=-cTO7ork6Hg


Release Date:
=============
2014-02-20


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


Common Vulnerability Scoring System:
====================================
5.7


Product & Service Introduction:
===============================
The Barracuda Firewall goes beyond traditional network firewalls and UTMs by providing powerful network security,
granular layer 7 application controls, user awareness and secure VPN connectivity combined with cloud-based malware
protection, content filtering and reporting. It alleviates the performance bottlenecks in Unified Threat Management
(UTM) appliances through intelligent integration of on-premise and cloud-based technologies. While the powerful on-
premises appliance is optimized for tasks like packet forwarding and routing, Intrusion Prevention (IPS), DNS/DHCP
services and site-to-site connectivity; CPU intensive tasks like virus scanning, content filtering and usage
reporting benefit from the scalable performance and elasticity of the cloud.

(Copy o the Vendor Homepage: https://www.barracuda.com/products/firewall )


Abstract Advisory Information:
==============================
The Vulnerability Laboratory Team discovered a filter bypass and a persistent vulnerability in Barracuda Networks Firewall Appliance v6.1.0.016 Application.


Vulnerability Disclosure Timeline:
==================================
2013-09-26: Researcher Notification & Coordination (Benjamin Kunz Mejri)
2013-09-28: Vendor Notification (Barracuda Networks Security Team - Bug Bounty Program)
2013-10-06: Vendor Response/Feedback (Barracuda Networks Security Team - Bug Bounty Program)
2014-02-17: Vendor Fix/Patch (Barracuda Networks Developer Team) [Coordination: Dave Farrow]
2014-02-20: Public Disclosure (Vulnerability Laboratory)


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


Affected Product(s):
====================
Barracuda Networks
Product: Firewall Appliance Web-Application 6.1.0.016 - x100 x200 x300 x400 x500 x600 & Vx


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


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


Technical Details & Description:
================================
A input validation web vulnerability is detected in the official Barracuda Networks Firewall Appliance Web-Application.
The vulnerability allows an attacker (remote) to implement/inject own malicious persistent script codes (application side).

The vulnerability is located in the `VPN > Certificates` module when processing to request via POST to GET method manipulated
`cert_error` parameters in the secure application exception-handling. The code will be directly executed in the main header
on top inside of the error message. The issue impact a persistent and a non-persistent issue.

The attacker goes to the certificates area and uploads even in the restricted mode 2 pem certs, he tampers the request and
exchange the upload path and drops also a invalid value to the name. The application will respond with a GET and drop a unknown
error message in the exception-handling of the module. The attacker is changing the referer and includes his own code in the
client-side affected parameter. Now the links in the main website will change to the error link persistent. The attacker is now
able to easily click the link or request the url to execute the code inside of the exception-handling contents`>Error message.

Exploitation of the persistent web vulnerability requires low user interaction and a local low privileged web-application account.
Successful exploitation of the vulnerability can lead to persistent session hijacking (customers), account steal via persistent web
attacks, persistent phishing or persistent manipulation of module context.


Vulnerable Module(s):
[+] VPN > Certificates

Vulnerable Parameter(s):
[+] cert_error (contents:error)

Affected Module(s):
[+] Exception-Handling - Error Message


Proof of Concept (PoC):
=======================
The input validation vulnerability in the exception-handling can be exploited by remote attackers with low privileged web-application user account
and low user interaction. For security demonstration or to reproduce the vulnerability follow the provided steps and information below to continue.

1. You need to request the regular module ...
https://firewall.localhost:8080/cgi-bin/index.cgi?&et=1380384291&locale=en_US&encrypt_password=&user=guest&primary_tab=VPN&secondary_tab=certificates&

2. Provoke an error inside of the regular protected exception-handling via upload pem:
https://firewall.localhost:8080/cgi-bin/index.cgi?&et=1380384291&locale=en_US&encrypt_password=&user=guest&primary_tab=VPN&secondary_tab=certificates&cert_error=Unknown%20operation#key0

3. After the redirect with the url to the error happened the attacker is able to change the exception input variable to execute own codes
https://firewall.localhost:8080/cgi-bin/index.cgi?&et=1380384291&locale=en_US&encrypt_password=&user=guest&primary_tab=VPN&secondary_tab=certificates&cert_error=%3E%22%3Ciframe%20src=b%3E



PoC: Exception Handling - Error Message

<tr><td><table id="status_screen" class="status_screen"><tbody><tr><td><center><table class="status_module"
cellpadding="0" cellspacing="0"><tbody><tr><td><div id="error"><b class="outlinetop"><b class="outline1"></b>
<b class="outline2"></b><b class="outline3"></b><b class="outline4"></b></b><div
id="contents">Error: >"<[MALICIOUS INJECTED SCRIPT CODE!])"><<br>
</div><b class="outlinebottom"><b class="outline4"></b><b class="outline3"></b><b class="outline2"></b>
<b class="outline1"></b></b></div></td></tr></table></center></td></tr></table></td></tr><tr style="background-color:#D9F5FF;">
<td class="config_screen" valign="top" height="400" width="100%" ><table summary="Body" border="0" width="100%" ><tr ><td>
<table width=100% height=100% style="padding:2px" ><tr><td height=100%>
<table cellspacing=0 cellpadding=0 class=outlined>
<tr>
<td class='tl'></td>
<td class='tm'></td>
<td class='tr'></td>
</tr>


Reference(s):
../Barracuda Firewall Certificates - provoke unknown exception.htm
../Barracuda Firewall Certificates.htm
../dom1.txt
../poc.txt
../poc-session-log.txt

Picture(s):
../1.png
../2.png
../3.png


Solution - Fix & Patch:
=======================
The remote web vulnerability can be patched by a secure parse of the error message context inside of the firewall certificate error exception-handling.


Security Risk:
==============
The security risk of the validation web vulnerability is estimated as medium to high because of the location in the secure application exception-handling.


Credits & Authors:
==================
Vulnerability Laboratory [Research Team] - Benjamin Kunz Mejri (bkm@evolution-sec.com) [www.vulnerability-lab.com]


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.evolution-sec.com
Contact: admin@vulnerability-lab.com - research@vulnerability-lab.com - admin@evolution-sec.com
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 (admin@vulnerability-lab.com or research@vulnerability-lab.com) to get a permission.

Copyright © 2014 | Vulnerability Laboratory [Evolution Security]



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

Login or Register to add favorites

File Archive:

May 2024

  • Su
  • Mo
  • Tu
  • We
  • Th
  • Fr
  • Sa
  • 1
    May 1st
    44 Files
  • 2
    May 2nd
    5 Files
  • 3
    May 3rd
    11 Files
  • 4
    May 4th
    0 Files
  • 5
    May 5th
    0 Files
  • 6
    May 6th
    28 Files
  • 7
    May 7th
    3 Files
  • 8
    May 8th
    4 Files
  • 9
    May 9th
    54 Files
  • 10
    May 10th
    12 Files
  • 11
    May 11th
    0 Files
  • 12
    May 12th
    0 Files
  • 13
    May 13th
    18 Files
  • 14
    May 14th
    11 Files
  • 15
    May 15th
    17 Files
  • 16
    May 16th
    13 Files
  • 17
    May 17th
    22 Files
  • 18
    May 18th
    0 Files
  • 19
    May 19th
    0 Files
  • 20
    May 20th
    17 Files
  • 21
    May 21st
    18 Files
  • 22
    May 22nd
    7 Files
  • 23
    May 23rd
    111 Files
  • 24
    May 24th
    27 Files
  • 25
    May 25th
    0 Files
  • 26
    May 26th
    0 Files
  • 27
    May 27th
    6 Files
  • 28
    May 28th
    12 Files
  • 29
    May 29th
    31 Files
  • 30
    May 30th
    0 Files
  • 31
    May 31st
    0 Files

Top Authors In Last 30 Days

File Tags

Systems

packet storm

© 2022 Packet Storm. All rights reserved.

Services
Security Services
Hosting By
Rokasec
close