Apache Tomcat Session fixation with FORM authenticator (CVE-2013-2067)

Original Release Date: August 13, 2013
Last Revised: October 13, 2017
Number: ASA-2013-311
Risk Level: Medium
Advisory Version: 3.0
Advisory Status: Final

1. Overview:

Apache Tomcat is an open source software implementation for Java Servlet and JavaServer Pages (JSP) technologies.

FORM authentication associates the most recent request requiring authentication with the current session. By repeatedly sending a request for an authenticated resource while the victim is completing the login form, an attacker could inject a request that would be executed using the victim's credentials. This attack has been prevented by changing the session ID prior to displaying the login page as well as after the user has successfully authenticated.

The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2013-2067 to this issue.

More information about this vulnerability can be found in the security advisory issued by Apache Tomcat:

2. Avaya System Products with affected version(s) of tomcat 6.x or 7.x installed:

Product: Affected Version(s): Risk Level: Actions:
Avaya Aura® Application Enablement Services 6.1 through 6.3 Medium Upgrade to 6.3.1 or later.
Avaya Aura® Application Server 5300:
  • SIP Core
2.x through 3.0 SP9 Medium Upgrade to 3.0 SP10 or later.
Avaya Communication Server 1000:
  • CS1000E
  • CS1000M
  • CS1000E/CS1000M Signaling Server
6.x, 7.x None See Mitigating Factors table below.
Avaya Aura® Conferencing 7.0 through 7.2 SP5 Medium Upgrade to 7.2 SP6 or later.
Avaya Aura® Experience Portal 6.0.x Medium Upgrade to 7.0.1 and Avaya Enterprise Linux for 7.0.1 or later and install latest security updates.
Avaya IP Office Server Edition 8.x None See Mitigating Factors table below.
Avaya IP Office Application Server 8.x None See Mitigating Factors table below.
Avaya Meeting Exchange 6.2 through 6.2 SP3 Medium Upgrade to 6.2 SP4 or later.
Avaya Aura® Messaging 6.0 through 6.3.3 SP4 Medium Upgrade to 6.3.3 SP5 or later
Avaya Messaging Application Server 5.2.0 through 5.2.18 Medium Upgrade to 5.2.19 or later.
Avaya Aura® Presence Services 6.x Medium 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 Secure Access Link Gateway 2.x None See Mitigating Factors table below.
Avaya Aura® Session Manager 5.x, 6.x None See Mitigating Factors table below.
Avaya Aura® System Manager 5.x, 6.x None See Mitigating Factors table below.
Avaya Aura® System Platform 6.0 through 6.2.2 Medium Upgrade to 6.3 or later
Avaya Aura® Utility Services 6.2.x through 6.3.9 Medium Upgrade to 6.3.10 or later.
Avaya Voice Portal 5.1.3 Medium See recommended actions and Mitigating Factors table below. This advisory will not be addressed as there will be no further releases. It is recommended to upgrade to Avaya Aura® Experience Portal.

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.

Mitigating Factors:

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-2067
The risk is None for CS1000, IP Office, IP Office Application Server, Session Manager and System Manager because the affected versions of tomcat (6.0.21 - 6.0.36) are not installed.
The risk is None for SAL Gateway because its web interface does not use FORM authentication.
The risk is Medium for other products because the exploit could lead to compromise of confidentiality, integrity or availability of resources by an unauthenticated user.

3. Avaya Software-Only Products:

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.

4. Additional Information:

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.

5. Disclaimer:

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.

6. Revision History:

V 1.0 - August 13, 2013 - Initial Statement issued.
V 2.0 - August 5, 2016 - Updated affected versions and actions for: AES, AS 5300, Conferencing, EP, MAS, System Platform, US, VP, PS.
V 3.0 - October 13, 2017 - Updated affected versions and actions for MX and set the 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.

© 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.