Back to list
IRM Security Advisory : Barracuda Networks Spam Firewall Cross-Site Scripting Vulnerability
May 22 2008 04:14PM
Mark Crowther (mark crowther irmplc com)
Barracuda Networks Spam Firewall Cross-Site Scripting Vulnerability
CVE Number: CVE-2008-2333
Vulnerability Type / Importance: Cross-Site Scripting (Reflected) /
Problem Discovered 24 April 2008
Vendor Contacted 24 April 2008
Advisory Published 22 May 2008
The Barracuda Spam Firewall device web administration interface is
vulnerable to a reflected cross-site scripting vulnerability which may
allow theft of administrative credentials or downloading of malicious
The Barracuda device presents LDAP testing functionality via a script
called 'ldap_test.cgi'. The script does not sufficiently validate
user-supplied input within the 'email' parameter. As a result,
client-supplied script code can be injected into the 'email' parameter
that would execute in the browser within the security context of the
Proof of Concept:
Access to the web management application can be limited by IP address.
Firmware release 3.5.11.025 has been released by the vendor to address
this issue; however the patch has not been tested by IRM.
IRM confirmed the presence of this vulnerability in Barracuda Spam
Firewall 600 Firmware 3.5.11.020.
The vendor has confirmed the issue exists in all versions prior to
Research and Advisory: Information Risk Management Plc.
Information Risk Management Plc (IRM) is a vendor independent
information risk consultancy, founded in 1998. IRM has become a leader
in client side risk assessment, technical level auditing and in the
research and development of security vulnerabilities and tools. IRM is
headquartered in London with Technical Centres in Europe and Asia as
well as Regional Offices in the Far East and North America. Please visit
our website at www.irmplc.com for further information.
All information in this advisory is provided on an 'as is' basis in the
hope that it will be useful. Information Risk Management Plc is not
responsible for any risks or occurrences caused by the application of
[ reply ]
Copyright 2010, SecurityFocus