OpenSSL is a toolkit that implements the Secure Sockets Layer (SSL), Transport Layer Security (TLS), and Datagram Transport Layer Security (DTLS) protocols, as well as a full-strength, general purpose cryptography library.
A race condition was found in the way OpenSSL handled ServerHello messages with an included Supported EC Point Format extension. A malicious server could possibly use this flaw to cause a multi-threaded TLS/SSL client using OpenSSL to write into freed memory, causing the client to crash or execute arbitrary code. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2014-3509 to this issue.
It was discovered that the OBJ_obj2txt() function could fail to properly NUL-terminate its output. This could possibly cause an application using OpenSSL functions to format fields of X.509 certificates to disclose portions of its memory. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2014-3508 to this issue.
A flaw was found in the way OpenSSL handled fragmented handshake packets. A man-in-the-middle attacker could use this flaw to force a TLS/SSL server using OpenSSL to use TLS 1.0, even if both the client and the server supported newer protocol versions. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2014-3511 to this issue.
Multiple flaws were discovered in the way OpenSSL handled DTLS packets. A remote attacker could use these flaws to cause a DTLS server or client using OpenSSL to crash or use excessive amounts of memory. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2014-3505, CVE-2014-3506 and CVE-2014-3507 to these issues.
A NULL pointer dereference flaw was found in the way OpenSSL performed a handshake when using the anonymous Diffie-Hellman (DH) key exchange. A malicious server could cause a DTLS client using OpenSSL to crash if that client had anonymous DH cipher suites enabled. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2014-3510 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 R3 | Low | Upgrade to R17 R4 or later. |
| Avaya Aura® Collaboration Environment | 2.x thru 3.0 SP3 | Low | Upgrade to 3.0 SP4 or later. |
| Avaya Aura® Experience Portal | 6.x, 7.x | Low | For 6.0 SP1 and SP2, upgrade to 6.0 SP3 and Avaya Linux for 6.0 SP3, and install
6.0 SP3 Security Updates. For 6.0 SP3, install 6.0 SP3 Security Updates. For 7.0, install 7.0 Security Updates. For 7.0.1, install 7.0.1 Security Updates. |
| Avaya IP Office Server Edition | 8.1 thru 9.1.3 | Low | Upgrade to 9.1.4 or later. |
| Avaya IP Office Application Server | 9.0 thru 9.1.3 | Low | Upgrade to 9.1.4 or later. |
| Avaya one-X® Client Enablement Services | 6.2.x | None | See Mitigating Factors table below. |
| Avaya Aura® Session Manager | 6.3 thru 6.3.10 | Low | Upgrade to 6.3.11 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-3505 CVE-2014-3506 CVE-2014-3507 CVE-2014-3510 |
These are a Low risk for all listed products as DTLS is not used by default. There is no risk to one-X CES as the package was customized to prevent these issues. |
|
CVE-2014-3508 |
This is a Low risk for all listed products as the pretty printing function
is not used by default. There is no risk to one-X CES as the package was customized to prevent this issue. |
| CVE-2014-3509 | This is a Low risk for all listed products as EC point format extensions are
not used by default. There is no risk to one-X CES as the package was customized to prevent this issue. |
|
CVE-2014-3511 |
This is a Low risk for all listed products as anonymous Diffie-Hellman key
exchange is not used by default. There is no risk to one-X CES as the package was customized to prevent this issue. |
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 AND IS PROVIDED "AS IS". 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 - September 23, 2014 - Initial Statement issued.
V 2.0 - February 27, 2015 - Updated CMS, EP and SM affected versions and actions.
V 3.0 - July 2, 2015 - Updated CE affected versions and actions.
V 4.0 - October 15, 2015 - Updated IPOSE and IPOAS 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
securityalerts@avaya.com.
Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.
© 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.