Nio connector is used for HTTP connections. Tomcat 6.0.0 through 6.0.30 and 7.0.0 through 7.0.6 does not enforce the maxHttpHeaderSize limit while parsing the request line in the NIO HTTP connector. A specially crafted request could trigger an DoS via an OutOfMemoryError. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-0534 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 | Low | Upgrade to 6.1.1 or later. |
| Avaya Aura® Application Server 5300 | 2.0 | Low | Upgrade to 2.0 PB14 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 Avaya Aura® Conferencing 7.0 or later. |
| Avaya Meeting Exchange | 5.x | Low | Upgrade to 6.2 or later. |
| Avaya Aura® Presence Services | 6.0, 6.1, 6.1.1 | Low | Upgrade to 6.1.2 or later. |
| Avaya Aura® Session Manager | 1.1, 5.2, 6.0 thru 6.2 | Low | Upgrade to 6.2.1 or later. |
| Avaya Aura® System Manager | 5.2.x through 6.2.3 | Low | Upgrade to 6.3 or later. |
| Avaya Aura™ System Platform | 6.0.x | Low | Upgrade to 6.2 or later. |
| Avaya Voice Portal | 5.0, 5.1 thru 5.1.2 | Low | Upgrade to Avaya Enterprise Linux for Voice Portal 5.1 SP3 and Voice Portal 5.1 SP3 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-2011-0534 |
This is a Low risk since the NIO connector is not used as part of the default installation. |
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 22, 2011 - Initial Statement issued.
V 2.0 - February 5, 2013 - Updated AES, AS5300, PS, SM, SMGR,SP and VP affected versions and actions.
V 3.0 - July 3, 2013 - Updated CSE actions and MX affected versions.
V 4.0 - October 11, 2013 - Updated MX affected versions and actions.
V 5.0 - December 16, 2013 - Updated MX actions and Advisory Status to Final.
Send information regarding any discovered security problems with Avaya products to either the contact noted in the product's documentation or securityalerts@avaya.com.
© 2011 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.