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.
An invalid free flaw was found in the way OpenSSL handled certain DTLS handshake messages. A malicious DTLS client or server could cause a DTLS server or client using OpenSSL to crash or, potentially, execute arbitrary code. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2014-8176 to this issue.
A flaw was found in the way the OpenSSL packages shipped with Red Hat Enterprise Linux 6 and 7 performed locking in the ssleay_rand_bytes() function. This issue could possibly cause a multi-threaded application using OpenSSL to perform an out-of-bounds read and crash. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2015-3216 to this issue.
An out-of-bounds read flaw was found in the X509_cmp_time() function of OpenSSL. A specially crafted X.509 certificate or a Certificate Revocation List (CRL) could possibly cause a TLS/SSL server or client using OpenSSL to crash. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2015-1789 to this issue.
A race condition was found in the session handling code of OpenSSL. This issue could possibly cause a multi-threaded TLS/SSL client using OpenSSL to double free session ticket data and crash. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2015-1791 to this issue.
A flaw was found in the way OpenSSL handled Cryptographic Message Syntax (CMS) messages. A CMS message with an unknown hash function identifier could cause an application using OpenSSL to enter an infinite loop. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2015-1792 to this issue.
A NULL pointer dereference was found in the way OpenSSL handled certain PKCS#7 inputs. A specially crafted PKCS#7 input with missing EncryptedContent data could cause an application using OpenSSL to crash. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2015-1790 to this issue.
More information about these vulnerabilities can be found in the security advisory issued by Red Hat:
| Product: | Affected Version(s): | Risk Level: | Actions: |
|---|---|---|---|
| Avaya CMS | R17 thru R17 R4 | Low | Upgrade to R17 R5 or R18, or later. |
| Avaya Breeze™ Platform | 2.x, 3.0 | Low | Upgrade to 3.1 or later. |
| Avaya Aura® Conferencing | 8.0 thru 8.0 SP4 | Low | Upgrade to 8.0 SP5 or later. |
| Avaya Aura® Experience Portal | 6.x, 7.0, 7.0.1 | Low | For 6.0, upgrade to 7.0.2 and Avaya Linux for 7.0.2 and install Linux Patch 2015-10 or later. For 7.0.x install Linux Patch 2015-10 or later. |
| Avaya IP Office Server Edition | 8.1, 9.0 thru 9.1.5 | Low | Upgrade to 9.1.6 or later. |
| Avaya IP Office Application Server | 9.0 thru 9.1.5 | Low | Upgrade to 9.1.6 or later. |
| Avaya one-X® Client Enablement Services | 6.2 thru 6.2 SP3 | Low | Upgrade to 6.2 SP4 or later. |
| Avaya Session Border Controller for Enterprise | 6.3.x | Low | Upgrade to 7.0 or later. |
| Avaya Aura® Session Manager | 6.3 thru 6.3.14, 7.x | Low | For 6.3 upgrade to 6.3.15 or later 6.3.x release. For 7.0 upgrade to 7.0.0.1 or later. |
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.
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-8176 |
This is a Low risk as DTLS is not used. |
|
CVE-2015-1789 |
This is a Low risk as X509 certificates from untrusted sources are not accepted and CRL are not used. |
|
CVE-2015-1790 |
This is a Low risk as PKCS 7 is not used. |
|
CVE-2015-1791 |
This is a Low risk as only a single thread handles TLS connections. |
|
CVE-2015-1792 |
This is a Low risk as CMS messages are not accepted from untrusted sources. |
|
CVE-2015-3216 |
This is a Low risk as multi-threaded applications are not used by default. |
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 Linux platform may be. Customers should determine on which Linux operating system the product was installed and then follow that vendor's guidance.
| Product: | Actions: |
|---|---|
| Avaya Aura® Experience Portal | Depending on the Operating System installed, the affected package may be installed on the underlying Operating System supporting the EP application. |
Recommended Actions for Software-Only Products:
In the event that the affected package is installed, Avaya recommends following recommended actions supplied by Red Hat regarding their Enterprise Linux.
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 - July 14, 2015 - Initial Statement issued.
V 2.0 - October 20, 2015 - Updated CMS, CE, EP, one-X CES, ASBCE and SM affected versions and actions.
V 3.0 - November 19, 2015 - Updated CMS affected versions and actions.
V 4.0 - June 1, 2016 - Updated Conferencing, IPO, IPOAS and SM affected versions and actions 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
[email protected].
Linux® is the registered trademark of Linus Torvalds 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.