OpenSSL Security Update (CVE-2014-0224, CVE-2014-3470)
Original Release Date: June 17, 2014
Last Revised: August 5, 2014
Number: ASA-2014-251
Risk Level: High
Advisory Version: 3.0
Advisory Status: Final
Overview
OpenSSL is a toolkit that implements the Secure Sockets Layer (SSL v2/v3) and Transport Layer Security (TLS v1) protocols, as well as a full-strength, general purpose cryptography library. Two vulnerabilities in the OpenSSL toolkit have been identified as potentially affecting the Avaya products listed below.
- CVE-2014-0224
It was found that OpenSSL clients and servers could be forced, via a specially crafted handshake packet, to use weak keying material for communication. A man-in-the-middle attacker could use this flaw to decrypt and modify traffic between a vulnerable client and a vulnerable server.
The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2014-0224 to this issue.
Note: In order to exploit this flaw, both the server and the client must be using a vulnerable version of OpenSSL. The server must be using OpenSSL version 1.0.1 and above, and the client must be using any version of OpenSSL. For more information about this flaw, refer to: www.kb.cert.org/vuls/id/978508
- CVE-2014-3470
A NULL pointer dereference flaw was found in the way OpenSSL performed anonymous Elliptic Curve Diffie Hellman (ECDH) key exchange. A specially crafted handshake packet could cause a TLS/SSL client that has the anonymous ECDH cipher suite enabled to crash.
The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2014-3470 to this issue.
Avaya would like to thank the OpenSSL project for reporting these issues. Upstream acknowledges KIKUCHI Masashi of Lepidum as the original reporter of CVE-2014-0224 and Felix Gröbert and Ivan Fratrić of Google as the original reporters of CVE-2014-3470.
All OpenSSL users are advised to upgrade to these updated packages, which contain backported patches to correct these issues. For the update to take effect, the applications linked to the OpenSSL library must be restarted or the system rebooted.
More information about these vulnerabilities can be found in the security advisory issued by OpenSSL:
A number of other vulnerabilities are discussed in the OpenSSL security advisory. Avaya has analyzed these vulnerabilities and determined that they are not applicable to the products listed in this notice. See Mitigating Factors below.
Avaya Desktop and Mobile Client Products using an affected version of OpenSSL include
| Product: | Affected Version(s): | Risk Level: | Actions: |
|---|---|---|---|
| Desktop applications | |||
| Avaya one-X® Communicator for Microsoft Windows | 6.1.x, x less than 10 |
High | Update the Avaya one-X® Communicator for Microsoft Windows client to version 6.1.10 or version 6.2.3. |
| Avaya one-X® Communicator for Microsoft Windows | 6.2.x, x less than 3 |
High | Update the Avaya one-X® Communicator for Microsoft Windows client to version 6.2.3. |
| Avaya one-X® Communicator for Mac OS X | 1.0.x, x less than 5 |
High | Update the Avaya one-X® Communicator for Mac OS X client to version 2.0.1.1. |
| Avaya one-X® Communicator for Mac OS X | 2.0.1.x, x less than 1 |
High | Update the Avaya one-X® Communicator for Mac OS X client to version 2.0.1.1. |
| Avaya Flare® Experience for Microsoft Windows | 1.1.x, x less than 5 |
High | Update the Avaya Flare® Experience for Microsoft Windows client to version 1.1.5 or to Avaya Communicator for Microsoft Windows version 2.0.1. |
| Avaya Communicator for Microsoft Windows | 2.0.x, x less than 1 |
High | Update the Avaya Communicator for Microsoft Windows client to version 2.0.1. |
| Avaya Client Applications | 2.x, 3.x | None | No action required. This application is not vulnerable to the issues described in this advisory. |
| Avaya Client Applications for Lync and CS1K | 6.2.x, x less than 3 |
High | Update the Avaya Client Applications client to version 6.2.3. |
| Avaya Client Applications for Lync | 6.3.x, x less than 1 |
High | Update the Avaya Client Applications client to version 6.3.1. |
| Avaya Collaboration Services | 6.2.x | None | No action required. This application is not vulnerable to the issues described in this advisory. |
| Avaya VDI Communicator (Windows) | 1.0.x, x less than 3 |
Medium | Update the Avaya VDI Communicator (Windows) client to version 1.0.3. |
| Mobile and tablet applications | |||
| Avaya one-X® Mobile SIP for iOS | 6.2.x, x less than 5 |
High | Update the Avaya one-X® Mobile SIP for iOS client to version 6.2.5. |
| Avaya one-X® Mobile SIP for iOS (CFE) | 6.2.x, x less than 5 |
High | Update the Avaya one-X® Mobile SIP for iOS (CFE) client to version 6.2.5. |
| Avaya one-X® Mobile CES for iPhone | All versions | None | No action required. This application is not vulnerable to the issues described in this advisory. |
| Avaya one-X® Mobile CES for Android | All versions | None | No action required. This application is not vulnerable to the issues described in this advisory. |
| Avaya one-X® Mobile Lite for iPhone | All versions | None | No action required. This application is not vulnerable to the issues described in this advisory. |
| Avaya one-X® Mobile Lite for Android | All versions | None | No action required. This application is not vulnerable to the issues described in this advisory. |
| Avaya Flare® Experience for iPad | 1.2.x, x less than 2 |
High | Update the Avaya Flare® Experience for iPad client to version 1.2.2. |
| Avaya Communicator for iPad (CFE) | 2.0.x, x less than 1 |
High | Update the Avaya Communicator for iPad client to version 2.0.1. |
| Avaya Communicator for Android | 2.0.x, x less than 2 |
High | Update the Avaya Communicator for Android client to version 2.0.2. |
| Avaya one-X® Mobile for BlackBerry | All versions | None | No action required. This application is not vulnerable to the issues described in this advisory. |
Recommended Actions:
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 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.Mitigating Factors:
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-2014-0224 | If client applications are operating entirely within a trusted environment (e.g. within a secure corporate network or virtual private network), the risk is reduced to Medium as authenticated access would be required. |
| CVE-2014-3470 | If client applications are operating entirely within a trusted environment (e.g. within a secure corporate network or virtual private network), the risk is reduced to Medium as authenticated access would be required. |
| CVE-2014-0221 | This issue is not applicable to the products named above. |
| CVE-2014-0195 | This issue is not applicable to the products named above. |
| CVE-2014-0198 | This issue is not applicable to the products named above. |
| CVE-2014-5298 | This issue is not applicable to the products named above. |
Dynamically-Linked Products
Avaya software-only products operate on general-purpose operating systems. Occasionally vulnerabilities may be discovered in the underlying operating system or applications that come with the operating system. These vulnerabilities often do not impact the software-only product directly but may threaten the integrity of the underlying platform.
In the case of this advisory Avaya software-only products are not affected by the vulnerability directly but the underlying platform may be. Customers should determine on which operating system the product was installed and then follow that vendor's guidance.
| Product: | Affected Vesion(s): | Risk Level: | Actions: |
|---|---|---|---|
| Avaya VDI Communicator (Linux) | 1.0.x, x less than 3 |
Medium | Depending on the Operating System installed, the affected package may be installed on the underlying Operating System supporting the application. |
Recommended Actions for Dynamically-Linked Products:
In the event that the affected package is installed, Avaya recommends following recommended actions supplied by the Operating System vendor.
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 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.
Mitigating Factors for Dynamicall-Linked Products:
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-2014-0224 | If client applications are operating entirely within a trusted environment (e.g. within a secure corporate network or virtual private network), the risk is reduced to Medium as authenticated access would be required. |
| CVE-2014-3470 | If client applications are operating entirely within a trusted environment (e.g. within a secure corporate network or virtual private network), the risk is reduced to Medium as authenticated access would be required. |
| CVE-2014-0221 | This issue is not applicable to the products named above. |
| CVE-2014-0195 | This issue is not applicable to the products named above. |
| CVE-2014-0198 | This issue is not applicable to the products named above. |
| CVE-2014-5298 | This issue is not applicable to the products named above. |
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.
Disclaimer
ALL INFORMATION IS BELIEVED TO BE CORRECT AT THE TIME OF PUBLICATION AND IS PROVIDED "AS IS". AVAYA INC., ON BEHALF OF 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.
Revision History
V 3.0 - August 5, 2014 - Update issued to clarify mitigating factors.
V 2.0 - July 8, 2014 - Update issued indicating available versions resolving the issue.
V 1.0 - June 17, 2014 - 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].
© 2014 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.