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.
A NULL pointer dereference flaw was found in the way OpenSSL parsed Secure/Multipurpose Internet Mail Extensions (S/MIME) messages. An attacker could use this flaw to crash an application that uses OpenSSL to decrypt or verify S/MIME messages. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2012-1165 to this issue.
A flaw was found in the PKCS#7 and Cryptographic Message Syntax (CMS) implementations in OpenSSL. An attacker could possibly use this flaw to perform a Bleichenbacher attack to decrypt an encrypted CMS, PKCS#7, or S/MIME message by sending a large number of chosen ciphertext messages to a service using OpenSSL and measuring error response times. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2012-0884 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||5.x, 6.1.x, 6.2, 6.3||Low||For 6.1.x and earlier, upgrade to 6.2 and install security patch 1 or later,
or upgrade to 6.3.1 or later.
For 6.2, install security patch 1 or later, or upgrade to 6.3.1 or later.
For 6.3, upgrade to 6.3.1 or later.
|Avaya Aura® Application Server 5300:
||2.0 including PB1 through PB25||Low||Upgrade to 2.0 PB26 or later.|
|Avaya Aura® Communication Manager||6.0.x, 6.2.x including SP1 through SP7||Low||For 6.0.x, upgrade to 6.2 and install SP7.1 or
later, or upgrade to 6.3 or later.
For 6.2, install SP7.1 or later, or upgrade to 6.3 or later.
|Avaya Communication Server 1000:
||6.x, 7.x||Low||There are no current plans to provide an upgrade to resolve this issue on the Communication Server 1000. See recommended actions and mitigating factors below.|
|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 7.0 or later.|
|Avaya Aura® Experience Portal||6.0, 6.0.1||Low||Upgrade to Avaya Enterprise Linux for 6.0.2 and 6.0.2 or later.|
|Avaya IP Office Application Server||6.x, 7.x, 8.x||Low||Upgrade to 9.0 or later.|
|Avaya IQ||5.2 thru 5.2.5||Low||Upgrade to 5.2.6 and install Patch 2 or later.|
|Avaya Meeting Exchange||5.x through 6.2.1||Low||Upgrade to 6.2.2 or later.|
|Avaya Aura® Messaging||6.0.x, 6.1.x, 6.2 including SP1 through SP3||Low||For 6.0.x and 6.1.x, upgrade to 6.2 and install CM 6.2 SP7.1 and 6.2 SP4 or
For 6.2, install CM 6.2 SP7.1 and 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||Low||Upgrade to 5.1 or later.|
|Avaya Aura® Session Manager||1.x, 5.x, 6.0.x, 6.1.x, 6.2, 6.2.1||Low||Upgrade to 6.2.2 or later.|
|Avaya Aura® SIP Enablement Services||5.x||Low||See recommended actions below. This advisory will not be addressed as no further releases are planned.|
|Avaya Aura® System Manager||5.x, 6.0.x, 6.1.x 6.2.x||Low||Upgrade to 6.3 or later.|
|Avaya Aura® System Platform||1.x, 6.0.x, 6.2||Low||For 6.0.x and earlier, upgrade to 18.104.22.168.3 and install patch 22.214.171.124.3 or
For 6.2, upgrade to 6.2.1 or later.
|Avaya Aura® Communication Manager Utility Services||6.0.x, 6.1.x, 6.2 through 126.96.36.199.15||Low||For 6.0 and 6.1, upgrade to 6.2 and install Service Pack
188.8.131.52.15 or later.
For 6.2, install Service Pack 184.108.40.206.15 or later.
|Avaya Voice Portal||5.0, 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 risk as no critical applications would be impacted or use CMS, PKCS#7, or S/MIME encrypted messages 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.
|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 Secure Access Link Gateway||Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the SAL Gateway 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 - May 29, 2012 - Initial Statement issued.
V 2.0 - August 29, 2012 - Changed AS5300, SM and SP affected versions and actions.
V 3.0 - September 19, 2012 - Changed SP and VP affected versions and actions.
V 4.0 - January 14, 2013 - Changed CS1000, EP, SMGR and CM US affected versions and actions.
V 5.0 - May 24, 2013 - Changed CM and PC affected versions and actions.
V 6.0 - June 26, 2013 - Changed Conferencing SE actions.
V 7.0 - October 29, 2013 - Changed AES affected versions and actions, and IPOAS actions.
V 8.0 - January 3, 2014 - Changed CM and Messaging affected versions and actions.
V 9.0 - April 1, 2015 - Changed Meeting Exchange affected versions and actions.
V 10.0 - July 6, 2015 - Updated IQ affected versions and actions.
V 11.0 - September 15, 2015 - Updated PS actions and set advisory to final.
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.
© 2012 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.