The Gluster filesystem during a file rename only validates that the source path exists within the mounted volume. This can allow an attacker to rename files in locations outside a mounted volume.
Acknowledgments: Name: Michael Hanselmann (hansmi.ch)
Statement: This issue did not affect Red Hat Enterprise Linux 6 and 7 as the flaw is present in glusterfs-server, which is not shipped there. This flaw affects glusterfs versions included in Red Hat Virtualization 4 Hypervisor. However, in recommended configurations, the vulnerability is only exposed to hypervisor administrators and can not be exploited from virtual machines or other hosts on the network. For Red Hat Virtualization, Product Security has rated this flaw as Moderate. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.
Created glusterfs tracking bugs for this issue: Affects: fedora-all [bug 1625085]
This issue has been addressed in the following products: Red Hat Gluster Storage 3.4 for RHEL 7 Native Client for RHEL 7 for Red Hat Storage Via RHSA-2018:2607 https://access.redhat.com/errata/RHSA-2018:2607
This issue has been addressed in the following products: Red Hat Gluster Storage 3.4 for RHEL 6 Native Client for RHEL 6 for Red Hat Storage Via RHSA-2018:2608 https://access.redhat.com/errata/RHSA-2018:2608
upstream fix: https://review.gluster.org/21068
Mitigation: To limit exposure of gluster server nodes : 1. gluster server should be on LAN and not reachable from public networks. 2. Use gluster auth.allow and auth.reject. 3. Use TLS certificates to authenticate gluster clients. caveat: This does not protect from attacks by authenticated gluster clients.
This issue has been addressed in the following products: Red Hat Virtualization 4 for Red Hat Enterprise Linux 7 Via RHSA-2018:3470 https://access.redhat.com/errata/RHSA-2018:3470