It was found that the fix for CVE-2018-10927, CVE-2018-10928, CVE-2018-10929, CVE-2018-10930, and CVE-2018-10926 was incomplete

A flaw was found in RPC request using gfs2_create_req in glusterfs server

A flaw was found in RPC request using gfs3_symlink_req in glusterfs server which allows symlink destinations to point to file paths outside of the gluster volume

A flaw was found in RPC request using gfs3_mknod_req supported by glusterfs server

It was found that glusterfs server is vulnerable to multiple stack based buffer overflows due to functions in server-rpc-fopc.c allocating fixed size buffers using 'alloca(3)'

It was found that glusterfs server does not properly sanitize file paths in the "trusted.io-stats-dump" extended attribute which is used by the "debug/io-stats" translator

glusterfs is vulnerable to privilege escalation on gluster server nodes

glusterfs server before versions 3.10.12, 4.0.2 is vulnerable when using 'auth.allow' option which allows any unauthenticated gluster client to connect from any network to mount…

A flaw was found in RPC request using gfs3_lookup_req in glusterfs server

It was found that the "mknod" call derived from mknod(2) can create files pointing to devices on a glusterfs server node

In Gluster GlusterFS 11.0, there is an xlators/mount/fuse/src/fuse-bridge.c notify stack-based buffer over-read

In Gluster GlusterFS 11.0, there is an xlators/cluster/dht/src/dht-common.c dht_setxattr_mds_cbk use-after-free

A flaw was found in the way dic_unserialize function of glusterfs does not handle negative key length values