Apache Tomcat is an open source software implementation for Java Servlet and JavaServer Pages (JSP) technologies.
It is possible to craft a malformed Content-Type header for a multipart request that causes Apache Commons FileUpload to enter an infinite loop. A malicious user could, therefore, craft a malformed request that triggered a denial of service. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2014-0050 to this issue.
NOTE: This issue did not affect Tomcat 5 or Tomcat 6.
More information about this vulnerability can be found in the security advisory issued by Apache Tomcat:
|Product:||Affected Version(s):||Risk Level:||Actions:|
|Avaya Aura® Conferencing||7.x||Medium||Upgrade to 8.0 or later.|
|Avaya IP Office Server Edition||9.0||Medium||Upgrade to 9.1 or later.|
|Avaya IP Office Application Server||9.0||Medium||Upgrade to 9.1 or later.|
Recommended Actions for System Products:
Avaya strongly recommends that customers follow networking and security best practices by implementing firewalls, ACLs, physical security or other appropriate access restrictions. Though Avaya believes such restrictions should always be in place, risk to Avaya products and the surrounding network from this potential vulnerability may be mitigated by ensuring these practices are implemented until such time as an Avaya provided product update or the recommended Avaya action is applied. Further restrictions as deemed necessary based on the customer's security policies may be required during this interim period, but customers should not modify the System Product operating system or application unless the change is approved by Avaya. Making changes that are not approved may void the Avaya product service contract.
When determining risk, Avaya takes into account many factors as outlined by Avaya's Security Vulnerability Classification Policy. The following table describes factors that mitigate the risk of specific vulnerabilities for affected Avaya products:
||This a Medium risk due to the potental for an authenticated user to cause a Denial of Service.|
Avaya software-only products operate on general-purpose operating systems. Occasionally vulnerabilities may be discovered in the applications installed on the system which may threaten the integrity of the underlying platform.
|Avaya Aura® Application Enablement Services||See recommended actions below.|
|Avaya Aura® Experience Portal||See recommended actions below.|
|Avaya Aura® Presence Services||See recommended actions below.|
|Avaya Secure Access Link Gateway||See recommended actions below.|
|Avaya Voice Portal||See recommended actions below.|
Recommended Actions for Software-Only Products:
If the affected package is installed, Avaya recommends customers determine if Apache Tomcat is installed by the Avaya software-only product or as a separate application and follow the vendor's guidance.
Additional information may also be available via the Avaya support website and through your Avaya account representative. Please contact your Avaya product support representative, or dial 1-800-242-2121, with any questions.
ALL INFORMATION IS BELIEVED TO BE CORRECT AT THE TIME OF PUBLICATION AND IS PROVIDED "AS IS". AVAYA INC., ON BEHALF ITSELF AND ITS SUBSIDIARIES AND AFFILIATES (HEREINAFTER COLLECTIVELY REFERRED TO AS "AVAYA"), DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AND FURTHERMORE, AVAYA MAKES NO REPRESENTATIONS OR WARRANTIES THAT THE STEPS RECOMMENDED WILL ELIMINATE SECURITY OR VIRUS THREATS TO CUSTOMERS' SYSTEMS. IN NO EVENT SHALL AVAYA BE LIABLE FOR ANY DAMAGES WHATSOEVER ARISING OUT OF OR IN CONNECTION WITH THE INFORMATION OR RECOMMENDED ACTIONS PROVIDED HEREIN, INCLUDING DIRECT, INDIRECT, INCIDENTAL, STATUTORY, CONSEQUENTIAL DAMAGES, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF AVAYA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
THE INFORMATION PROVIDED HERE DOES NOT AFFECT THE SUPPORT AGREEMENTS IN PLACE FOR AVAYA PRODUCTS. SUPPORT FOR AVAYA PRODUCTS CONTINUES TO BE EXECUTED AS PER EXISTING AGREEMENTS WITH AVAYA.
V 1.0 - March 6, 2014 - Initial Statement issued.
V 2.0 - September 4, 2014 - Updated Conferencing actions.
V 3.0 - March 2, 2015 - Updated IPO and IPOAS affected versions and actions, set advisory status to final.
Avaya customers or Business Partners should report any security issues found with Avaya products via the standard support process.
Independent security researchers can contact Avaya at firstname.lastname@example.org.
© 2014 Avaya Inc. All Rights Reserved. All trademarks identifying Avaya products by the ® or ™ are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners.