The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers). An example of a network attack is an attacker causing a denial of service by sending a specially crafted TCP packet across a wide area network (e.g., CVE-2004-0230).
Attack Complexity
Low
AC
The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Privileges Required
None
PR
The attacker is unauthenticated prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction
None
UI
The vulnerable system can be exploited without interaction from any human user, other than the attacker. Examples include: a remote attacker is able to send packets to a target system a locally authenticated attacker executes code to elevate privileges
Scope
Unchanged
S
An exploited vulnerability can only affect resources managed by the same security authority. In the case of a vulnerability in a virtualized environment, an exploited vulnerability in one guest instance would not affect neighboring guest instances.
Confidentiality
Low
C
There is some impact on confidentiality, but the attacker either does not gain control of any data, or the information obtained does not have a significant impact on the system or its operations.
Integrity
Low
I
Modification of data is possible, but the attacker does not have control over what can be modified, or the extent of what the attacker can affect is limited. The data modified does not have a direct, serious impact on the system.
Availability
None
A
There is no impact on the availability of the system; the attacker does not have the ability to disrupt access to or use of the system.
Title:
======
Barracuda Control Center 620 - Multiple Web Vulnerabilities
Date:
=====
2011-12-21
References:
===========
http://www.vulnerability-lab.com/get_content.php?id=32
VL-ID:
=====
32
Introduction:
=============
Barracuda Networks - Worldwide leader in email and Web security.
Control Center Application of Barracuda Networks
(Copy of the Vendor Homepage: http://www.barracudanetworks.com/ns/products/)
Abstract:
=========
Vulnerability-lab Team discovered multiple Web Vulnerabilities on Barracuda Control Center 620 appliance/application.
Report-Timeline:
================
2011-06-03:Vendor Notification
2011-07-12:Vendor Response/Feedback
2011-11-26:Vendor Fix/Patch
2011-12-21:Public or Non-Public Disclosure
Status:
========
Published
Affected Products:
==================
Exploitation-Technique:
=======================
Remote
Severity:
=========
Medium
Details:
========
1.1
Multiple persistent Input Validation vulnerabilities are detected on Barracudas Control Center 620. Local low privileged user account can
implement/inject malicious persistent script code. When exploited by an authenticated user, the identified vulnerabilities
can lead to information disclosure, access to intranet available servers, manipulated persistent content.
Vulnerable Module(s): (Persistent)
[+] authdblookup -input
1.2
Multiple non-persistent Input Validation vulnerabilities are detected on Barracudas Control Center 620 appliance.
Attackers can form malicious client-side requests to hijack customer/admin sessions.
Successful exploitation requires user inter action & can lead to information disclosure, session
hijacking and access to servers in the intranet.
Vulnerable Module(s): (Non-Persistent)
[+] editdevices
[+] main
Picture(s):
../control1.png
../control2.png
../control3.png
Proof of Concept:
=================
The vulnerabilities can be exploited by low privileged user accounts or remote attacker via high required user inter action.
For demonstration or reproduce ...
1.1 Persistent
https://127.0.0.1:8080/bcc/[email protected]&selected-node=
Manually reproduce ...
1. Login
2. Switch to the vulnerable authdblookup-input.jsp add mask
3. Include your own malicious persistent script code (java-script or html) & save the input
4. The stored script code will be executed in main-bar as stable output result (persistent)
1.2 Non-Persistent
https://127.0.0.1:8080/bcc/editdevices.jsp?device-type=spyware&selected-node=1&containerid=[IVE]
https://127.0.0.1:8080/bcc/main.jsp?device-type=[IVE]
Solution:
=========
Barracuda implemented after the issues 2011 a validation mask to filter malicious & disallowed inputs.
The barracuda firmware of the filter has been update multiple times.
Risk:
=====
1.1
The security risk of the discovered persistent vulnerabilities are estimated as medium(+) because of low required user inter action.
1.2
The security risk of the discovered non-persistent vulnerabilities are estimated as low because of high required user inter action.
Credits:
========
Vulnerability Research Laboratory - Pim J.F. Campers (X4lt)
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. Any modified copy or reproduction, including partially usages, of this file requires authorization from Vulnerability-
Lab. 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 or its suppliers.
Copyright 2011|Vulnerability-Lab
This information is provided for TESTING and LEGAL RESEARCH purposes only. All trademarks used are properties of their respective owners. By visiting this website you agree to Terms of Use and Privacy Policy and Impressum