VMware® has issued security advisory VMSA-2014-0012.1 to address one or more security vulnerabilities. These are libxml2, Curl and Python package updates to address multiple security issues. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2013-2877, CVE-2014-0191, CVE-2014-0015, CVE-2014-0138, CVE-2013-1752 and CVE-2013-4238 to these issues.
A description of these vulnerabilities may be found at:
Certain Avaya products are supported on a VMware ESXi Virtualization Platform and may be affected by these vulnerabilities.
The following products are installable on a customer supplied VMware system. Actions to be taken with these products are described below.
| Product: | Affected Version(s): | Risk Level: | Actions: |
|---|---|---|---|
| Avaya Aura® Application Enablement Services | 6.2.x and later | Low | Avaya recommends that customers install the security update as detailed in the VMware security advisory. |
| Avaya CMS | R17 and later | Low | Avaya recommends that customers install the security update as detailed in the VMware security advisory. |
| Avaya Aura® Collaboration Environment | 2.x and later | Low | Avaya recommends that customers install the security update as detailed in the VMware security advisory. |
| Avaya Aura® Communication Manager | 6.2.x and later | Low | Avaya recommends that customers install the security update as detailed in the VMware security advisory. |
| Avaya Aura® Presence Services | 6.1.x and later | Low | Avaya recommends that customers install the security update as detailed in the VMware security advisory. |
| Avaya Aura® Session Manager | 6.2.x and later | Low | Avaya recommends that customers install the security update as detailed in the VMware security advisory. |
| Avaya Aura® System Manager | 6.2.x and later | Low | Avaya recommends that customers install the security update as detailed in the VMware security advisory. |
| Avaya Aura® Utility Services | 6.2.x and later | Low | Avaya recommends that customers install the security update as detailed in the VMware security advisory. |
Recommended Actions for Products running on VMware:
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 the recommended
update is applied.
Further restrictions as deemed necessary based on the
customer's security policies may be required during this
interim period.
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-2877 CVE-2014-0191 |
These are a Low risk as processing of XML files is not possible without local account access. |
| CVE-2014-0138 | This is a Low risk as curl functionality is only possible with local account access. |
| CVE-2014-0015 | There is no risk as NTLM connections are not supported. |
|
CVE-2013-1752 CVE-2013-4238 |
These are a Low risk as the Python SSL module is not used to process certificates. |
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 3, 2015 - 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].
VMware® is the registered trademark of VMware Inc. in the U.S. and other countries.
© 2015 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.