Insecure defaults for CORS filter (CVE-2018-8014)

Original Release Date: July 19, 2018
Last Revised: April 16, 2021
Number: ASA-2018-196
Overall Severity Classification: Critical
Advisory Version: 6.0
Advisory Status: Final

1. Overview:

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

The defaults settings for the CORS filter are insecure and enable 'supportsCredentials' for all origins. It is expected that users of the CORS filter will have configured it appropriately for their environment rather than using it in the default configuration. Therefore, it is expected that most users will not be impacted by this issue. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2018-8014 to this issue.

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

2. Avaya System Products with an affected version of Tomcat installed:

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 6.x, 7.x, 8.0.0 No fix needed. The risk is mitigated because the CORS filter is not enabled/used by default and would require privileged user permissions to change.

An upgrade to 7.1.3.4 or 8.0.1 or later will install a version of Tomcat that removes this potential vulnerability.
Avaya Aura® Application Server 5300:
  • SIP Core
3.0 through 3.0 SP 14.3 Upgrade to 3.0 SP14.4 or later.  
Avaya CMS R17.x through R18.1.0.0 Upgrade to R18.1.0.1 or later.  
Avaya Aura® Conferencing 8.0 through 8.0 SP11 Upgrade to 8.0 SP12 or later.  
Avaya Aura® Experience Portal 7.0.x through 7.2.1 Upgrade to 7.2.2 or later and install the latest Security Updates.  
Avaya IP Office 9.x through 11.0 FP4 Upgrade to 11.0 FP5 or later.  
Avaya IQ 5.x No further releases are planned. See recommended actions below. This advisory will not be addressed as no further releases are planned. It is recommended to migrate to Avaya Oceanalytics for Elite.
Avaya Meeting Exchange 6.2 through 6.2 SP6 Upgrade to 6.2 SP7 or later.  
Avaya Aura® Messaging 6.3.x, 7.0.x, 7.1 Upgrade to 7.1 SP1 or later.  
Avaya Proactive Contact 5.1.0 through 5.2.0.1 Upgrade to 5.2.0.2 or later.  
Avaya Aura® System Platform 6.x No further releases are planned. Avaya Aura R6 that includes System Platform is End of Manufacturer Support. It is recommended to migrate to Avaya Aura® Appliance Virtualization Platform.
Avaya Aura® Utility Services 6.x, 7.x No fix needed. The risk is mitigated because the CORS filter is not enabled/used by default and would require privileged user permissions to change.

An upgrade to 7.1.3.3 or later will install a version of Tomcat that removes this potential vulnerability.

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.

CVSS 3.0 Scoring and Metrics:

Avaya uses the Common Vulnerability Scoring System version 3 (CVSSv3) 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 CVSSv3 base score and metrics. Customers are encouraged to calculate the Temporal and Environmental CVSSv3 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 v3.0: Specification Document.

Vulnerability CVSSv3 Base Score CVSSv3 Metrics
CVE-2018-8014
9.8 (Critical) CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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

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

6. Revision History:

V 1.0 - July 19, 2018 - Initial Statement issued.
V 2.0 - January 9, 2019 - Updated AES, AS5300 and SP versions and resolution.
V 3.0 - April 23, 2019 - Updated AES, Conferencing, EP, Messaging and US resolution and information.
V 4.0 - August 29, 2019 - Updated CMS and IPO resolution and information.
V 5.0 - December 4, 2019 - Updated MX resolution and information.
V 6.0 - April 16, 2021 - Updated PC versions and resolution 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 securityalerts@avaya.com.

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