Apache Tomcat is an open source software implementation for Java Servlet and JavaServer Pages (JSP) technologies.
For performance reasons, information parsed from a request is often cached in two places: the internal request object and the internal processor object. These objects are not recycled at exactly the same time. When certain errors occur that needed to be added to the access log, the access logging process triggers the re-population of the request object after it has been recycled. However, the request object was not recycled before being used for the next request. That lead to information leakage (e.g. remote IP address, HTTP headers) from the previous request to the next request. The issue was resolved be ensuring that the request and response objects were recycled after being re-populated to generate the necessary access log entries. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-3375 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.x | Low | Upgrade to 6.2. or later. |
Avaya Aura® Application Server 5300:
|
2.0.x | None | See Mitigating Factors table below. |
Avaya Communication Server 1000:
|
6.0.x, 7.0.x, 7.5.x | None | See Mitigating Factors table below. |
| Avaya Aura® Conferencing Standard Edition | 6.0.x | None | See Mitigating Factors table below. |
| Avaya Aura® Experience Portal | 6.0, 6.0.1 | Low | Upgrade to Avaya Enterprise Linux for 6.0.2 and 6.0.2 or later. |
| Avaya IP Office Application Server | 6.1, 7.0, 8.0 | None | See Mitigating Factors table below. |
| Avaya IQ | 5.x | None | See Mitigating Factors table below. |
| Avaya Meeting Exchange | 5.x | None | See Mitigating Factors table below. |
| Avaya Aura® Messaging | 6.0.x, 6.1.x | None | See Mitigating Factors table below. |
| Avaya Messaging Application Server | 5.x | None | See Mitigating Factors table below. |
| Avaya Aura® Presence Services | 6.0.x, 6.1.x | None | See Mitigating Factors table below. |
| Avaya Aura® Session Manager | 1.1.x, 5.2.x, 6.0.x, 6.1.x, 6.2.x | None | See Mitigating Factors table below. |
| Avaya Aura® SIP Enablement Services | 5.x | None | See Mitigating Factors table below. |
| Avaya Aura® System Manager | 5.2.x, 6.0.x, 6.1.x, 6.2.x | None | See Mitigating Factors table below. |
| Avaya Aura® System Platform | 1.1.x, 6.0.x, 6.2.x | None | See Mitigating Factors table below. |
| Avaya Aura® Communication Manager Utility Services | 6.x | None | See Mitigating Factors table below. |
| Avaya Voice Portal | 5.0.x, 5.1.x | None | See Mitigating Factors table below. |
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-3375 |
The risk is Low for Application Enablement Services and Experience
Portal because of the limited value of information that could be
leaked. There is no risk for all other products because the only versions of Tomcat affected are 6.0.30 - 6.0.33 and 7.x before 7.0.22. These other products do not have an affected version of Tomcat installed. |
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 16, 2012 - Initial Statement issued.
V 2.0 - March 19, 2012 - Updated Section 2 title, and changed affected
versions for SM, SMGR, and SP.
V 3.0 - March 19, 2013 - Updated AES and EP affected versions and 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 [email protected].
© 2012 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.