Back to list
Multiple Vulnerabilities in Hummingbird Collaboration
Jan 10 2006 04:05PM
luca carettoni securenetwork it
Secure Network - Security Research Advisory
Vuln name: Multiple Vulnerabilities in Hummingbird Collaboration
Systems affected: Collaboration 5.2.1 and lower versions
Vendor URL: http://www.hummingbird.com/products/enterprise/collaboration/
Author(s): Luca Carettoni - luca.carettoni (at) securenetwork (dot) it [email concealed]
Federico Maggi - federico.maggi (at) securenetwork (dot) it [email concealed]
Vendor disclosure: 20th December 2005
Vendor acknowledged: 21st December 2005
Public disclosure: 10th January 2006
Advisory number: SN-2006-01
Advisory URL: http://www.securenetwork.it/advisories/
*** SUMMARY ***
Hummingbird Collaboration is a Web-based collaborative groupware for
teams across and beyond the enterprise.
It integrates different works on single projects accessed by several
concurrent users, improving efficiency, organization and automated workflow.
Regular and registered users can easily access to all project information,
documents, discussion threads, tasks list through the Web.
It includes several utilities like messaging system, project and
file manager and a Web calendar.
(a) Cross-Site Scripting (XSS), (b) improper file handling and (c) information disclosure
vulnerabilities are present and can be exploited remotely.
*** VULNERABILITY DETAILS ***
(a) Cross Site Scripting (XSS)
A second-order XSS have been found. It allows permanent scripting by uploading
malicious client side scripts by embedding them in a HTML page.
Hummingbird Collaboration does not verify the content of HTML files during the
In addition, the collaborative groupware does not force the HTML to be downloaded
(e.g. forcing the "Content-Disposition" property): As a result, the HTML page
and embedded scripts are normally interpreted and rendered by the user browser.
An attacker could (1) plan session hijacking attacks, (2) prepare phishing
(a regular user could be tricked by presenting him/her with a fake login page)
and (3) affect the usability and the availability of the service.
(b) Improper file handling
Using a crafted URL, a user could force the download of a previously uploaded
file changing its original name.
By exploiting this vulnerability, a regular user can be tricked about
file content and filename of what he/she's downloading.
(c) Information disclosure
By inspecting some application responses it is possible to get more information
about the parameters type and format. Instead of displaying generic error
messages, detailed information are sent to the client (e.g. the parameter must be TRUE or FALSE).
Moreover, by inspecting the application cookies is it possible to get internal
network information about the IP address of the application server.
*** EXPLOIT ***
(a) An attacker can simply upload an HTML file with embedded malicious
(b) An attacker would need to trick the user into downloading a certain
file with a crafted URL, like the following one:
In this example, the file with id equal to 1189762 is downloaded,
changing the name and the type of txt file in "fake.doc".
Other techniques (e.g. XSS) make it easy to create a fake link
similar to the previous one.
(c) In most cases it just involves the inspection of server responses.
The following URL shows an example of improper error handling
using [numericParam] instead of a string parameter.
The internal IP address is "encoded" into the cookie name
*** FIX INFORMATION ***
The vendor suggests that updating the software solves this
vulnerability, however we have not been able to test the latest
versions and to confirm this.
*** WORKAROUNDS ***
It should be noted that the server may only be accessed by users
who have accounts and who have been correctly authenticated.
Users may be restricted to be read-only so that they cannot upload files.
*** LEGAL NOTICES ***
Secure Network (www.securenetwork.it) is an information security company,
which provides consulting and training services, and engages in security
research and development.
We are committed to open, full disclosure of vulnerabilities, cooperating
with software developers for properly handling disclosure issues.
This advisory is copyright © 2006 Secure Network S.r.l. Permission is
hereby granted for the redistribution of this alert, provided that it is
not altered except by reformatting it, and that due credit is given. It
may not be edited in any way without the express consent of Secure Network
S.r.l. Permission is explicitly given for insertion in vulnerability
databases and similars, provided that due credit is given to Secure Network
The information in the advisory is believed to be accurate at the time of
publishing based on currently available information. This information is
provided as-is, as a free service to the community by Secure Network
research staff. There are no warranties with regard to this information.
Secure Network does not accept any liability for any direct, indirect,
or consequential loss or damage arising from use of, or reliance on,
If you have any comments or inquiries, or any issue with what is reported
in this advisory, please inform us as soon as possible.
E-mail: securenetwork (at) securenetwork (dot) it [email concealed]
GPG/PGP key: http://www.securenetwork.it/pgpkeys/Secure%20Network.asc
Phone: +39 0363 560 402
[ reply ]
Copyright 2010, SecurityFocus