Network Security Services (NSS) is a set of libraries designed to support the cross-platform development of security-enabled client and server applications.
The nss-util packages provide utilities for use with the Network Security Services (NSS) libraries.
Multiple buffer handling flaws were found in the way NSS handled cryptographic data from the network. A remote attacker could use these flaws to crash an application using NSS or, possibly, execute arbitrary code with the permission of the user running the application. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2016-2834 to this issue.
A NULL pointer dereference flaw was found in the way NSS handled invalid Diffie-Hellman keys. A remote client could use this flaw to crash a TLS/SSL server using NSS. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2016-5285 to this issue.
It was found that Diffie Hellman Client key exchange handling in NSS was vulnerable to small subgroup confinement attack. An attacker could use this flaw to recover private keys by confining the client DH key to small subgroup of the desired group. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2016-8635 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, 7.0 including 7.0.1 Linux Security Update 2||Medium||Update to 7.0.1 Linux Security Update 3 or later.|
|Avaya Aura® Application Server 5300:
||3.0 through 3.0 SP13||Medium||Upgrade to 3.0 SP13.4 or later.|
|Avaya IQ||5.2.x||Medium||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 Breeze™ Platform||3.0 through 3.2||Medium||Upgrade to 3.3 or later.|
|Avaya CMS||R17 through R17 R6, R18 through R126.96.36.199||Low||For R17, upgrade to R17 R7 or later.
For R18, upgrade to R18.0.1 or later.
|Avaya Aura® Communication Manager||6.x, 7.0 including 7.0 Security Service Pack 3||Low||Update to 7.0 Security Service Pack 4 or later.|
|Avaya Aura® Communication Manager Messaging||7.0 through 7.0 Security Service Pack 3||Low||Update to 7.0 Security Service Pack 4 or later.|
|Avaya Communication Server 1000:
||7.x||None||See recommended actions and Mitigating Factors table below. This advisory will not be addressed as no further releases are planned.|
|Avaya Aura® Conferencing||7.x, 8.0 through 8.0 SP9||Medium||Upgrade to 8.0 SP10 or later.|
|Avaya Aura® Experience Portal||6.x, 7.0 through 7.1||Medium||Upgrade to 7.2 or later.|
|Avaya IP Office Server Edition||8.1, 9.x, 10.0.x||Medium||Upgrade to 10.1 or later.|
|Avaya IP Office Application Server||8.1, 9.x, 10.0.x||Medium||Upgrade to 10.1 or later.|
|Avaya Meeting Exchange||6.2 through 6.2 SP3||Medium||Upgrade to 6.2 SP4 or later.|
|Avaya Message Networking||5.x, 6.3.x||Low||See recommended actions and Mitigating Factors table below. This advisory will not be addressed as no further releases are planned.|
|Avaya Aura® Messaging||6.3 through 6.3.3 SP6||Low||Upgrade to 6.3.3 SP7 or later.|
|Avaya one-X® Client Enablement Services||6.2 through 6.2 SP5||Medium||Upgrade to 6.2 SP6 or later.|
|Avaya Proactive Contact||5.0 through 5.1.2||Medium||Upgrade to 5.1.3 or later.|
|Avaya Session Border Controller for Enterprise||6.x, 7.0 through 7.1||Medium||Upgrade to 7.2 or later.|
|Avaya Aura® Session Manager||6.3 through 6.3.18, 7.0.x||Medium||For 6.3, upgrade to 6.3.19 or later.
For 7.0.x, upgrade to 7.1 or later.
|Avaya Aura® System Manager||6.3 through 6.3.18, 7.0.x||Low||For 6.3, upgrade to 6.3.19 or later.
For 7.0.x, upgrade to 7.1 or later.
|Avaya Aura® System Platform||6.3.x, 6.4.0||Medium||Upgrade to 6.4.1 or later.|
|Avaya Aura® Utility Services||6.3 through 6.3.14, 7.0 through 188.8.131.52||Medium||For 6.3, upgrade to 6.3.15 or later.
For 7.0 upgrade to 184.108.40.206 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:
|This is rated a no risk for Communication Server 1000 because NSS tokens are not used with this product.
This is rated a Low risk for CMS due to the server not being exposed to the external network.
These are rated a Low risk for CM, CMM, MN, Messaging, and SMGR because these products do not use NSS for cryptographic operations, it is installed only to satisfy package dependencies.
These are rated a Medium risk for all other products because of the potential to crash applications compiled against the NSS library.
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.
|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 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 - December 22, 2016 - Initial Statement issued.
V 2.0 - September 16, 2018 - Updated affected versions and actions for all products 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@example.com.
Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.
© 2016 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.