The glibc packages provide the standard C libraries (libc), POSIX thread libraries (libpthread), standard math libraries (libm), and the Name Server Caching Daemon (nscd) used by multiple programs on the system. Without these libraries, the Linux system cannot function correctly.
It was found that getaddrinfo() did not limit the amount of stack memory used during name resolution. An attacker able to make an application resolve an attacker-controlled hostname or IP address could possibly cause the application to exhaust all stack memory and crash. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2013-1914 to this issue.
A flaw was found in the regular expression matching routines that process multibyte character input. If an application utilized the glibc regular expression matching mechanism, an attacker could provide specially-crafted input that, when processed, would cause the application to crash. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2013-0242 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 thru 6.3 | Medium | For bundled and VMware offers, upgrade to 6.3.1 or later. For SP offer, upgrade to 6.3.3 or later. |
Avaya Aura® Application Server 5300:
|
2.x, 3.x | Medium | For 2.0 upgrade to 3.0 and install Service Pack 6 or later. For 3.0 install Service Pack 6 or later. |
| Avaya IQ | 5.2 thru 5.2.5 | Medium | Upgrade to 5.2.6 and install Patch 2 or later. |
| Avaya Aura® Communication Manager | 6.0 thru 6.3 | Low | For 6.0, 6.1, 6.2, upgrade to 6.3 and install CM 6.3 SSP 301 or later. For 6.3, install CM 6.3 SSP 301 or later. |
Avaya Communication Server 1000:
|
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 | 7.0 thru 7.2 SP2 | Low | Upgrade to 7.2 SP3 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 7.0 or later. |
| Avaya IP Office Application Server | 8.x | Medium | Upgrade to 9.0 or later. |
| Avaya Meeting Exchange | 6.2 thru 6.2 SP2 | Low | Upgrade to 6.2 SP3. |
| Avaya Aura® Messaging | 6.0 thru 6.2 | Low | Upgrade to 6.3 or later. |
| Avaya one-X® Client Enablement Services | 6.1.x | Medium | Upgrade to 6.2 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 thru 5.1 | Low | Upgrade to 5.1.1 or later. |
| Avaya Aura® Session Manager | 5.x, 6.0.x thru 6.2.x | Medium | Upgrade to 6.3 or later. |
| Avaya Aura® System Manager | 5.x, 6.0 thru 6.3.2 | Medium | Upgrade to 6.3.3 or later. |
| Avaya Aura® System Platform | 6.0 thru 6.3 | Low | Upgrade to 6.3.1 or later. |
| Avaya Aura® Utility Services | 6.0, 6.1, 6.2, 6.3 | Medium | For versions prior to 6.3, upgrade to 6.3 and install 6.3.1.0.20 or later. For 6.3, install 6.3.1.0.20 or later. |
| Avaya Voice Portal | 5.x | Medium | See recommended actions and Mitigating Factors table below. This advisory will not be addressed as there will be no further releases. It is recommended to upgrade to Avaya Aura® Experience Portal. |
Recommended Actions for System Products:
Avaya strongly recommends following the
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 the System Product operating system or
application should not be modified 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:
| Vulnerability | Mitigating Factors |
|---|---|
|
CVE-2013-0242 CVE-2013-1914 |
The risk is rated Low for CM, CS1000, Conferencing, Conferencing Standard Edition, Meeting Exchange, Messaging, Presence, Proactive Contact and System Platform
because exploitation of this vulnerability would require privileged user account access which would not provide additional capability. The risk is rated Medium for other products because exploitation of this vulnerability would require authenticated user interaction to potentially crash an application. |
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 installed, the affected package may be installed on the underlying Operating System supporting the AES application. |
| CVLAN | Depending on the Operating System installed, the affected package may be installed on the underlying Operating System supporting the CVLAN application. |
| Avaya Aura® Experience Portal | Depending on the Operating System installed, 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 installed, the affected package may be installed on the underlying Operating System supporting the IMS application. |
| Avaya Aura® Presence Services | Depending on the Operating System installed, 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 installed, 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 installed, the affected package may be installed on the underlying Operating System supporting the SMGR application. |
| Avaya Voice Portal | Depending on the Operating System installed, 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 following the 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 - August 13, 2013 - Initial Statement issued.
V 2.0 - June 8, 2015 - Updated affected versions and actions for AES, AS5300, CM, Conferencing, Messaging, One-X CES, Proactive Contact, SM, SMGR, SP, US and actions for IPOAS and VP.
V 3.0 - July 17, 2015 - Updated affected versions and actions for IQ.
V 4.0 - August 3, 2016 - Updated affected versions and actions for MX, PS 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 protected].
Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.
© 2013 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.