Red Hat Security Advisory: samba security and bug fix update
An update for samba is now available for Red Hat Gluster Storage 3.5 on Red Hat Enterprise Linux 7. 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.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2019-10197US | critical9.1 | — | ||
A flaw was found in samba versions 4.9.x up to 4.9.13, samba 4.10.x up to 4.10.8 and samba 4.11.x up to 4.11.0rc3, when certain parameters were set in the samba configuration file.… | ||||
references
External citations — patches, advisories, analysis.
- https://access.redhat.com/errata/RHSA-2019:3253self
- https://access.redhat.com/security/cve/CVE-2019-10197external
- https://access.redhat.com/security/updates/classification/#moderateexternal
- 1667895external
- 1715503external
- 1724243external
- 1724261external
- 1743595external
remediations (50)
- Fixedctdb-0:4.9.8-109.el7rhgs.x86_64 as a component of Red Hat Gluster 3.5 Samba on RHEL-7
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the smb service will be restarted automatically.
https://access.redhat.com/errata/RHSA-2019:3253 - Fixedlibsmbclient-0:4.9.8-109.el7rhgs.x86_64 as a component of Red Hat Gluster 3.5 Samba on RHEL-7
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the smb service will be restarted automatically.
https://access.redhat.com/errata/RHSA-2019:3253 - Fixedlibsmbclient-devel-0:4.9.8-109.el7rhgs.x86_64 as a component of Red Hat Gluster 3.5 Samba on RHEL-7
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the smb service will be restarted automatically.
https://access.redhat.com/errata/RHSA-2019:3253 - Fixedlibwbclient-0:4.9.8-109.el7rhgs.x86_64 as a component of Red Hat Gluster 3.5 Samba on RHEL-7
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the smb service will be restarted automatically.
https://access.redhat.com/errata/RHSA-2019:3253 - Fixedlibwbclient-devel-0:4.9.8-109.el7rhgs.x86_64 as a component of Red Hat Gluster 3.5 Samba on RHEL-7
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the smb service will be restarted automatically.
https://access.redhat.com/errata/RHSA-2019:3253 - Fixedsamba-0:4.9.8-109.el7rhgs.src as a component of Red Hat Gluster 3.5 Samba on RHEL-7
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the smb service will be restarted automatically.
https://access.redhat.com/errata/RHSA-2019:3253 - Fixedsamba-0:4.9.8-109.el7rhgs.x86_64 as a component of Red Hat Gluster 3.5 Samba on RHEL-7
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the smb service will be restarted automatically.
https://access.redhat.com/errata/RHSA-2019:3253 - Fixedsamba-client-0:4.9.8-109.el7rhgs.x86_64 as a component of Red Hat Gluster 3.5 Samba on RHEL-7
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the smb service will be restarted automatically.
https://access.redhat.com/errata/RHSA-2019:3253 - Fixedsamba-client-libs-0:4.9.8-109.el7rhgs.x86_64 as a component of Red Hat Gluster 3.5 Samba on RHEL-7
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the smb service will be restarted automatically.
https://access.redhat.com/errata/RHSA-2019:3253 - Fixedsamba-common-0:4.9.8-109.el7rhgs.noarch as a component of Red Hat Gluster 3.5 Samba on RHEL-7
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the smb service will be restarted automatically.
https://access.redhat.com/errata/RHSA-2019:3253 - Fixedsamba-common-libs-0:4.9.8-109.el7rhgs.x86_64 as a component of Red Hat Gluster 3.5 Samba on RHEL-7
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the smb service will be restarted automatically.
https://access.redhat.com/errata/RHSA-2019:3253 - Fixedsamba-common-tools-0:4.9.8-109.el7rhgs.x86_64 as a component of Red Hat Gluster 3.5 Samba on RHEL-7
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the smb service will be restarted automatically.
https://access.redhat.com/errata/RHSA-2019:3253 - Fixedsamba-dc-0:4.9.8-109.el7rhgs.x86_64 as a component of Red Hat Gluster 3.5 Samba on RHEL-7
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the smb service will be restarted automatically.
https://access.redhat.com/errata/RHSA-2019:3253 - Fixedsamba-dc-libs-0:4.9.8-109.el7rhgs.x86_64 as a component of Red Hat Gluster 3.5 Samba on RHEL-7
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the smb service will be restarted automatically.
https://access.redhat.com/errata/RHSA-2019:3253 - Fixedsamba-debuginfo-0:4.9.8-109.el7rhgs.x86_64 as a component of Red Hat Gluster 3.5 Samba on RHEL-7
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the smb service will be restarted automatically.
https://access.redhat.com/errata/RHSA-2019:3253 - Fixedsamba-devel-0:4.9.8-109.el7rhgs.x86_64 as a component of Red Hat Gluster 3.5 Samba on RHEL-7
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the smb service will be restarted automatically.
https://access.redhat.com/errata/RHSA-2019:3253 - Fixedsamba-krb5-printing-0:4.9.8-109.el7rhgs.x86_64 as a component of Red Hat Gluster 3.5 Samba on RHEL-7
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the smb service will be restarted automatically.
https://access.redhat.com/errata/RHSA-2019:3253 - Fixedsamba-libs-0:4.9.8-109.el7rhgs.x86_64 as a component of Red Hat Gluster 3.5 Samba on RHEL-7
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the smb service will be restarted automatically.
https://access.redhat.com/errata/RHSA-2019:3253 - Fixedsamba-pidl-0:4.9.8-109.el7rhgs.noarch as a component of Red Hat Gluster 3.5 Samba on RHEL-7
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the smb service will be restarted automatically.
https://access.redhat.com/errata/RHSA-2019:3253 - Fixedsamba-python-0:4.9.8-109.el7rhgs.x86_64 as a component of Red Hat Gluster 3.5 Samba on RHEL-7
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the smb service will be restarted automatically.
https://access.redhat.com/errata/RHSA-2019:3253 - Fixedsamba-vfs-glusterfs-0:4.9.8-109.el7rhgs.x86_64 as a component of Red Hat Gluster 3.5 Samba on RHEL-7
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the smb service will be restarted automatically.
https://access.redhat.com/errata/RHSA-2019:3253 - Fixedsamba-winbind-0:4.9.8-109.el7rhgs.x86_64 as a component of Red Hat Gluster 3.5 Samba on RHEL-7
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the smb service will be restarted automatically.
https://access.redhat.com/errata/RHSA-2019:3253 - Fixedsamba-winbind-clients-0:4.9.8-109.el7rhgs.x86_64 as a component of Red Hat Gluster 3.5 Samba on RHEL-7
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the smb service will be restarted automatically.
https://access.redhat.com/errata/RHSA-2019:3253 - Fixedsamba-winbind-krb5-locator-0:4.9.8-109.el7rhgs.x86_64 as a component of Red Hat Gluster 3.5 Samba on RHEL-7
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the smb service will be restarted automatically.
https://access.redhat.com/errata/RHSA-2019:3253 - Fixedsamba-winbind-modules-0:4.9.8-109.el7rhgs.x86_64 as a component of Red Hat Gluster 3.5 Samba on RHEL-7
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the smb service will be restarted automatically.
https://access.redhat.com/errata/RHSA-2019:3253 - Workaroundctdb-0:4.9.8-109.el7rhgs.x86_64 as a component of Red Hat Gluster 3.5 Samba on RHEL-7
The following methods can be used as a mitigation (only one is needed): 1. Use the 'sharesec' tool to configure a security descriptor for the share that's at least as strict as the permissions on the share root directory. 2. Use the 'valid users' option to allow only users/groups which are able to enter the share root directory. 3. Remove 'wide links = yes' if it's not really needed. 4. In some situations it might be an option to use 'chmod a+x' on the share root directory, but you need to make sure that files and subdirectories are protected by stricter permissions. You may also want to 'chmod a-w' in order to prevent new top level files and directories, which may have less restrictive permissions.
- Workaroundlibsmbclient-0:4.9.8-109.el7rhgs.x86_64 as a component of Red Hat Gluster 3.5 Samba on RHEL-7
The following methods can be used as a mitigation (only one is needed): 1. Use the 'sharesec' tool to configure a security descriptor for the share that's at least as strict as the permissions on the share root directory. 2. Use the 'valid users' option to allow only users/groups which are able to enter the share root directory. 3. Remove 'wide links = yes' if it's not really needed. 4. In some situations it might be an option to use 'chmod a+x' on the share root directory, but you need to make sure that files and subdirectories are protected by stricter permissions. You may also want to 'chmod a-w' in order to prevent new top level files and directories, which may have less restrictive permissions.
- Workaroundlibsmbclient-devel-0:4.9.8-109.el7rhgs.x86_64 as a component of Red Hat Gluster 3.5 Samba on RHEL-7
The following methods can be used as a mitigation (only one is needed): 1. Use the 'sharesec' tool to configure a security descriptor for the share that's at least as strict as the permissions on the share root directory. 2. Use the 'valid users' option to allow only users/groups which are able to enter the share root directory. 3. Remove 'wide links = yes' if it's not really needed. 4. In some situations it might be an option to use 'chmod a+x' on the share root directory, but you need to make sure that files and subdirectories are protected by stricter permissions. You may also want to 'chmod a-w' in order to prevent new top level files and directories, which may have less restrictive permissions.
- Workaroundlibwbclient-0:4.9.8-109.el7rhgs.x86_64 as a component of Red Hat Gluster 3.5 Samba on RHEL-7
The following methods can be used as a mitigation (only one is needed): 1. Use the 'sharesec' tool to configure a security descriptor for the share that's at least as strict as the permissions on the share root directory. 2. Use the 'valid users' option to allow only users/groups which are able to enter the share root directory. 3. Remove 'wide links = yes' if it's not really needed. 4. In some situations it might be an option to use 'chmod a+x' on the share root directory, but you need to make sure that files and subdirectories are protected by stricter permissions. You may also want to 'chmod a-w' in order to prevent new top level files and directories, which may have less restrictive permissions.
- Workaroundlibwbclient-devel-0:4.9.8-109.el7rhgs.x86_64 as a component of Red Hat Gluster 3.5 Samba on RHEL-7
The following methods can be used as a mitigation (only one is needed): 1. Use the 'sharesec' tool to configure a security descriptor for the share that's at least as strict as the permissions on the share root directory. 2. Use the 'valid users' option to allow only users/groups which are able to enter the share root directory. 3. Remove 'wide links = yes' if it's not really needed. 4. In some situations it might be an option to use 'chmod a+x' on the share root directory, but you need to make sure that files and subdirectories are protected by stricter permissions. You may also want to 'chmod a-w' in order to prevent new top level files and directories, which may have less restrictive permissions.
- Workaroundsamba-0:4.9.8-109.el7rhgs.src as a component of Red Hat Gluster 3.5 Samba on RHEL-7
The following methods can be used as a mitigation (only one is needed): 1. Use the 'sharesec' tool to configure a security descriptor for the share that's at least as strict as the permissions on the share root directory. 2. Use the 'valid users' option to allow only users/groups which are able to enter the share root directory. 3. Remove 'wide links = yes' if it's not really needed. 4. In some situations it might be an option to use 'chmod a+x' on the share root directory, but you need to make sure that files and subdirectories are protected by stricter permissions. You may also want to 'chmod a-w' in order to prevent new top level files and directories, which may have less restrictive permissions.
- Workaroundsamba-0:4.9.8-109.el7rhgs.x86_64 as a component of Red Hat Gluster 3.5 Samba on RHEL-7
The following methods can be used as a mitigation (only one is needed): 1. Use the 'sharesec' tool to configure a security descriptor for the share that's at least as strict as the permissions on the share root directory. 2. Use the 'valid users' option to allow only users/groups which are able to enter the share root directory. 3. Remove 'wide links = yes' if it's not really needed. 4. In some situations it might be an option to use 'chmod a+x' on the share root directory, but you need to make sure that files and subdirectories are protected by stricter permissions. You may also want to 'chmod a-w' in order to prevent new top level files and directories, which may have less restrictive permissions.
- Workaroundsamba-client-0:4.9.8-109.el7rhgs.x86_64 as a component of Red Hat Gluster 3.5 Samba on RHEL-7
The following methods can be used as a mitigation (only one is needed): 1. Use the 'sharesec' tool to configure a security descriptor for the share that's at least as strict as the permissions on the share root directory. 2. Use the 'valid users' option to allow only users/groups which are able to enter the share root directory. 3. Remove 'wide links = yes' if it's not really needed. 4. In some situations it might be an option to use 'chmod a+x' on the share root directory, but you need to make sure that files and subdirectories are protected by stricter permissions. You may also want to 'chmod a-w' in order to prevent new top level files and directories, which may have less restrictive permissions.
- Workaroundsamba-client-libs-0:4.9.8-109.el7rhgs.x86_64 as a component of Red Hat Gluster 3.5 Samba on RHEL-7
The following methods can be used as a mitigation (only one is needed): 1. Use the 'sharesec' tool to configure a security descriptor for the share that's at least as strict as the permissions on the share root directory. 2. Use the 'valid users' option to allow only users/groups which are able to enter the share root directory. 3. Remove 'wide links = yes' if it's not really needed. 4. In some situations it might be an option to use 'chmod a+x' on the share root directory, but you need to make sure that files and subdirectories are protected by stricter permissions. You may also want to 'chmod a-w' in order to prevent new top level files and directories, which may have less restrictive permissions.
- Workaroundsamba-common-0:4.9.8-109.el7rhgs.noarch as a component of Red Hat Gluster 3.5 Samba on RHEL-7
The following methods can be used as a mitigation (only one is needed): 1. Use the 'sharesec' tool to configure a security descriptor for the share that's at least as strict as the permissions on the share root directory. 2. Use the 'valid users' option to allow only users/groups which are able to enter the share root directory. 3. Remove 'wide links = yes' if it's not really needed. 4. In some situations it might be an option to use 'chmod a+x' on the share root directory, but you need to make sure that files and subdirectories are protected by stricter permissions. You may also want to 'chmod a-w' in order to prevent new top level files and directories, which may have less restrictive permissions.
- Workaroundsamba-common-libs-0:4.9.8-109.el7rhgs.x86_64 as a component of Red Hat Gluster 3.5 Samba on RHEL-7
The following methods can be used as a mitigation (only one is needed): 1. Use the 'sharesec' tool to configure a security descriptor for the share that's at least as strict as the permissions on the share root directory. 2. Use the 'valid users' option to allow only users/groups which are able to enter the share root directory. 3. Remove 'wide links = yes' if it's not really needed. 4. In some situations it might be an option to use 'chmod a+x' on the share root directory, but you need to make sure that files and subdirectories are protected by stricter permissions. You may also want to 'chmod a-w' in order to prevent new top level files and directories, which may have less restrictive permissions.
- Workaroundsamba-common-tools-0:4.9.8-109.el7rhgs.x86_64 as a component of Red Hat Gluster 3.5 Samba on RHEL-7
The following methods can be used as a mitigation (only one is needed): 1. Use the 'sharesec' tool to configure a security descriptor for the share that's at least as strict as the permissions on the share root directory. 2. Use the 'valid users' option to allow only users/groups which are able to enter the share root directory. 3. Remove 'wide links = yes' if it's not really needed. 4. In some situations it might be an option to use 'chmod a+x' on the share root directory, but you need to make sure that files and subdirectories are protected by stricter permissions. You may also want to 'chmod a-w' in order to prevent new top level files and directories, which may have less restrictive permissions.
- Workaroundsamba-dc-0:4.9.8-109.el7rhgs.x86_64 as a component of Red Hat Gluster 3.5 Samba on RHEL-7
The following methods can be used as a mitigation (only one is needed): 1. Use the 'sharesec' tool to configure a security descriptor for the share that's at least as strict as the permissions on the share root directory. 2. Use the 'valid users' option to allow only users/groups which are able to enter the share root directory. 3. Remove 'wide links = yes' if it's not really needed. 4. In some situations it might be an option to use 'chmod a+x' on the share root directory, but you need to make sure that files and subdirectories are protected by stricter permissions. You may also want to 'chmod a-w' in order to prevent new top level files and directories, which may have less restrictive permissions.
- Workaroundsamba-dc-libs-0:4.9.8-109.el7rhgs.x86_64 as a component of Red Hat Gluster 3.5 Samba on RHEL-7
The following methods can be used as a mitigation (only one is needed): 1. Use the 'sharesec' tool to configure a security descriptor for the share that's at least as strict as the permissions on the share root directory. 2. Use the 'valid users' option to allow only users/groups which are able to enter the share root directory. 3. Remove 'wide links = yes' if it's not really needed. 4. In some situations it might be an option to use 'chmod a+x' on the share root directory, but you need to make sure that files and subdirectories are protected by stricter permissions. You may also want to 'chmod a-w' in order to prevent new top level files and directories, which may have less restrictive permissions.
- Workaroundsamba-debuginfo-0:4.9.8-109.el7rhgs.x86_64 as a component of Red Hat Gluster 3.5 Samba on RHEL-7
The following methods can be used as a mitigation (only one is needed): 1. Use the 'sharesec' tool to configure a security descriptor for the share that's at least as strict as the permissions on the share root directory. 2. Use the 'valid users' option to allow only users/groups which are able to enter the share root directory. 3. Remove 'wide links = yes' if it's not really needed. 4. In some situations it might be an option to use 'chmod a+x' on the share root directory, but you need to make sure that files and subdirectories are protected by stricter permissions. You may also want to 'chmod a-w' in order to prevent new top level files and directories, which may have less restrictive permissions.
- Workaroundsamba-devel-0:4.9.8-109.el7rhgs.x86_64 as a component of Red Hat Gluster 3.5 Samba on RHEL-7
The following methods can be used as a mitigation (only one is needed): 1. Use the 'sharesec' tool to configure a security descriptor for the share that's at least as strict as the permissions on the share root directory. 2. Use the 'valid users' option to allow only users/groups which are able to enter the share root directory. 3. Remove 'wide links = yes' if it's not really needed. 4. In some situations it might be an option to use 'chmod a+x' on the share root directory, but you need to make sure that files and subdirectories are protected by stricter permissions. You may also want to 'chmod a-w' in order to prevent new top level files and directories, which may have less restrictive permissions.
- Workaroundsamba-krb5-printing-0:4.9.8-109.el7rhgs.x86_64 as a component of Red Hat Gluster 3.5 Samba on RHEL-7
The following methods can be used as a mitigation (only one is needed): 1. Use the 'sharesec' tool to configure a security descriptor for the share that's at least as strict as the permissions on the share root directory. 2. Use the 'valid users' option to allow only users/groups which are able to enter the share root directory. 3. Remove 'wide links = yes' if it's not really needed. 4. In some situations it might be an option to use 'chmod a+x' on the share root directory, but you need to make sure that files and subdirectories are protected by stricter permissions. You may also want to 'chmod a-w' in order to prevent new top level files and directories, which may have less restrictive permissions.
- Workaroundsamba-libs-0:4.9.8-109.el7rhgs.x86_64 as a component of Red Hat Gluster 3.5 Samba on RHEL-7
The following methods can be used as a mitigation (only one is needed): 1. Use the 'sharesec' tool to configure a security descriptor for the share that's at least as strict as the permissions on the share root directory. 2. Use the 'valid users' option to allow only users/groups which are able to enter the share root directory. 3. Remove 'wide links = yes' if it's not really needed. 4. In some situations it might be an option to use 'chmod a+x' on the share root directory, but you need to make sure that files and subdirectories are protected by stricter permissions. You may also want to 'chmod a-w' in order to prevent new top level files and directories, which may have less restrictive permissions.
- Workaroundsamba-pidl-0:4.9.8-109.el7rhgs.noarch as a component of Red Hat Gluster 3.5 Samba on RHEL-7
The following methods can be used as a mitigation (only one is needed): 1. Use the 'sharesec' tool to configure a security descriptor for the share that's at least as strict as the permissions on the share root directory. 2. Use the 'valid users' option to allow only users/groups which are able to enter the share root directory. 3. Remove 'wide links = yes' if it's not really needed. 4. In some situations it might be an option to use 'chmod a+x' on the share root directory, but you need to make sure that files and subdirectories are protected by stricter permissions. You may also want to 'chmod a-w' in order to prevent new top level files and directories, which may have less restrictive permissions.
- Workaroundsamba-python-0:4.9.8-109.el7rhgs.x86_64 as a component of Red Hat Gluster 3.5 Samba on RHEL-7
The following methods can be used as a mitigation (only one is needed): 1. Use the 'sharesec' tool to configure a security descriptor for the share that's at least as strict as the permissions on the share root directory. 2. Use the 'valid users' option to allow only users/groups which are able to enter the share root directory. 3. Remove 'wide links = yes' if it's not really needed. 4. In some situations it might be an option to use 'chmod a+x' on the share root directory, but you need to make sure that files and subdirectories are protected by stricter permissions. You may also want to 'chmod a-w' in order to prevent new top level files and directories, which may have less restrictive permissions.
- Workaroundsamba-vfs-glusterfs-0:4.9.8-109.el7rhgs.x86_64 as a component of Red Hat Gluster 3.5 Samba on RHEL-7
The following methods can be used as a mitigation (only one is needed): 1. Use the 'sharesec' tool to configure a security descriptor for the share that's at least as strict as the permissions on the share root directory. 2. Use the 'valid users' option to allow only users/groups which are able to enter the share root directory. 3. Remove 'wide links = yes' if it's not really needed. 4. In some situations it might be an option to use 'chmod a+x' on the share root directory, but you need to make sure that files and subdirectories are protected by stricter permissions. You may also want to 'chmod a-w' in order to prevent new top level files and directories, which may have less restrictive permissions.
- Workaroundsamba-winbind-0:4.9.8-109.el7rhgs.x86_64 as a component of Red Hat Gluster 3.5 Samba on RHEL-7
The following methods can be used as a mitigation (only one is needed): 1. Use the 'sharesec' tool to configure a security descriptor for the share that's at least as strict as the permissions on the share root directory. 2. Use the 'valid users' option to allow only users/groups which are able to enter the share root directory. 3. Remove 'wide links = yes' if it's not really needed. 4. In some situations it might be an option to use 'chmod a+x' on the share root directory, but you need to make sure that files and subdirectories are protected by stricter permissions. You may also want to 'chmod a-w' in order to prevent new top level files and directories, which may have less restrictive permissions.
- Workaroundsamba-winbind-clients-0:4.9.8-109.el7rhgs.x86_64 as a component of Red Hat Gluster 3.5 Samba on RHEL-7
The following methods can be used as a mitigation (only one is needed): 1. Use the 'sharesec' tool to configure a security descriptor for the share that's at least as strict as the permissions on the share root directory. 2. Use the 'valid users' option to allow only users/groups which are able to enter the share root directory. 3. Remove 'wide links = yes' if it's not really needed. 4. In some situations it might be an option to use 'chmod a+x' on the share root directory, but you need to make sure that files and subdirectories are protected by stricter permissions. You may also want to 'chmod a-w' in order to prevent new top level files and directories, which may have less restrictive permissions.
- Workaroundsamba-winbind-krb5-locator-0:4.9.8-109.el7rhgs.x86_64 as a component of Red Hat Gluster 3.5 Samba on RHEL-7
The following methods can be used as a mitigation (only one is needed): 1. Use the 'sharesec' tool to configure a security descriptor for the share that's at least as strict as the permissions on the share root directory. 2. Use the 'valid users' option to allow only users/groups which are able to enter the share root directory. 3. Remove 'wide links = yes' if it's not really needed. 4. In some situations it might be an option to use 'chmod a+x' on the share root directory, but you need to make sure that files and subdirectories are protected by stricter permissions. You may also want to 'chmod a-w' in order to prevent new top level files and directories, which may have less restrictive permissions.
- Workaroundsamba-winbind-modules-0:4.9.8-109.el7rhgs.x86_64 as a component of Red Hat Gluster 3.5 Samba on RHEL-7
The following methods can be used as a mitigation (only one is needed): 1. Use the 'sharesec' tool to configure a security descriptor for the share that's at least as strict as the permissions on the share root directory. 2. Use the 'valid users' option to allow only users/groups which are able to enter the share root directory. 3. Remove 'wide links = yes' if it's not really needed. 4. In some situations it might be an option to use 'chmod a+x' on the share root directory, but you need to make sure that files and subdirectories are protected by stricter permissions. You may also want to 'chmod a-w' in order to prevent new top level files and directories, which may have less restrictive permissions.
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan