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.
It was discovered that OpenSSL would accept ephemeral RSA keys when using non-export RSA cipher suites. A malicious server could make a TLS/SSL client using OpenSSL use a weaker key exchange method. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2015-0204 to this issue.
An integer underflow flaw, leading to a buffer overflow, was found in the way OpenSSL decoded malformed Base64-encoded inputs. An attacker able to make an application using OpenSSL decode a specially crafted Base64-encoded input (such as a PEM file) could use this flaw to cause the application to crash. Note: this flaw is not exploitable via the TLS/SSL protocol because the data being transferred is not Base64-encoded. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2015-0292 to this issue.
A denial of service flaw was found in the way OpenSSL handled SSLv2 handshake messages. A remote attacker could use this flaw to cause a TLS/SSL server using OpenSSL to exit on a failed assertion if it had both the SSLv2 protocol and EXPORT-grade cipher suites enabled. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2015-0293 to this issue.
Multiple flaws were found in the way OpenSSL parsed X.509 certificates. An attacker could use these flaws to modify an X.509 certificate to produce a certificate with a different fingerprint without invalidating its signature, and possibly bypass fingerprint-based blacklisting in applications. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2014-8275 to this issue.
An out-of-bounds write flaw was found in the way OpenSSL reused certain ASN.1 structures. A remote attacker could possibly use a specially crafted ASN.1 structure that, when parsed by an application, would cause that application to crash. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2015-0287 to this issue.
A NULL pointer dereference flaw was found in OpenSSL's X.509 certificate handling implementation. A specially crafted X.509 certificate could cause an application using OpenSSL to crash if the application attempted to convert the certificate to a certificate request. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2015-0288 to this issue.
A NULL pointer dereference was found in the way OpenSSL handled certain PKCS#7 inputs. An attacker able to make an application using OpenSSL verify, decrypt, or parse a specially crafted PKCS#7 input could cause that application to crash. TLS/SSL clients and servers using OpenSSL were not affected by this flaw. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2015-0289 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 Aura® Application Enablement Services | 6.x | Low | Upgrade to 7.0 or later. |
Avaya Aura® Application Server 5300:
|
3.0 thru 3.0 SP10 | Low | Upgrade to 3.0 SP11 or later. |
| Avaya IQ | 5.x | Low | See recommended actions and Mitigating Factors table below. This advisory will not be addressed as no further releases are planned. It is recommended to migrate to Avaya Oceanalytics for Elite. |
| Avaya Aura® Communication Manager | 6.0 thru 6.3 | Low | For 6.0 to 6.2.x, upgrade to 6.3 and install Security Service Pack 7 or
later. For 6.3, install Security Service Pack 7 or later. |
Avaya Communication Server 1000:
|
7.x | Low | See recommended actions and Mitigating Factors table below. This advisory will not be addressed as no further releases are planned. |
| Avaya Aura® Conferencing | 7.2 thru 7.2 SP6 | Low | Upgrade to 7.2 SP7 or later. |
| Avaya IP Office Application Server | 8.x | Low | See recommended actions and Mitigating Factors table below. This advisory will not be addressed as no further service packs or security updates are planned. It is recommended that customers upgrade to 9.1 or later to continue to receive software update support. |
| Avaya Meeting Exchange | 6.2 thru 6.2 SP2 | Low | Upgrade to 6.2 SP3 or later. |
| Avaya Message Networking | 6.3 | Low | Upgrade to 6.3 SP1 or later. |
| Avaya Aura® Messaging | 6.3 thru 6.3.3.5 | Low | Upgrade to 6.3.3.6 or later. |
| Avaya one-X® Client Enablement Services | 6.1.x | Low | Upgrade to 6.2 SP4 or later. |
| Avaya Aura® Presence Services | 6.x | Low | Upgrade to Aura Presence Services 7.0 or later. Further information about this version, as well as the overall Aura 7.0 release, is available on support.avaya.com. |
| Avaya Proactive Contact | 5.0.x, 5.1.0, 5.1.1 | Low | Upgrade to 5.1.2 or later. |
| Avaya Aura® Session Manager | 6.0.x, 6.1.x, 6.2.x | Low | Upgrade to 6.3.15 or later. |
| Avaya Aura® System Manager | 6.0 thru 6.3.14 | Low | Upgrade to 6.3.15 or later. |
| Avaya Aura® System Platform | 6.0 thru 6.3.6 | Low | Upgrade to 6.3.7 or later. |
| Avaya Aura® Utility Services | 6.0 thru 6.3 SP9 | Low | Upgrade to 6.3 SP10 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-8275 | The risk is rated Low for all listed products because the fingerprint-based certificate-blacklist protection mechanism is not used by default. |
| CVE-2015-0204 | The risk is rated Low for all listed products because weak keys are disabled by default. |
| CVE-2015-0287 | This is a Low risk for all listed products because OpenSSL is used for parsing certificates and certificate parsing is not affected by this vulnerability. |
| CVE-2015-0288 | This is a Low risk for all listed products because untrusted X.509 certificates are not used and they are not converted to certificate requests without non-standard direct user interaction. |
| CVE-2015-0289 | This is a Low risk for all listed products as only SSL/TLS secure connections are used and PKCS#7 input is not used by default without non-standard direct user interaction. |
| CVE-2015-0292 | This is a Low risk for all listed products as only SSL/TLS secure connections are used and Base64-encoded input from untrusted sources is not used by default without non-standard direct user interaction. |
| CVE-2015-0293 | This is a Low risk for all listed products because SSLv2 and EXPORT-grade cipher suites are disabled 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® Application Enablement Services | Depending on the Operating System installed, the affected package may be installed on the underlying Operating System supporting the AES application. |
| Avaya IQ | Depending on the Operating System installed, the affected package may be installed on the underlying Operating System supporting the Avaya IQ application. |
| CVLAN | Depending on the Operating System installed, the affected package may be installed on the underlying Operating System supporting the CVLAN application. |
| 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. |
| Avaya Integrated Management Suite (IMS) | Depending on the Operating System installed, the affected package may be installed on the underlying Operating System supporting the IMS application. |
| Avaya Aura® Presence Services | Depending on the Operating System installed, the affected package may be installed on the underlying Operating System supporting the PS 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 - June 16, 2015 - Initial Statement issued.
V 2.0 - October 27, 2015 - Updated AES, AS5300, CM, one-X CES, PS, SM, SMGR, SP
and US affected versions and actions.
V 3.0 - May 20, 2016 - Updated AAC and PC affected versions and actions.
V 4.0 - August 26, 2016 - Updated MX, MN and Messaging affected versions and actions.
V 5.0 - May 25, 2017 - Updated IQ 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
securityalerts@avaya.com.
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.