CVE-2020-7032: ASA-2020-153

Avaya WebLM Vulnerability (CVE-2020-7032)

Original Release Date: November 12, 2020
Last Revised: November 12, 2020
Number: ASA-2020-153
Overall Severity Classification: Medium
Advisory Version: 1.0
Advisory Status: Final

1. Overview:

Avaya WebLM provides ability to manage licenses of one or more Avaya software products for your organization. WebLM is Web-based and facilitates easy tracking of licenses.

An XML external entity (XXE) vulnerability in WebLM admin interface allows authenticated users to read arbitrary files or conduct server-side request forgery (SSRF) attacks via a crafted DTD in an XML request. This issue has been assigned Common Vulnerabilities and Exposures (cve.mitre.org) identifier CVE-2020-7032.

Avaya would like to thank Markus Koplin of SEC Consult for reporting this issue.

2. Avaya Products affected:

For assessment and severity classification details refer to Section 3 of Avaya’s Product 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 WebLM

7.0 through 7.1.3.6, 8.0.x, 8.1 through 8.1.2 up to Hot Fix 3

For 7.x, upgrade to 7.1.3.7 or later.
For 8.0.x, upgrade to 8.1.3 or later.
For 8.1.x, install latest 8.1.2 Hot Fix or upgrade to 8.1.3 or later.

Hot Fix for System Manager 8.1.2
Avaya Aura Release Notes 8.1.x
Avaya Aura WebLM 7.1 Product Correction Notice

Avaya Aura® System Manager

7.0 through 7.1.3.6, 8.0 through 8.1.2 including Hot Fix 3 and earlier.

For 7.x, upgrade to 7.1.3.7 or later.
For 8.0.x, upgrade to 8.1.3 or later.
For 8.1.x, install latest 8.1.2 Hot Fix or upgrade to 8.1.3 or later.

System Manager is affected because the WebLM component is installed.
Hot Fix for System Manager 8.1.2
Avaya Aura Release Notes 8.1.x
Avaya Aura Release Notes 7.1.x

Recommended Actions for 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 Scoring and Metrics:

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-2020-7032

6.5 (Medium)

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:H

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

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

5. Revision History:

V 1.0 - November 12, 2020 - Initial Statement issued.

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.