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.
A heap-based buffer overflow was found in glibc's __nss_hostname_digits_dots() function, which is used by the gethostbyname() and gethostbyname2() glibc function calls. A remote attacker able to make an application call either of these functions could use this flaw to execute arbitrary code with the permissions of the user running the application. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2015-0235 to this issue.
More information about this vulnerability can be found in the security advisory issued by Red Hat:
|Product:||Affected Version(s):||Risk Level:||Actions:|
|Avaya Aura® Application Enablement Services||6.3 through 6.3.3||Medium||Upgrade to 6.3.3 and install Linux Security Update Patch 2 or later as described in PSN004416u..|
|Avaya Aura® Application Server 5300:
||2.x through 3.0 SP10||Medium||For 2.x, upgrade to 3.0 and install SP10.1 or later.
For 3.0, install SP10.1 or later.
|Avaya IQ||5.2.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 to migrate to Avaya Oceanalytics for Elite.|
|Avaya Aura® Communication Manager||6.0 through 6.3||Medium||For 6.3, install Security Service Pack 6 or later.
For 6.2 and earlier, upgrade to 6.3 and install Security Service Pack 6 or later.
|Avaya Communication Server 1000:
||7.x||Medium||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 through 7.2 SP6||Medium||Upgrade to 7.2 SP7 or later.|
|Avaya IP Office Application Server||8.x||Medium||Upgrade to 9.1.4 or later.|
|Avaya Meeting Exchange||5.2.x, 6.2 through 6.2 SP2||Medium||Upgrade to 6.2 SP3 or later.|
|Avaya Message Networking||5.2.x through 6.3 specifically prior to Patch 3||Low||Upgrade to 6.3 Patch 3 or later.|
|Avaya Aura® Messaging||6.3 through 6.3.2||Medium||Upgrade to 6.3.3 or later.|
|Avaya one-X® Client Enablement Services||6.1.x||Medium||Upgrade to 6.2 SP4 or later.|
|Avaya Aura® Presence Services||6.x||Medium||Upgrade to Aura Presence Services 7.1 or later. Further information about this version, as well as the overall Aura 7.1 release, is available on support.avaya.com.|
|Avaya Proactive Contact||5.1 through 5.1.1||Medium||Upgrade to 5.1.2 or later.|
|Avaya Aura® Session Manager||6.0.x through 6.2.x||Medium||Upgrade to 6.3.13 or later.|
|Avaya Aura® System Manager||6.0 through 6.3.12||Medium||Upgrade to 6.3.13 or later.|
|Avaya Aura® System Platform||6.3 through 6.3.6||Medium||Upgrade to 6.3.7 or later.|
|Avaya Aura® Utility Services||6.3 through 6.3.8||Medium||Upgrade to 6.3.9 or later.|
Recommended Actions for System Products:
Avaya strongly recommends following 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:
||The risk is rated Medium for all listed products because the exploit would require local account access. Remote attack may not be possible, because either the DNS server is not running or
the products sanitize the input and provide name resolution to trusted hosts only within the enterprise. Additionally, the known affected programs or utilities are not used and additional protection mechanisms are in place to
protect the products from remote exploit.
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||Depending on the Operating System installed, the affected package may be installed on the underlying Operating System supporting the AES application.|
|Avaya IQ||Depending on the Operating System installed, the affected package may be installed on the underlying Operating System supporting the Avaya IQ 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.|
Recommended Actions for Software-Only Products:
In the event that the affected package is installed, Avaya recommends following 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, IS PROVIDED "AS IS", AND IS APPLICABLE ONLY TO PRODUCT VERSIONS ELIGIBLE FOR MANUFACTURER SUPPORT IN ACCORDANCE WITH AVAYA PRODUCT LIFE CYCLE POLICY. 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 14, 2015 - Initial Statement issued.
V 2.0 - May 21, 2015 - Updated affected versions and actions for AES, AS5300, CM, SM, SMGR and Utility Services.
V 3.0 - December 6, 2017 - Updated affected versions and actions for all other products and set the advisory status to Final.
Avaya customers or Business Partners should report any security issues found with Avaya products via the standard support process.
Independent security researchers can contact Avaya at email@example.com.
Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.
© 2015 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.