- Issued:
- 2017-03-23
- Updated:
- 2017-03-23
RHSA-2017:0484 - Moderate: Red Hat Gluster Storage 3.2.0 security, bug fix, and enhancement update
Synopsis
Moderate: Red Hat Gluster Storage 3.2.0 security, bug fix, and enhancement update
Type/Severity
Security Advisory: Moderate
Topic
An update is now available for Red Hat Gluster Storage 3.2 on Red Hat Enterprise Linux 6.
Red Hat Product Security has rated this update as having a security impact of Moderate. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.
Description
Red Hat Gluster Storage is a software only scale-out storage solution that provides flexible and affordable unstructured data storage. It unifies data storage and infrastructure, increases performance, and improves availability and manageability to meet enterprise-level storage challenges.
The following packages have been upgraded to a later upstream version: glusterfs (3.8.4), redhat-storage-server (3.2.0.3). (BZ#1362373)
Security Fix(es):
- It was found that glusterfs-server RPM package would write file with predictable name into world readable /tmp directory. A local attacker could potentially use this flaw to escalate their privileges to root by modifying the shell script during the installation of the glusterfs-server package. (CVE-2015-1795)
This issue was discovered by Florian Weimer of Red Hat Product Security.
Bug Fix(es):
-
Bricks remain stopped if server quorum is no longer met, or if server quorum is disabled, to ensure that bricks in maintenance are not started incorrectly. (BZ#1340995)
-
The metadata cache translator has been updated to improve Red Hat Gluster Storage performance when reading small files. (BZ#1427783)
-
The 'gluster volume add-brick' command is no longer allowed when the replica count has increased and any replica bricks are unavailable. (BZ#1404989)
-
Split-brain resolution commands work regardless of whether client-side heal or the self-heal daemon are enabled. (BZ#1403840)
Enhancement(s):
-
Red Hat Gluster Storage now provides Transport Layer Security support for Samba and NFS-Ganesha. (BZ#1340608, BZ#1371475)
-
A new reset-sync-time option enables resetting the sync time attribute to zero when required. (BZ#1205162)
-
Tiering demotions are now triggered at most 5 seconds after a hi-watermark breach event. Administrators can use the cluster.tier-query-limit volume parameter to specify the number of records extracted from the heat database during demotion. (BZ#1361759)
-
The /var/log/glusterfs/etc-glusterfs-glusterd.vol.log file is now named /var/log/glusterfs/glusterd.log. (BZ#1306120)
-
The 'gluster volume attach-tier/detach-tier' commands are considered deprecated in favor of the new commands, 'gluster volume tier VOLNAME attach/detach'. (BZ#1388464)
-
The HA_VOL_SERVER parameter in the ganesha-ha.conf file is no longer used by Red Hat Gluster Storage. (BZ#1348954)
-
The volfile server role can now be passed to another server when a server is unavailable. (BZ#1351949)
-
Ports can now be reused when they stop being used by another service. (BZ#1263090)
-
The thread pool limit for the rebalance process is now dynamic, and is determined based on the number of available cores. (BZ#1352805)
-
Brick verification at reboot now uses UUID instead of brick path. (BZ#1336267)
-
LOGIN_NAME_MAX is now used as the maximum length for the slave user instead of __POSIX_LOGIN_NAME_MAX, allowing for up to 256 characters including the NULL byte. (BZ#1400365)
-
The client identifier is now included in the log message to make it easier to determine which client failed to connect. (BZ#1333885)
Solution
For details on how to apply this update, which includes the changes described in this advisory, refer to:
https://access.redhat.com/articles/11258
Affected Products
| Product | Version | Arch |
|---|---|---|
| Red Hat Gluster Storage Server for On-premise | 3 | x86_64 |
| Red Hat Enterprise Linux Server | 6 | x86_64 |
Updated Packages
- glusterfs-client-xlators-3.8.4-18.el6.x86_64.rpm
- glusterfs-cli-3.8.4-18.el6.x86_64.rpm
- glusterfs-ganesha-3.8.4-18.el6rhs.x86_64.rpm
- glusterfs-rdma-3.8.4-18.el6rhs.x86_64.rpm
- python-gluster-3.8.4-18.el6rhs.noarch.rpm
- glusterfs-events-3.8.4-18.el6rhs.x86_64.rpm
- glusterfs-libs-3.8.4-18.el6.x86_64.rpm
- python-gluster-3.8.4-18.el6.noarch.rpm
- glusterfs-libs-3.8.4-18.el6rhs.x86_64.rpm
- glusterfs-api-devel-3.8.4-18.el6.x86_64.rpm
- glusterfs-fuse-3.8.4-18.el6.x86_64.rpm
- glusterfs-3.8.4-18.el6.x86_64.rpm
- glusterfs-3.8.4-18.el6rhs.x86_64.rpm
- glusterfs-geo-replication-3.8.4-18.el6rhs.x86_64.rpm
- redhat-storage-server-3.2.0.3-1.el6rhs.src.rpm
- glusterfs-api-3.8.4-18.el6.x86_64.rpm
- glusterfs-devel-3.8.4-18.el6.x86_64.rpm
- glusterfs-server-3.8.4-18.el6rhs.x86_64.rpm
- glusterfs-api-devel-3.8.4-18.el6rhs.x86_64.rpm
- glusterfs-debuginfo-3.8.4-18.el6rhs.x86_64.rpm
- glusterfs-client-xlators-3.8.4-18.el6rhs.x86_64.rpm
- redhat-storage-server-3.2.0.3-1.el6rhs.noarch.rpm
- glusterfs-debuginfo-3.8.4-18.el6.x86_64.rpm
- glusterfs-cli-3.8.4-18.el6rhs.x86_64.rpm
- glusterfs-3.8.4-18.el6rhs.src.rpm
- glusterfs-fuse-3.8.4-18.el6rhs.x86_64.rpm
- glusterfs-devel-3.8.4-18.el6rhs.x86_64.rpm
- glusterfs-3.8.4-18.el6.src.rpm
- glusterfs-api-3.8.4-18.el6rhs.x86_64.rpm
- glusterfs-rdma-3.8.4-18.el6.x86_64.rpm
Fixes
- This content is not included.BZ - 1200927
- This content is not included.BZ - 1362373
- This content is not included.BZ - 1375059
- This content is not included.BZ - 1382319
- This content is not included.BZ - 1403587
- This content is not included.BZ - 1403919
- This content is not included.BZ - 1404551
- This content is not included.BZ - 1424944
- This content is not included.BZ - 1425748
- This content is not included.BZ - 1432972
CVEs
References
- https://access.redhat.com/security/updates/classification/#moderate
- https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/3.2/html/3.2_release_notes/
Additional information
- The Red Hat security contact is This content is not included.secalert@redhat.com. More contact details at Security Contacts and Procedures.
- Offline Security Data data is available for integration with other systems. See Offline Security Data API to get started.