Headline
CVE-2019-7003: ASA-2019-119
A SQL injection vulnerability in the reporting component of Avaya Control Manager could allow an unauthenticated attacker to execute arbitrary SQL commands and retrieve sensitive data related to other users on the system. Affected versions of Avaya Control Manager include 7.x and 8.0.x versions prior to 8.0.4.0. Unsupported versions not listed here were not evaluated.
Avaya Control Manager SQL Injection (CVE-2019-7003)
Original Release Date: July 9, 2019
Last Revised: July 10, 2019
Number: ASA-2019-119
Overall Severity Classification: Critical
Advisory Version: 2.0
Advisory Status: Final
1. Overview:
Avaya Control Manager is an operational administration solution enabling administrators to control key administrative elements across both Avaya Oceana™ & Avaya Enterprise Cloud: xCaaS solution offerings, and Avaya based contact center & Avaya Aura unified communications environments.
A SQL injection vulnerability was found in the reporting component of Avaya Control Manager which could allow an unauthenticated attacker to execute arbitrary SQL commands and retrieve sensitive data related to other users on the system. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2019-7003 to this issue.
Avaya would like to thank Ben Leonard-Lagarde (Modux) 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 Control Manager
7.x, 8.0.0.0 through 8.0.3.0
Upgrade to 8.0.4.0 or later.
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 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-2019-7003
9.3 (Critical)
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N
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 - July 9, 2019 - Initial Statement issued.
V 2.0 - July 10, 2019 - Updated reporter surname and finalized advisory.
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].
© 2019 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.