It was found that the "mknod" call derived from mknod(2) can create files pointing to devices on a glusterfs server node. An authenticated attacker could use this to create an arbitrary device and read data from any device attached to the glusterfs server node.
Find out more about CVE-2018-10923 from the MITRE CVE dictionary dictionary and NIST NVD.
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/.
CVSS3 Base Score | 7.6 |
---|---|
CVSS3 Base Metrics | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L |
Attack Vector | Network |
Attack Complexity | Low |
Privileges Required | Low |
User Interaction | None |
Scope | Unchanged |
Confidentiality | High |
Integrity Impact | Low |
Availability Impact | Low |
Platform | Errata | Release Date |
---|---|---|
Red Hat Gluster Storage 3.4 for RHEL 6 (glusterfs) | RHSA-2018:2608 | 2018-09-04 |
Red Hat Storage Native Client for Red Hat Enterprise Linux 6 (glusterfs) | RHSA-2018:2608 | 2018-09-04 |
Red Hat Virtualization 4 Management Agent for RHEL 7 Hosts | RHSA-2018:3470 | 2018-11-05 |
Red Hat Virtualization 4 Management Agent for RHEL 7 Hosts | RHSA-2018:2607 | 2018-09-04 |
Red Hat Storage Native Client for Red Hat Enterprise Linux 7 (glusterfs) | RHSA-2018:2607 | 2018-09-04 |
Red Hat Gluster Storage 3.4 for RHEL 7 (glusterfs) | RHSA-2018:2607 | 2018-09-04 |
Platform | Package | State |
---|---|---|
Red Hat Enterprise Linux 7 | glusterfs | Not affected |
Red Hat Enterprise Linux 6 | glusterfs | Not affected |
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.