Apache Tomcat is an open source software implementation for Java Servlet and JavaServer Pages (JSP) technologies.
The fix for CVE-2005-2090 was not complete. It did not cover the following cases: - - content-length header with chunked encoding over any HTTP connector - - multiple content-length headers over any AJP connector
Requests with multiple content-length headers or with a content-length header when chunked encoding is being used should be rejected as invalid. When multiple components (firewalls, caches, proxies and Tomcat) process a sequence of requests where one or more requests contain either multiple content-length headers or a content-length header when chunked encoding is being used and several components do not reject the request and make different decisions as to which content-length header to use an attacker can poison a web-cache, perform an XSS attack and obtain sensitive information from requests other then their own. Tomcat now rejects requests with multiple content-length headers or with a content-length header when chunked encoding is being used. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2013-4286 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 | 6.1 thru 6.3.2 | Low | Upgrade to 6.3.3 or later. |
Avaya Aura® Application Server 5300:
|
2.x, 3.0 including PB1 thru SP8 | Low | Upgrade to 3.0 SP 9 or later. |
Avaya Communication Server 1000:
|
7.x | Low | See recommended actions and Mitigating Factors table below. This advisory will not be addressed as no further releases are planned. |
| Avaya Aura® Conferencing | 7.x | Low | Upgrade to 8.0 or later. |
| Avaya Aura® Conferencing Standard Edition | 6.0.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.0 thru 6.0.3, 7.0 thru 7.0.1 | Low | For 6.0, upgrade to 6.0.3 and Avaya Linux for 6.0.3 and install Security Updates for 6.0.3. For 6.0.3, install Security Updates for 6.0.3. For 7.0 upgrade to 7.0.1 and install Security Updates for 7.0.1. For 7.0.1, install Security Updates for 7.0.1. |
| Avaya IP Office Server Edition | 8.1, 9.0 | Low | Upgrade to 9.1 or later. |
| Avaya IP Office Application Server | 8.x, 9.0 | Low | Upgrade to 9.1 or later. |
| Avaya Meeting Exchange | 5.x, 6.x | Low | Upgrade to 6.2 SP4 or later. |
| Avaya Aura® Messaging | 6.0 thru 6.3.3.4 | Low | Upgrade to 6.3.3.5 or later. |
| Avaya Messaging Application Server | 5.2 including 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 Proactive Contact | 5.0 thru 5.1.1 | Low | Upgrade to 5.1.2 or later. |
| Avaya Aura® System Platform | 1.1, 6.0 thru 6.3.4 | Low | Upgrade to 6.3.5 or later. |
| Avaya Aura® Utility Services | 6.0 thru 6.3 SP7 | Low | Upgrade to 6.3 SP8 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:
| Vulnerability | Mitigating Factors |
|---|---|
|
CVE-2013-4286 |
This is a Low risk as authentication would be required and no critical system processes or applications would be affected, nor would additional capabilities be gained. |
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.
| Product: | Actions: |
|---|---|
| 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 - April 1, 2014 - Initial Statement issued.
V 2.0 - September 4, 2014 - Updated AES affected versions and actions, Conferencing actions, and removed Avaya IQ from affected products.
V 3.0 - April 3, 2015 - Updated AS5300, IPO and SP affected versions and actions.
V 4.0 - April 21, 2015 - Updated EP and CMUS affected versions and actions.
V 5.0 - August 21, 2015 - Updated IPOAS and MAS affected versions and actions.
V 6.0 - September 17, 2015 - Updated PS actions.
V 7.0 - Aug 11, 2016 - Updated PC affected versions and actions.
V 8.0 - January 24, 2017 - Updated Messaging affected versions and actions.
V 9.0 - September 14, 2017 - Updated MX affected versions and actions and ASA 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
[email protected].
© 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.