Tomcat provides support for sendfile with the HTTP NIO and HTTP APR connectors. Sendfile is used automatically for content served via the DefaultServlet and deployed Web applications may use it directly via setting request attributes. These request attributes were not validated. When running under a security manager, this lack of validation allowed a malicious Web application to return files to users that the security manager should make inaccessible or terminate (via a crash) the JVM. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-2526 to this issue.
More information about this vulnerability can be found in the security advisories issued for the following releases of Apache Tomcat:
|Product:||Affected Version(s):||Risk Level:||Actions:|
|Avaya Aura® Application Enablement Services||5.2 thru 5.2.3, 6.1.x||Low||Application Enablement Services 5.2 thru 5.2.3: Upgrade to 5.2.4 or 6.2 or later.
Application Enablement Services 6.1.x: Upgrade to 6.2 or later.
|Avaya Aura® Application Server 5300:
||2.0 including PB1 thru PB26||Low||Upgrade to 2.0 PB27 or later.|
|Avaya Communication Server 1000:
||6.0, 7.x||Low||See recommended actions below. This advisory will not be addressed as no upgrade of Tomcat is planned.|
|Avaya IQ||5.2 thru 5.2.5||Low||Upgrade to IQ 5.2.6 and install Patch 2 or later.|
|Avaya Aura® Presence Services||6.0.x, 6.1.x||Low||Upgrade to 6.2 or later.|
|Avaya Aura® System Platform||1.1, 6.0||Low||Upgrade to System Platform 6.2 SP1 or later.|
|Avaya Voice Portal||5.0.x, 5.1, 5.1 SP1, 5.1 SP2||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:
||This is a Low risk as Avaya products only run trusted Avaya Web applications.|
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 - August 30, 2011 - Initial Statement issued.
V 2.0 - September 28, 2012 - Updated actions for Application Enablement Services, Communication Server 1000, System Platform and Voice Portal.
V 3.0 - November 1, 2012 - Updated affected versions and actions for Application Enablement Services.
V 4.0 - October 29, 2013 - Updated Application Server 5300 and Presence Services affected versions and actions,
removed Session Manager and System Manager because Tomcat is provided by JBoss.
V 5.0 - June 25, 2015 - Updated IQ affected versions and actions, and set 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 email@example.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.