RHSA-2017:2338

csafUSredhat_csaf

Red Hat Security Advisory: samba security update

view advisory published 2017-08-01

An update for samba is now available for Red Hat Gluster Storage 3.2 for 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.

01

describes (2)

Related CVEs.

IDseverity exploitable
CVE-2017-2619UShigh7.5Exploit
Samba before versions 4.6.1, 4.5.7 and 4.4.11 are vulnerable to a malicious client using a symlink race to allow access to areas of the server file system not exported under the sh…
CVE-2017-9461USmedium6.5—
smbd in Samba before 4.4.10 and 4.5.x before 4.5.6 has a denial of service vulnerability (fd_open_atomic infinite loop with high CPU usage and memory consumption) due to wrongly ha…
02

references

External citations — patches, advisories, analysis.

03

remediations (84)

  • Fixedctdb-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedctdb-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedctdb-tests-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedctdb-tests-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedlibsmbclient-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedlibsmbclient-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedlibsmbclient-devel-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedlibsmbclient-devel-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedlibwbclient-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedlibwbclient-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedlibwbclient-devel-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedlibwbclient-devel-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedsamba-0:4.6.3-4.el7rhgs.src as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedsamba-0:4.6.3-4.el7rhgs.src as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedsamba-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedsamba-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedsamba-client-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedsamba-client-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedsamba-client-libs-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedsamba-client-libs-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedsamba-common-0:4.6.3-4.el7rhgs.noarch as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedsamba-common-0:4.6.3-4.el7rhgs.noarch as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedsamba-common-libs-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedsamba-common-libs-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedsamba-common-tools-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedsamba-common-tools-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedsamba-dc-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedsamba-dc-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedsamba-dc-libs-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedsamba-dc-libs-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedsamba-debuginfo-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedsamba-debuginfo-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedsamba-devel-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedsamba-devel-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedsamba-krb5-printing-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedsamba-krb5-printing-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedsamba-libs-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedsamba-libs-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedsamba-pidl-0:4.6.3-4.el7rhgs.noarch as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedsamba-pidl-0:4.6.3-4.el7rhgs.noarch as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedsamba-python-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedsamba-python-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedsamba-test-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedsamba-test-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedsamba-test-libs-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedsamba-test-libs-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedsamba-vfs-glusterfs-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedsamba-vfs-glusterfs-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedsamba-winbind-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedsamba-winbind-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedsamba-winbind-clients-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedsamba-winbind-clients-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedsamba-winbind-krb5-locator-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedsamba-winbind-krb5-locator-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedsamba-winbind-modules-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 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-2017:2338
  • Fixedsamba-winbind-modules-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 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-2017:2338
  • Workaroundctdb-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 Samba on RHEL-7

    Add the parameter: unix extensions = no to the [global] section of your smb.conf and restart smbd. This prevents SMB1 clients from creating symlinks on the exported file system using SMB1. However, if the same region of the file system is also exported using NFS, NFS clients can create symlinks that potentially can also hit the race condition. For non-patched versions of Samba we recommend only exporting areas of the file system by either SMB or NFS, not both.

  • Workaroundctdb-tests-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 Samba on RHEL-7

    Add the parameter: unix extensions = no to the [global] section of your smb.conf and restart smbd. This prevents SMB1 clients from creating symlinks on the exported file system using SMB1. However, if the same region of the file system is also exported using NFS, NFS clients can create symlinks that potentially can also hit the race condition. For non-patched versions of Samba we recommend only exporting areas of the file system by either SMB or NFS, not both.

  • Workaroundlibsmbclient-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 Samba on RHEL-7

    Add the parameter: unix extensions = no to the [global] section of your smb.conf and restart smbd. This prevents SMB1 clients from creating symlinks on the exported file system using SMB1. However, if the same region of the file system is also exported using NFS, NFS clients can create symlinks that potentially can also hit the race condition. For non-patched versions of Samba we recommend only exporting areas of the file system by either SMB or NFS, not both.

  • Workaroundlibsmbclient-devel-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 Samba on RHEL-7

    Add the parameter: unix extensions = no to the [global] section of your smb.conf and restart smbd. This prevents SMB1 clients from creating symlinks on the exported file system using SMB1. However, if the same region of the file system is also exported using NFS, NFS clients can create symlinks that potentially can also hit the race condition. For non-patched versions of Samba we recommend only exporting areas of the file system by either SMB or NFS, not both.

  • Workaroundlibwbclient-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 Samba on RHEL-7

    Add the parameter: unix extensions = no to the [global] section of your smb.conf and restart smbd. This prevents SMB1 clients from creating symlinks on the exported file system using SMB1. However, if the same region of the file system is also exported using NFS, NFS clients can create symlinks that potentially can also hit the race condition. For non-patched versions of Samba we recommend only exporting areas of the file system by either SMB or NFS, not both.

  • Workaroundlibwbclient-devel-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 Samba on RHEL-7

    Add the parameter: unix extensions = no to the [global] section of your smb.conf and restart smbd. This prevents SMB1 clients from creating symlinks on the exported file system using SMB1. However, if the same region of the file system is also exported using NFS, NFS clients can create symlinks that potentially can also hit the race condition. For non-patched versions of Samba we recommend only exporting areas of the file system by either SMB or NFS, not both.

  • Workaroundsamba-0:4.6.3-4.el7rhgs.src as a component of Red Hat Gluster 3.2 Samba on RHEL-7

    Add the parameter: unix extensions = no to the [global] section of your smb.conf and restart smbd. This prevents SMB1 clients from creating symlinks on the exported file system using SMB1. However, if the same region of the file system is also exported using NFS, NFS clients can create symlinks that potentially can also hit the race condition. For non-patched versions of Samba we recommend only exporting areas of the file system by either SMB or NFS, not both.

  • Workaroundsamba-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 Samba on RHEL-7

    Add the parameter: unix extensions = no to the [global] section of your smb.conf and restart smbd. This prevents SMB1 clients from creating symlinks on the exported file system using SMB1. However, if the same region of the file system is also exported using NFS, NFS clients can create symlinks that potentially can also hit the race condition. For non-patched versions of Samba we recommend only exporting areas of the file system by either SMB or NFS, not both.

  • Workaroundsamba-client-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 Samba on RHEL-7

    Add the parameter: unix extensions = no to the [global] section of your smb.conf and restart smbd. This prevents SMB1 clients from creating symlinks on the exported file system using SMB1. However, if the same region of the file system is also exported using NFS, NFS clients can create symlinks that potentially can also hit the race condition. For non-patched versions of Samba we recommend only exporting areas of the file system by either SMB or NFS, not both.

  • Workaroundsamba-client-libs-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 Samba on RHEL-7

    Add the parameter: unix extensions = no to the [global] section of your smb.conf and restart smbd. This prevents SMB1 clients from creating symlinks on the exported file system using SMB1. However, if the same region of the file system is also exported using NFS, NFS clients can create symlinks that potentially can also hit the race condition. For non-patched versions of Samba we recommend only exporting areas of the file system by either SMB or NFS, not both.

  • Workaroundsamba-common-0:4.6.3-4.el7rhgs.noarch as a component of Red Hat Gluster 3.2 Samba on RHEL-7

    Add the parameter: unix extensions = no to the [global] section of your smb.conf and restart smbd. This prevents SMB1 clients from creating symlinks on the exported file system using SMB1. However, if the same region of the file system is also exported using NFS, NFS clients can create symlinks that potentially can also hit the race condition. For non-patched versions of Samba we recommend only exporting areas of the file system by either SMB or NFS, not both.

  • Workaroundsamba-common-libs-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 Samba on RHEL-7

    Add the parameter: unix extensions = no to the [global] section of your smb.conf and restart smbd. This prevents SMB1 clients from creating symlinks on the exported file system using SMB1. However, if the same region of the file system is also exported using NFS, NFS clients can create symlinks that potentially can also hit the race condition. For non-patched versions of Samba we recommend only exporting areas of the file system by either SMB or NFS, not both.

  • Workaroundsamba-common-tools-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 Samba on RHEL-7

    Add the parameter: unix extensions = no to the [global] section of your smb.conf and restart smbd. This prevents SMB1 clients from creating symlinks on the exported file system using SMB1. However, if the same region of the file system is also exported using NFS, NFS clients can create symlinks that potentially can also hit the race condition. For non-patched versions of Samba we recommend only exporting areas of the file system by either SMB or NFS, not both.

  • Workaroundsamba-dc-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 Samba on RHEL-7

    Add the parameter: unix extensions = no to the [global] section of your smb.conf and restart smbd. This prevents SMB1 clients from creating symlinks on the exported file system using SMB1. However, if the same region of the file system is also exported using NFS, NFS clients can create symlinks that potentially can also hit the race condition. For non-patched versions of Samba we recommend only exporting areas of the file system by either SMB or NFS, not both.

  • Workaroundsamba-dc-libs-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 Samba on RHEL-7

    Add the parameter: unix extensions = no to the [global] section of your smb.conf and restart smbd. This prevents SMB1 clients from creating symlinks on the exported file system using SMB1. However, if the same region of the file system is also exported using NFS, NFS clients can create symlinks that potentially can also hit the race condition. For non-patched versions of Samba we recommend only exporting areas of the file system by either SMB or NFS, not both.

  • Workaroundsamba-debuginfo-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 Samba on RHEL-7

    Add the parameter: unix extensions = no to the [global] section of your smb.conf and restart smbd. This prevents SMB1 clients from creating symlinks on the exported file system using SMB1. However, if the same region of the file system is also exported using NFS, NFS clients can create symlinks that potentially can also hit the race condition. For non-patched versions of Samba we recommend only exporting areas of the file system by either SMB or NFS, not both.

  • Workaroundsamba-devel-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 Samba on RHEL-7

    Add the parameter: unix extensions = no to the [global] section of your smb.conf and restart smbd. This prevents SMB1 clients from creating symlinks on the exported file system using SMB1. However, if the same region of the file system is also exported using NFS, NFS clients can create symlinks that potentially can also hit the race condition. For non-patched versions of Samba we recommend only exporting areas of the file system by either SMB or NFS, not both.

  • Workaroundsamba-krb5-printing-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 Samba on RHEL-7

    Add the parameter: unix extensions = no to the [global] section of your smb.conf and restart smbd. This prevents SMB1 clients from creating symlinks on the exported file system using SMB1. However, if the same region of the file system is also exported using NFS, NFS clients can create symlinks that potentially can also hit the race condition. For non-patched versions of Samba we recommend only exporting areas of the file system by either SMB or NFS, not both.

  • Workaroundsamba-libs-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 Samba on RHEL-7

    Add the parameter: unix extensions = no to the [global] section of your smb.conf and restart smbd. This prevents SMB1 clients from creating symlinks on the exported file system using SMB1. However, if the same region of the file system is also exported using NFS, NFS clients can create symlinks that potentially can also hit the race condition. For non-patched versions of Samba we recommend only exporting areas of the file system by either SMB or NFS, not both.

  • Workaroundsamba-pidl-0:4.6.3-4.el7rhgs.noarch as a component of Red Hat Gluster 3.2 Samba on RHEL-7

    Add the parameter: unix extensions = no to the [global] section of your smb.conf and restart smbd. This prevents SMB1 clients from creating symlinks on the exported file system using SMB1. However, if the same region of the file system is also exported using NFS, NFS clients can create symlinks that potentially can also hit the race condition. For non-patched versions of Samba we recommend only exporting areas of the file system by either SMB or NFS, not both.

  • Workaroundsamba-python-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 Samba on RHEL-7

    Add the parameter: unix extensions = no to the [global] section of your smb.conf and restart smbd. This prevents SMB1 clients from creating symlinks on the exported file system using SMB1. However, if the same region of the file system is also exported using NFS, NFS clients can create symlinks that potentially can also hit the race condition. For non-patched versions of Samba we recommend only exporting areas of the file system by either SMB or NFS, not both.

  • Workaroundsamba-test-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 Samba on RHEL-7

    Add the parameter: unix extensions = no to the [global] section of your smb.conf and restart smbd. This prevents SMB1 clients from creating symlinks on the exported file system using SMB1. However, if the same region of the file system is also exported using NFS, NFS clients can create symlinks that potentially can also hit the race condition. For non-patched versions of Samba we recommend only exporting areas of the file system by either SMB or NFS, not both.

  • Workaroundsamba-test-libs-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 Samba on RHEL-7

    Add the parameter: unix extensions = no to the [global] section of your smb.conf and restart smbd. This prevents SMB1 clients from creating symlinks on the exported file system using SMB1. However, if the same region of the file system is also exported using NFS, NFS clients can create symlinks that potentially can also hit the race condition. For non-patched versions of Samba we recommend only exporting areas of the file system by either SMB or NFS, not both.

  • Workaroundsamba-vfs-glusterfs-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 Samba on RHEL-7

    Add the parameter: unix extensions = no to the [global] section of your smb.conf and restart smbd. This prevents SMB1 clients from creating symlinks on the exported file system using SMB1. However, if the same region of the file system is also exported using NFS, NFS clients can create symlinks that potentially can also hit the race condition. For non-patched versions of Samba we recommend only exporting areas of the file system by either SMB or NFS, not both.

  • Workaroundsamba-winbind-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 Samba on RHEL-7

    Add the parameter: unix extensions = no to the [global] section of your smb.conf and restart smbd. This prevents SMB1 clients from creating symlinks on the exported file system using SMB1. However, if the same region of the file system is also exported using NFS, NFS clients can create symlinks that potentially can also hit the race condition. For non-patched versions of Samba we recommend only exporting areas of the file system by either SMB or NFS, not both.

  • Workaroundsamba-winbind-clients-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 Samba on RHEL-7

    Add the parameter: unix extensions = no to the [global] section of your smb.conf and restart smbd. This prevents SMB1 clients from creating symlinks on the exported file system using SMB1. However, if the same region of the file system is also exported using NFS, NFS clients can create symlinks that potentially can also hit the race condition. For non-patched versions of Samba we recommend only exporting areas of the file system by either SMB or NFS, not both.

  • Workaroundsamba-winbind-krb5-locator-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 Samba on RHEL-7

    Add the parameter: unix extensions = no to the [global] section of your smb.conf and restart smbd. This prevents SMB1 clients from creating symlinks on the exported file system using SMB1. However, if the same region of the file system is also exported using NFS, NFS clients can create symlinks that potentially can also hit the race condition. For non-patched versions of Samba we recommend only exporting areas of the file system by either SMB or NFS, not both.

  • Workaroundsamba-winbind-modules-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 Samba on RHEL-7

    Add the parameter: unix extensions = no to the [global] section of your smb.conf and restart smbd. This prevents SMB1 clients from creating symlinks on the exported file system using SMB1. However, if the same region of the file system is also exported using NFS, NFS clients can create symlinks that potentially can also hit the race condition. For non-patched versions of Samba we recommend only exporting areas of the file system by either SMB or NFS, not both.

scry

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