Print | Rate this content

HPSBST03598 rev.1 - HPE 3PAR OS using glibc, Remote Denial of Service (DoS), Arbitrary Code Execution

SUPPORT COMMUNICATION - SECURITY BULLETIN

Document ID: c05128937

Version: 1

HPSBST03598 rev.1 - HPE 3PAR OS using glibc, Remote Denial of Service (DoS), Arbitrary Code Execution
NOTICE: The information in this Security Bulletin should be acted upon as soon as possible.

Release Date: 2016-05-11

Last Updated: 2016-05-11


Potential Security Impact: Remote Arbitrary Code Execution, Denial of Service (DoS)

Source: Hewlett Packard Enterprise, HPE Product Security Response Team

VULNERABILITY SUMMARY

HPE 3PAR OS has addressed stack based buffer overflows in glibc's implementation of getaddrinfo(). This vulnerability could be remotely exploited to cause Denial of Service (DoS) or allow execution of arbitrary code on the host with the permissions of a user running glibc library.

References:
  • CVE-2015-7547
  • PSRT110105

SUPPORTED SOFTWARE VERSIONS*: ONLY impacted versions are listed.

HPE 3PAR OS versions 3.1.3 and later, prior to 3.2.1 MU5 and 3.2.2 MU2 using glibc

BACKGROUND

CVSS 2.0 Base Metrics
Reference
Base Vector
Base Score
CVE-2015-7547
(AV:N/AC:M/Au:N/C:P/I:P/A:P)
6.8
Information on CVSS is documented in HP Customer Notice: HPSN-2008-002

RESOLUTION

HPE has provided the following software updates and mitigation information to resolve the vulnerability in 3PAR OS using glibc.

  • 3PAR OS 3.2.1 MU5 and 3.2.2 MU2

    • HPE recommends prior impacted versions update to 3PAR OS 3.2.1 MU 5 or 3.2.2 MU2.
    • glibc has been updated in these releases to resolve the glibc vulnerability.
  • 3PAR OS 3.1.3 is also vulnerable but will not be fixed.

    Mitigation: The best protection to guard against exploitation of this vulnerability is to securely configure and operate the storage array in accordance with the HPE 3PAR Configuration Guidelines documentation. Please contact HPE Technical Support for assistance.

HISTORY
Version:1 (rev.1) - 11 May 2016 Initial release

Third Party Security Patches: Third party security patches that are to be installed on systems running Hewlett Packard Enterprise (HPE) software products should be applied in accordance with the customer's patch management policy.

Support: For issues about implementing the recommendations of this Security Bulletin, contact normal HPE Services support channel. For other issues about the content of this Security Bulletin, send e-mail to security-alert@hpe.com.

Report: To report a potential security vulnerability with any HPE supported product, send Email to: security-alert@hpe.com

Subscribe: To initiate a subscription to receive future HPE Security Bulletin alerts via Email: http://www.hpe.com/support/Subscriber_Choice

Security Bulletin Archive: A list of recently released Security Bulletins is available here: http://www.hpe.com/support/Security_Bulletin_Archive

Software Product Category: The Software Product Category is represented in the title by the two characters following HPSB.

3C = 3COM
3P = 3rd Party Software
GN = HP General Software
HF = HP Hardware and Firmware
MU = Multi-Platform Software
NS = NonStop Servers
OV = OpenVMS
PV = ProCurve
ST = Storage Software
UX = HP-UX

©Copyright 2016 Hewlett Packard Enterprise Company, L.P.
Hewlett Packard Enterprise Company shall not be liable for technical or editorial errors or omissions contained herein. The information provided is provided "as is" without warranty of any kind. To the extent permitted by law, neither HPE nor its affiliates, subcontractors or suppliers will be liable for incidental, special or consequential damages including downtime cost; lost profits; damages relating to the procurement of substitute products or services; or damages for loss of data, or software restoration. The information in this document is subject to change without notice. Hewlett Packard Enterprise Company and the names of Hewlett Packard Enterprise products referenced herein are trademarks of Hewlett Packard Enterprise Company in the United States and other countries. Other product and company names mentioned herein may be trademarks of their respective owners.

Provide feedback

Please rate the information on this page to help us improve our content. Thank you!