[NEWS] Barracuda Spam Firewall Arbitrary File Disclosure
- From: SecuriTeam <support@xxxxxxxxxxxxxx>
- Date: 2 Aug 2006 15:09:43 +0200
The following security advisory is sent to the securiteam mailing list, and can be found at the SecuriTeam web site: http://www.securiteam.com
- - promotion
The SecuriTeam alerts list - Free, Accurate, Independent.
Get your security news from a reliable source.
- - - - - - - - -
Barracuda Spam Firewall Arbitrary File Disclosure
<http://www.barracudanetworks.com> Barracuda Spam Firewalls are
vulnerable to arbitrary file disclosure due to improper parameter
* Barracuda Spam Firewalls from version 3.3.01.001 to 3.3.02.053
* Barracuda Spam Firewalls version 22.214.171.124
The Barracuda Spam Firewalls from version 3.3.01.001 to 3.3.02.053 are
vulnerable to arbitrary file disclosure via the preview_email.cgi script.
The /cgi-bin/preview_email.cgi script is designed to retrieve a message
from the local message database on the Barracuda Spam Firewall. However,
the "file" parameter which is passed via GET is not properly sanitized to
restrict the file retrieval to the message database directories. The
script looks for "/mail/mlog" in the file parameter but does not take into
account directory transversal arguments such as ".." The result is that
any file that is accessible to the web server user is accessible from the
web interface. The script does require a valid user to be logged in to
perform this attack, however using the "Barracuda Hardcoded Password
Vulnerability" (NNL-20060801-01) guest password vulnerability this
restriction can easily be overcome.
This particular problem is amplified by the fact that it is possible to
download the full configuration file for the barracuda. The configuration
file is periodically backed-up into the /tmp directory as
Message confidentiality is compromised by the fact that an attacker who is
able to view the message log screen (which can be done via the guest
password vulnerability) can easily view any message on the system. The
message logs are stored as /mail/mlog/X/Y/email_address/msgID where X is
the first character of email_address, Y is the second character of
email_address, email_address is the recipient's email address and msgID is
the message ID assigned to the message in question. So for example if jon
AT smith DOT com received a message with messageID 1234, any user could
view the message by entering /mail/mlog/j/o/jon AT smith DOT com/1234
Proof of Concept:
* Never allow your barracuda web interface to be accessible from untrusted
networks (especially the Internet)
* Upgrade to version 126.96.36.199 or later
30 May 2006 - Initial Vendor Contact
24 June 2006 - Vendor replies with prospect of fix
17 July 2006 - NNL request status update, no reply
01 Aug 2006 - NNL releases vulnerability report, notifies vendor of
The information has been provided by <mailto:gssincla@xxxxxxxxxxxxxxx>
This bulletin is sent to members of the SecuriTeam mailing list.
To unsubscribe from the list, send mail with an empty subject line and body to: list-unsubscribe@xxxxxxxxxxxxxx
In order to subscribe to the mailing list, simply forward this email to: list-subscribe@xxxxxxxxxxxxxx
The information in this bulletin is provided "AS IS" without warranty of any kind.
In no event shall we be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages.
- Prev by Date: [NEWS] Barracuda Spam Firewall Hardcoded Password Vulnerability
- Next by Date: [UNIX] TSEP copyright File Inclusion
- Previous by thread: [NEWS] Barracuda Spam Firewall Hardcoded Password Vulnerability
- Next by thread: [UNIX] TSEP copyright File Inclusion