As per upstream advisory:
The SMB1/2/3 protocols have a concept of "ChangeNotify", where a client can request file name notification on a directory handle when a condition such as "new file creation" or "file size change" or "file timestamp update" occurs.
A missing permissions check on a directory handle requesting ChangeNotify meant that a client with a directory handle open only for FILE_READ_ATTRIBUTES (minimal access rights) could be used to obtain change notify replies from the server. These replies contain information that should not be available to directory handles open for FILE_READ_ATTRIBUTE only.
Name: the Samba project
Upstream: Steven French (Microsoft and the Samba Team)
As Samba internally opens an underlying file system handle on a directory when a client requests an open, even for FILE_READ_ATTRIBUTES then if the underlying file system permissions don't allow "r" (read) access for the connected user, then the handle open request will be denied.
"r" access is the normal permission needed to list or otherwise reveal the contents of a directory, so if a connected user has "r" access then they will be able to list the directory contents normally, and the information received by a ChangeNofity request is already available to the user.
The security issue occurs if the Administrator or directory owner had set more restrictive Windows ACL permissions on the directory to disallow read access to the user, and this permissions change was not reflected in the underlying file system permissions.
This will only occur if Samba is configured with VFS modules to decouple the underlying file system permissions from the Windows ACLs, by setting up a share with the settings:
vfs_objects = vfs_acl_xattr
acl_xattr:ignore system acls = yes
Created samba tracking bugs for this issue:
Affects: fedora-all [bug 1892634]
This issue has been addressed in the following products:
Red Hat Enterprise Linux 7
Via RHSA-2020:5439 https://access.redhat.com/errata/RHSA-2020:5439
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):