Apache Tomcat is an open source software implementation for Java Servlet and JavaServer Pages (JSP) technologies.
When using FORM authentication there was a narrow window where an attacker could perform a session fixation attack. The window was considered too narrow for an exploit to be practical but, erring on the side of caution, this issue has been treated as a security vulnerability. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2019-17563 to this issue.
More information about this vulnerability can be found in the security advisory issued by Apache Tomcat:
For assessment and severity classification details refer to Section 3 of Avaya's Product Security Vulnerability Response Policy.
The "Resolution" column will be updated as fixes are made available. Please reference the "Information" column for any additional information regarding the affected product.
| Product: | Version(s): | Resolution: | Information: |
|---|---|---|---|
| Avaya Aura® Application Enablement Services | 7.1.x through 8.1.3.2 | Upgrade to 8.1.3.3 or later. | |
Avaya Aura® Application Server 5300:
|
3.0 SP13.1 thru 3.0 SP15.3 | Upgrade to 3.0 SP15.4 or later. | |
| Avaya CMS | R18.x, R19.0.x | Upgrade to 19.1.0 or later. | |
| Avaya Aura® Conferencing | 8.0 thru 8.0 SP16 | Upgrade to 8.0 SP17 or later. | |
| Avaya Aura® Experience Portal | 7.2.1, 7.2.2 | Upgrade to 7.2.3 or later. | |
| Avaya IP Office | 10.x, 11.0.x | Upgrade to 11.1 or later. | |
| Avaya Meeting Exchange | 6.2 SP4 through 6.2 SP8 | Upgrade to 6.2 SP9 or later. | |
| Avaya Aura® Messaging | 6.3.x through 7.1 SP2 | Upgrade to 7.1 SP3 or later. | |
| Avaya one-X® Client Enablement Services | 6.2.x | No fix planned. | |
| Avaya Proactive Contact | 5.0 through 5.2.0.1 | Upgrade to 5.2.0.2 or later. | |
| Avaya Session Border Controller for Enterprise | 7.x, 8.0 thru 8.0.1.x | Upgrade to 8.1.0.0 or later. | |
| Avaya Aura® Utility Services | 7.0 thru 7.1.3.5 | Upgrade to 7.1.3.6 or later. |
Recommended Actions for System Products:
Avaya strongly recommends following 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 the System Product operating system or
application should not be modified unless the change is
approved by Avaya. Making changes that are not approved may
void the Avaya product service contract.
Avaya uses the Common Vulnerability Scoring System
(CVSS) base score and metrics as reported by the vendor for the affected component(s) or by the National Institute of Standards and Technology in the National Vulnerability Database. In some cases, such as where CVSS information is not available from the vendor or NIST, Avaya will calculate the CVSS base score and metrics. Customers are encouraged to calculate the Temporal and Environmental CVSS scores to determine how the vulnerability could affect their specific implementation or environment. For more information on CVSS and how the score is calculated, see
Common Vulnerability Scoring System: Specification Document.
| Vulnerability | CVSSv3 Base Score | CVSSv3 Metrics |
|---|---|---|
| CVE-2019-17563 |
7.5 (High) | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H |
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: |
|---|---|
| Aura® Application Enablement Services | If the affected package is installed, determine if Apache Tomcat is installed by the Avaya software-only product or as a separate application and follow the vendor's guidance. |
| Aura® Experience Portal | If the affected package is installed, determine if Apache Tomcat is installed by the Avaya software-only product or as a separate application and follow the vendor's guidance. |
| Avaya one-X Client Enablement Services | If the affected package is installed, 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, IS PROVIDED "AS IS", AND IS APPLICABLE ONLY TO PRODUCT VERSIONS ELIGIBLE FOR MANUFACTURER SUPPORT IN ACCORDANCE WITH AVAYA PRODUCT LIFE CYCLE POLICY. 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 24, 2020 - Initial Statement issued.
V 2.0 - December 16, 2020 - Updated AS5300, CMS, Conferencing, EP, IPO and SBCE Versions and Resolutions.
V 3.0 - April 5, 2022 - Updated AES, MX, Messaging, one-X CES and PC Versions and Resolutions,
and set advisory status to Final..
Avaya customers or Business Partners should report any security issues found with Avaya products via the standard support process.
Independent security researchers can contact Avaya at
[email protected].
© 2020 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.