Apache Tomcat is an open source software implementation for Java Servlet and JavaServer Pages (JSP) technologies.
When processing a request submitted using the chunked transfer encoding, Tomcat ignored but did not limit any extensions that were included. This allows a client to perform a limited DOS by streaming an unlimited amount of data to the server. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2012-3544 to this issue.
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® Application Enablement Services||5.x thru 6.3||Low||Upgrade to 6.3.1 or later.|
|Avaya Aura® Application Server 5300:
||2.x, 3.0 including PB1 thru PB5||Low||For 2.x, upgrade to 3.0 and install SP6 or later.
For 3.x, install SP6 or later.
|Avaya Aura® Conferencing||7.0 thru 7.2 SP5||Low||Upgrade to 7.2 SP6 or later.|
|Avaya Aura® Conferencing Standard Edition||6.x||Low||See recommended actions and Mitigating Factors table below. This advisory will not be addressed as no further releases are planned. It is recommended that customers migrate to one of Avaya's conferencing solutions including Aura® Conferencing 7.0 or later.|
|Avaya Aura® Experience Portal||6.x||Low||Upgrade to 7.0 or later.|
|Avaya IP Office Server Edition||8.1||Low||Upgrade to 9.0 or later.|
|Avaya IP Office Application Server||8.x||Low||Upgrade to 9.0 or later.|
|Avaya IQ||5.2 thru 5.2.5||Low||Upgrade to 5.2.6 and install Patch 2 or later.|
|Avaya Meeting Exchange||5.x through 6.2 SP3||Low||Upgrade to 6.2 SP4 or later.|
|Avaya Aura® Messaging||6.0 thru 6.3.2||Low||Upgrade to 6.3.2 SP2 and install patch 2 or later.|
|Avaya Messaging Application Server||5.2 thru 5.2 SP18||Low||Upgrade to 5.2 SP19 or later.|
|Avaya Aura® Presence Services||6.x||Low||Upgrade to Aura Presence Services 7.0 or later. Further information about this version, as well as the overall Aura 7.0 release, is available on support.avaya.com.|
|Avaya Aura® SIP Enablement Services||5.2.x||Low||See Mitigating Factors table below. There are no current plans to resolve this issue.|
|Avaya Aura® System Platform||6.0 thru 6.3||Low||Upgrade to 6.3.1 or later.|
|Avaya Aura® Utility Services||6.0 thru 6.3||Low||Upgrade to 6.3.1 or later.|
|Avaya Voice Portal||5.x||Low||Upgrade to Experience Portal 7.0 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:
|CVE-2012-3544||This is a low risk for all products because chunked transfer encoding requests are not allowed by default.|
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 - June 27, 2013 - Initial Statement issued.
V 2.0 - January 14, 2014 - Changed AS5300, EP, Conferencing SE, Utility Services and VP affected versions and actions.
V 3.0 - April 21, 2015 - Changed AES, Conferencing, IPOSE, IPOAS and SP affected versions and actions.
V 4.0 - June 10, 2015 - Changed Messaging and Messaging Application Server affected versions and actions.
V 5.0 - October 15, 2015 - Changed IQ and PS affected versions and actions.
V 6.0 - September 11, 2017 - Updated affected versions and actions for MX, and set Advisory status to Final.
© 2013 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.