Accellion Kiteworks contains multiple vulnerabilities
Original Release date: 26 Aug 2016 | Last revised: 26 Aug 2016
The Accellion Kiteworks appliance prior to version kw2016.03.00 contains multiple vulnerabilities.
CWE-276: Incorrect Default Permissions – CVE-2016-5662
The `/opt/bin/cli` script has setuid permissions by default, allowing an authenticated KiteWorks users to escalate privileges of commands to root.
In practice, the user would likely already have administrator or root privileges.CWE-79: Improper Neutralization of Input During Web Page Generation (‘Cross-site Scripting’) – CVE-2016-5663An unauthenticated remote user may be able to conduct reflected cross-site scripting attacks using the code, error, and error_description parameters of oauth_callback.php.CWE-22: Improper Limitation of a Pathname to a Restricted Directory (‘Path Traversal’) – CVE-2016-5664An unauthenticated remote attacker may be able to view limited sets of files outside of the webroot directory by a crafted HTTP request.CWE-16: ConfigurationAccording to the reporter, Accellion KiteWorks is pre-configured with insecure defaults that may allow a remote user to create an SSH tunnel for a local user and bypass typical authentication channels.
The KiteWorks appliance also is configured to allow local user access without further authentication to the Apache Solr and Memcache instances.The CVSS score below is based on CVE-2016-5664.
An unauthenticated user may be able to conduct cross-site scripting attacks or read limited files from the appliance.
An authenticated user may be able to elevate privileges of commands to root.
Apply an update
Accellion has addressed these issues in KiteWorks version kw2016.03.00.
Affected users are encouraged to update their software as soon as possible.
Vendor Information (Learn More)
16 Aug 2016
If you are a vendor and your product is affected, let us know.
CVSS Metrics (Learn More)
Thanks to Shubham Shah for reporting this vulnerability.
This document was written by Garret Wassermann.
If you have feedback, comments, or additional information about this vulnerability, please send us email.