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 flaw was found in the way the TLS/SSL (Transport Layer Security/Secure Sockets Layer) protocols handled session renegotiation. A man-in-the-middle attacker could use this flaw to prefix arbitrary plain text to a client's session (for example, an HTTPS connection to a website). This could force the server to process an attacker's request as if authenticated using the victim's credentials. This update addresses this flaw by implementing the TLS Renegotiation Indication Extension, as defined in RFC 5746. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2009-3555 to this issue.
Refer to the following Knowledgebase article for additional details about the CVE-2009-3555 flaw: http://kbase.redhat.com/faq/docs/DOC-20491
It was found that browsers could accept certificates with MD2 hash signatures, even though MD2 is no longer considered a cryptographically strong algorithm. This could make it easier for an attacker to create a malicious certificate that would be treated as trusted by a browser. OpenSSL now disables the use of the MD2 algorithm inside signatures by default. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2009-2409 to this issue.
An input validation flaw was found in the handling of the BMPString and UniversalString ASN1 string types in OpenSSL's ASN1_STRING_print_ex() function. An attacker could use this flaw to create a specially-crafted X.509 certificate that could cause applications using the affected function to crash when printing certificate contents. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2009-0590 to this issue.
More information about these vulnerabilities can be found in the security advisory issued by RedHat Linux:
|Product:||Affected Version(s):||Risk Level:||Actions:|
|Avaya Aura™ Application Enablement Services||4.2.3 and earlier||Low||Upgrade to AES 4.2.4 or later.|
|Avaya Aura™ Communication Manager||4.x, 5.0 through 5.2.1 SSP1||Low||Upgrade to CM 5.2.1 with SSP2 or later installed or upgrade to CM 6.0.1 or later.|
|Avaya Intuity AUDIX LX||2.0 including 2.0 SP1 and SP2||Low||This advisory will not be addressed as no further releases are planned.|
|Avaya Meeting Exchange||5.0 thru 5.2 SP2||Low||Upgrade to MX 6.2 or later.|
|Avaya Message Networking||3.1, 5.2 thru 5.2.3||Low||Upgrade to MN 5.2.4 or later.|
|Avaya Messaging Storage Server||4.x, 5.0, 5.1.x, 5.2 thru 5.2.8||Low||Upgrade to MSS 5.2.9 or later.|
|Avaya Aura™ SIP Enablement Services||4.x, 5.x||Low||This advisory will not be addressed as no further releases are planned.|
|Avaya Proactive Contact||4.0 thru 4.2||Low||Upgrade to PC 4.2.1 or later.|
|Avaya Voice Portal||4.1 SP3 and earlier||Low||Upgrade to VP 4.1 SP4 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's product and the surrounding network from this potential vulnerability may be mitigated by ensuring these practices are implemented until such time as a product update is available or the recommended action is applied. Further restrictions as deemed necessary based on the customer's security policies may be required during this interim period.
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 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™ 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.|
|Voice Portal||Depending on the Operating System provided by customers, the affected package may be installed on the underlying Operating System supporting the Voice Portal 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 RedHat 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 - April 22, 2010 - Initial Statement issued.
V 2.0 - September 15, 2010 - Updated CM Actions.
V 3.0 - October 11, 2010 - Updated CM Actions.
V 4.0 - December 14, 2010 - Updated AES & VP Affected Versions & Actions, updated CM Actions.
V 5.0 - March 20, 2013 - Updated MN, MSS, MX, PC Affected Versions and Actions and Advisory Status 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.
© 2010 Avaya Inc. All Rights Reserved. All trademarks identified by the ® or ™ are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners.