Apache Tomcat is an open source software implementation for Java Servlet and JavaServer Pages (JSP) technologies.
The CSRF prevention filter could be bypassed if a request was made to a protected resource without a session identifier present in the request. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2012-4431 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, 6.1.x, 6.2.x | Low | Upgrade to 6.3 or later. |
Avaya Aura® Application Server 5300:
|
2.x | Low | Install PB28 or later, or upgrade to 3.0 or later. |
Avaya Communication Server 1000:
|
6.x, 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.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.x, 6.1.x, 6.2.x | Low | Upgrade to 6.3 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® Session Manager | 5.2, 6.0 thru 6.2.x | Low | Upgrade to 6.3 or later. |
| Avaya Aura® SIP Enablement Services | 5.x | Low | See recommended actions below. This advisory will not be addressed as no further releases are planned. |
| Avaya Aura® System Manager | 5.2, 6.0 thru 6.2.x | Low | Upgrade to 6.3 or later. |
| Avaya Aura® System Platform | 1.x, 6.0.x, 6.2.x | Low | Upgrade to 6.3 or later. |
| Avaya Aura® Utility Services | 6.0 thru 6.2.x | Low | Upgrade to 6.3 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:
| Vulnerability | Mitigating Factors |
|---|---|
|
CVE-2012-4431 |
This is a low risk because the CSRF prevention filter is not used 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.
| 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 Aura® System Manager 1.0 | 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 - February 13, 2013 - Initial Statement issued.
V 2.0 - January 10, 2014 - Changed AES, IPOSE, SP, CMUS, and VP affected
versions and actions. Changed EP and IPOAS actions.
V 3.0 - August 5, 2014 - Changed Messaging affected versions and actions.
V 4.0 - November 15, 2014 - Changed Conferencing actions.
V 5.0 - October 15, 2015 - Changed IQ, MAS and PS affected versions and actions.
V 6.0 - September 6, 2017 - Updated affected versions and actions for MX, 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 protected].
© 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.