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.
The fix for CVE-2010-3847 introduced a regression in the way the dynamic loader expanded the $ORIGIN dynamic string token specified in the RPATH and RUNPATH entries in the ELF library header. A local attacker could use this flaw to escalate their privileges via a setuid or setgid program using such a library. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-0536 to this issue.
It was discovered that the glibc addmntent() function did not sanitize its input properly. A local attacker could possibly use this flaw to inject malformed lines into /etc/mtab via certain setuid mount helpers, if the attacker were allowed to mount to an arbitrary directory under their control. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-0296 to this issue.
It was discovered that the glibc fnmatch() function did not properly restrict the use of alloca(). If the function was called on sufficiently large inputs, it could cause an application using fnmatch() to crash or, possibly, execute arbitrary code with the privileges of the application. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-1071 to this issue.
It was discovered that the locale command did not produce properly escaped output as required by the POSIX specification. If an attacker were able to set the locale environment variables in the environment of a script that performed shell evaluation on the output of the locale command, and that script were run with different privileges than the attacker's, it could execute arbitrary code with the privileges of the script. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-1095 to this issue.
ld.so in the GNU C Library (aka glibc or libc6) 2.13 and earlier expands the $ORIGIN dynamic string token when RPATH is composed entirely of this token, which might allow local users to gain privileges by creating a hard link in an arbitrary directory to a (1) setuid or (2) setgid program with this RPATH value, and then executing the program with a crafted value for the LD_PRELOAD environment variable, a different vulnerability than CVE-2010-3847 and CVE-2011-0536. NOTE: it is not expected that any standard operating-system distribution would ship an applicable setuid or setgid program. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-1658 to this issue.
Integer overflow in posix/fnmatch.c in the GNU C Library (aka glibc or libc6) 2.13 and earlier allows context-dependent attackers to cause a denial of service (application crash) via a long UTF8 string that is used in an fnmatch call with a crafted pattern argument, a different vulnerability than CVE-2011-1071. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-1659 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.2.x, 6.1||Medium||Upgrade to 6.1.1 or later.|
|Avaya Aura® Application Server 5300:
||2.0||Medium||Upgrade to 2.0 PB1 or later.|
|Avaya Aura® Communication Manager||6.0.x||Low||Upgrade to 6.2 or later.|
|Avaya Communication Server 1000:
||6.0, 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||Medium||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.0, 6.1, 7.0||Medium||Upgrade to 8.0 or later.|
|Avaya IQ||5.2 thru 5.2.5||Medium||Upgrade to 5.2.6 and install Patch 2 or later.|
|Avaya Aura® Presence Services||6.0, 6.1, 6.1.1||Medium||Upgrade to 6.1.2 or later.|
|Avaya Aura® Session Manager||1.1, 5.2.x, 6.0.x, 6.1 thru 6.1.2||Medium||Upgrade to 6.1.3 or later.|
|Avaya Aura® System Manager||5.2.x,6.0.x, 6.1 thru 6.1.3||Medium||Upgrade to 6.1.4 or later.|
|Avaya Aura® System Platform||1.1, 6.0 thru 6.0 SP5||Medium||Install patch 126.96.36.199.3 or later.|
|Avaya Voice Portal||5.0.x, 5.1, 5.1.1||Medium||Upgrade to Avaya Enterprise Linux for Voice Portal 5.1 SP2 and Voice Portal 5.2 SP2 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:
|These are rated a Low for CM and CS1000 because exploiting these vulnerabilities would require local access from an authenticated account with administrative privileges.
These are a medium risk for AES, AS5300, Conferencing, IQ, Presence, Session Manager, System Manager, System Platform and Voice Portal due to the potential for privilege escalation.
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® 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.|
|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 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 - June 24, 2011 - Initial Statement issued.
V 2.0 - February 5, 2013 - Updated AES, AS5300, CM, CS1000, IPO AS, PS, SM, SMGR, SP and VP affected versions and actions.
V 3.0 - July 3, 2013 - Updated CSE actions.
V 4.0 - June 26, 2015 - Updated IQ affected versions and actions, and set 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.
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.