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 the Datagram Transport Layer Security (DTLS) protocol implementation in OpenSSL leaked timing information when performing certain operations. A remote attacker could possibly use this flaw to retrieve plain text from the encrypted packets by using a DTLS server as a padding oracle. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-4108 to this issue.
A double free flaw was discovered in the policy checking code in OpenSSL. A remote attacker could use this flaw to crash an application that uses OpenSSL by providing an X.509 certificate that has specially-crafted policy extension data. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-4109 to this issue.
An information leak flaw was found in the SSL 3.0 protocol implementation in OpenSSL. Incorrect initialization of SSL record padding bytes could cause an SSL client or server to send a limited amount of possibly sensitive data to its SSL peer via the encrypted connection. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-4576 to this issue.
It was discovered that OpenSSL did not limit the number of TLS/SSL handshake restarts required to support Server Gated Cryptography. A remote attacker could use this flaw to make a TLS/SSL server using OpenSSL consume an excessive amount of CPU by continuously restarting the handshake. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-4619 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||Low||Upgrade to 6.2 or later.|
|Avaya Aura® Application Server 5300:
||2.0 without Patch Bundle 26 or later.||Low||Upgrade to 2.0 PB26 or later.|
|Avaya Aura® Communication Manager||4.x, 5.x, 6.0.x, 6.2.x||Low||Upgrade to 6.3 or later.|
|Avaya Communication Server 1000:
||7.0, 7.5||Low||Upgrade to 7.6 or later.|
|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 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 Aura® Messaging||6.0.x thru 6.2||Low||Upgrade to 6.3 or later.|
|Avaya Aura® Presence Services||6.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 Proactive Contact||5.0, 5.0.1||Low||Upgrade to 5.1 or later.|
|Avaya Aura® Session Manager||1.x, 5.x, 6.0.x, 6.1.x, 6.2||Medium||Upgrade to 6.2.1 or later.|
|Avaya Aura® System Manager||5.2, 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 1.x, 6.0.x, upgrade to 6.2 then install patch 184.108.40.206.9 or later.
For 6.2, install patch 220.127.116.11.9 or later.
|Avaya Aura® Communication Manager Utility Services||6.0, 6.1, 6.2||Low||For 6.0, 6.1 upgrade to 6.2 then install patch 18.104.22.168.15 or later
For 6.2, install patch 22.214.171.124.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 rated a low risk for all product as DTLS and SCG are not used by default.|
||This is rated a low risk due to limited memory leak thru an encrypted connection.|
||This are rated a low risk for AES, AS 5300, CM, CSE, IP Office AS, IQ, AAM, PS, PC,SMGR, CMUS, VP as no critical system or processes are affected.
This is rated a medium risk for ASM due to the possibility of a partial Denial of Service (DoS).
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 10, 2012 - Initial Statement issued.
V 2.0 - December 7, 2012 - Changed affected versions and actions for AS5300, SP and VP.
V 3.0 - January 3, 2013 - Changed affected versions and actions for SMGR and CMUS.
V 4.0 - March 19, 2013 - Changed PC affected versions and actions.
V 5.0 - May 8, 2013 - Changed CM affected versions and actions and CS1000 actions.
V 6.0 - July 22, 2015 - Changed CSE, IQ, IPOAS, and Messaging affected versions and actions.
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.