Network Security Services (NSS) is a set of libraries designed to support the development of security-enabled client and server applications.
It was found that the Malaysia-based Digicert Sdn. Bhd. subordinate Certificate Authority (CA) issued HTTPS certificates with weak keys. This update renders any HTTPS certificates signed by that CA as untrusted. This covers all uses of the certificates, including SSL, S/MIME, and code signing. Note: Digicert Sdn. Bhd. is not the same company as found at digicert.com. (BZ#751366)
More information about this vulnerability can be found in the security advisory issued by Red Hat:
|Product:||Affected Version(s):||Risk Level:||Actions:|
|Avaya Aura® Application Enablement Services||5.2, 5.2.1, 5.2.2, 5.2.3, 6.1.x||Low||For customers running Application Enablement Services 5.2.3 or earlier, upgrade to Application Enablement Services 5.2.4 or later.
For customers running Application Enablement Services 6.1.x, upgrade to Application Enablement Services 6.2 or later
|Avaya Aura® Application Server 5300:
||2.0 including PB1 through PB18||Low||Upgrade to Application Server 5300 2.0 PB19 or later.|
|Avaya Aura® Communication Manager||5.x, 6.0.x||Low||Upgrade to Communication Manager 6.2 or later.|
|Avaya Communication Server 1000:
||6.x, 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 Standard Edition||6.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 that customers migrate to one of Avaya's conferencing solutions including Aura® Conferencing 8.0 or later.|
|Avaya Aura® Experience Portal||6.0||Low||Upgrade to Experience Portal 6.2 or later|
|Avaya IP Office Application Server||6.x, 7.x, 8.x||Low||Upgrade to IP Office Application Server 9.0 or later.|
|Avaya IQ||5.x||Low||See recommended actions below. This issue will be addressed in accordance with section five of Avaya's Product Security Vulnerability Response Policy|
|Avaya Message Networking||5.2 thru 5.2.4||Low||Upgrade to Message Networking 5.2.5 or later.|
|Avaya Aura® Messaging||6.0.x, 6.1.x||Low||Upgrade to Messaging 6.2 or later.|
|Avaya Messaging Storage Server||5.2 thru 5.2.13||Low||Upgrade to Messaging Storage Server 5.2.14 or later.|
|Avaya Aura® Presence Services||6.0.x, 6.1, 6.1.1||Low||Upgrade to Presence Services 6.1.2 or later.|
|Avaya Proactive Contact||5.0||Low||Upgrade to Proactive Contact 5.1 or later.|
|Avaya Aura® Session Manager||1.x, 5.2.x, 6.0.x, 6.1.x, 6.2||Low||Upgrade to Session Manager 6.2.1 or later.|
|Avaya Aura® System Manager||5.x, 6.0.x, 6.1.x, 6.2.x||Low||Upgrade to System Manager 6.3 or later.|
|Avaya Aura® System Platform||1.x, 6.0 thru 6.2.x||Low||Upgrade to System Platform 6.3 or later.|
|Avaya Aura® Communication Manager Utility Services||6.0, 6.1, 6.2||Low||Upgrade to Utility Services 6.2 then install patch 188.8.131.52.15 or later.|
|Avaya Voice Portal||5.0.x, 5.1, 5.1.1, 5.1.2,||Low||Upgrade to Avaya Enterprise Linux for 5.1.3 and 5.1.3 or later.|
Recommended Actions for System Products:
Avaya strongly recommends that customers follow 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 customers should not modify the System Product operating system or application 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 a low on AES, AS5300, CM, CSE, EP, IPO AS, IQ, MN,
Messaging, MSS, PS, PC, SM, SMGR, SP, CMUS, VP as no critical
applications or processes would be affected.
This is rated a none on CS1000 because the library is not used for certificate management.
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 4.x/5.x||Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the AES application.|
|CVLAN||Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the CVLAN application.|
|Avaya Aura® Experience Portal||Depending on the Operating System provided by customers, 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 provided by customers, the affected package may be installed on the underlying Operating System supporting the IMS application.|
|Avaya Aura® Presence Services||Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the PS application.|
|Avaya Aura® System Manager 1.0||Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the SMGR application.|
|Avaya Voice Portal||Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the VP application.|
Recommended Actions for Software-Only Products:
In the event that the affected package is installed, Avaya recommends that customers follow 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 - December 19, 2011 - Initial Statement issued.
V 2.0 - April 5, 2012 - Updated AS 5300, CM and SM affected version and actions.
V 3.0 - December 13, 2012 - Updated AES, EP, PS, SMGR and VP affected versions and actions.
V 4.0 - January 2, 2013 - Updated MN, AAM and CMUS affected versions and actions.
V 5.0 - February 6, 2013 - Updated MSS affected versions and actions.
V 6.0 - March 19, 2013 - Updated PC and VP actions.
V 7.0 - March 25, 2015 -Updated actions for Conferencing SE and CS1K and affected versions and actions for IP Office and SP.
Send information regarding any discovered security problems with Avaya products to either the contact noted in the product's documentation or email@example.com.
Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.
© 2011 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.