glibc security update (RHSA-2012-0126)

Original Release Date: April 11, 2012
Last Revised: July 26, 2013
Number: ASA-2012-156
Risk Level: Low
Advisory Version: 7.0
Advisory Status: Interim

1. Overview:

The glibc packages contain the standard C libraries used by multiple programs on the system. These packages contain the standard C and the standard math libraries. Without these two libraries, a Linux system cannot function properly.

An integer overflow flaw, leading to a heap-based buffer overflow, was found in the way the glibc library read timezone files. If a carefully-crafted timezone file was loaded by an application linked against glibc, it could cause the application to crash or, potentially, execute arbitrary code with the privileges of the user running the application. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2009-5029 to this issue.

A flaw was found in the way the ldd utility identified dynamically linked libraries. If an attacker could trick a user into running ldd on a malicious binary, it could result in arbitrary code execution with the privileges of the user running ldd. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2009-5064 to this issue.

An integer overflow flaw, leading to a heap-based buffer overflow, was found in the way the glibc library loaded ELF (Executable and Linking Format) files. If a carefully-crafted ELF file was loaded by an application linked against glibc, it could cause the application to crash or, potentially, execute arbitrary code with the privileges of the user running the application. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-0830 to this issue.

It was found that the glibc addmntent() function, used by various mount helper utilities, did not handle certain errors correctly when updating the mtab (mounted file systems table) file. If such utilities had the setuid bit set, a local attacker could use this flaw to corrupt the mtab file. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-1089 to this issue.

A denial of service flaw was found in the remote procedure call (RPC) implementation in glibc. A remote attacker able to open a large number of connections to an RPC service that is using the RPC implementation from glibc, could use this flaw to make that service use an excessive amount of CPU time. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-4609 to this issue.

More information about these vulnerabilities can be found in the security advisory issued by Red Hat:

2. Avaya System Products using a modified version of RHEL5 with affected components/packages installed:

Product: Affected Version(s): Risk Level: Actions:
Avaya Aura® Application Enablement Services 5.x, 6.1.x Low Upgrade to Application Enablement Services 6.2 or later.
Avaya Aura® Application Server 5300:
  • SIP Core
2.0 without Patch Bundle PB26 or later. Low Upgrade to Application Server 5300 with PB26 or later.
Avaya Aura® Communication Manager 5.2.x, 6.0.x, 6.2.x Low Upgrade to Communication Manager 6.3 or later.
Avaya Communication Server 1000:
  • CS1000E
  • CS1000M
  • CS1000E/CS1000M Signaling Server
6.x, 7.x Low 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.0.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 Avaya Aura® Conferencing 7.0 or later.
Avaya IP Office Application Server 6.x, 7.x, 8.0 Low Upgrade to IP Office Application Server 8.1 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 Aura® Messaging 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 Aura® Presence Services 6.0.x, 6.1.x Low Upgrade to Presence Services 6.2 or later.
Avaya Proactive Contact 5.0.x Low Upgrade to Proactive Contact 5.1 or later.
Avaya Aura® Session Manager 1.x, 5.x, 6.1.x, 6.2 Low Upgrade to Session Manager 6.2 SP1 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.x, 6.2 Low System Platform 1.x, 6.0.x: Upgrade to System Platform 6.0.3 and install patch 6.0.3.9.3 or upgrade to System Platform 6.2.1 or later.
System Platform 6.2: Upgrade to System Platform 6.2.1 or later.
Avaya Aura® Communication Manager Utility Services 6.0.x, 6.1.x, 6.2 Low For 6.0 and 6.1, upgrade to Utility Services 6.2 and install Service Pack 6.2.5.0.15 or later.
For 6.2, install Service Pack 6.2.5.0.15 or later.
Avaya Voice Portal 5.0.x, 5.1 thru 5.1 SP2 Low Upgrade to Avaya Enterprise Linux for Voice Portal 5.1 SP3 and Voice Portal 5.1 SP3 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.

Mitigating Factors:

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:

Vulnerability Mitigating Factors
CVE-2009-5029
CVE-2009-5064
CVE-2010-0830
CVE-2011-1089
These are a low risk as they would required privileged account access.
CVE-2011-4609 This is a low risk as the RPC implementation from glibc is not used.

3. Avaya Software-Only Products:

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.

Product: Actions:
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.

4. Additional Information:

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.

5. Disclaimer:

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.

6. Revision History:

V 1.0 - April 11, 2012 - Initial Statement issued.
V 2.0 - August 3, 2012 - Updated AES, AS5300, IPOAS and SM affected versions and actions.
V 3.0 - September 13, 2012 - Updated SP and VP affected versions and actions.
V 4.0 - December 14, 2012 - Updated SMGR affected versions and actions.
V 5.0 - March 6, 2013 - Updated PC and CMUS affected versions and actions.
V 6.0 - May 24, 2013 - Updated CS1000 actions, CM and PS affected versions and actions.
V 7.0 - July 26, 2013 - Updated Conferencing SE actions.

Send information regarding any discovered security problems with Avaya products to either the contact noted in the product's documentation or securityalerts@avaya.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.