CVE-2017-2619

mediumpriority · track · 44EPSS 0.111 · 96 %ileexploit · functionalEURUUS

grimoire priorityP1 · Urgent

Exploitable?

Public exploit

1 exploit · functional

Likely / severe?

11.1% (96th) EPSS

CVSS 6 · medium

Is it mine?

96 products

Check your exposure

Who says so?

5 sources

cnnvd · enisa_euvd · fstec_bdu · nvd

EPSS · scored 2026-10-27

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 share definition.

remediations

Vendor fix, mitigation, or workaround guidance, as published by each source.

A vendor fix is available.

Fixedctdb-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 Samba on RHEL-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedctdb-tests-0:4.6.3-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedldb-tools-0:1.1.29-1.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedlibldb-0:1.1.29-1.el6rhs.src as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedlibldb-0:1.1.29-1.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedlibldb-debuginfo-0:1.1.29-1.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedlibldb-devel-0:1.1.29-1.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedlibsmbclient-0:4.6.3-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedlibsmbclient-devel-0:4.6.3-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedlibtalloc-0:2.1.9-1.el6rhs.src as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedlibtalloc-0:2.1.9-1.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedlibtalloc-debuginfo-0:2.1.9-1.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedlibtalloc-devel-0:2.1.9-1.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedlibtdb-0:1.3.12-1.1.el6rhs.src as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedlibtdb-0:1.3.12-1.1.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedlibtdb-debuginfo-0:1.3.12-1.1.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedlibtdb-devel-0:1.3.12-1.1.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedlibtevent-0:0.9.31-1.el6rhs.src as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedlibtevent-0:0.9.31-1.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedlibtevent-debuginfo-0:0.9.31-1.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedlibtevent-devel-0:0.9.31-1.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedlibwbclient-0:4.6.3-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedlibwbclient-devel-0:4.6.3-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedpyldb-0:1.1.29-1.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedpyldb-devel-0:1.1.29-1.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedpytalloc-0:2.1.9-1.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedpytalloc-devel-0:2.1.9-1.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedpython-tdb-0:1.3.12-1.1.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedpython-tevent-0:0.9.31-1.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedsamba-0:4.6.3-5.el6rhs.src as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedsamba-0:4.6.3-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedsamba-client-0:4.6.3-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedsamba-client-libs-0:4.6.3-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedsamba-common-0:4.6.3-5.el6rhs.noarch as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedsamba-common-libs-0:4.6.3-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedsamba-common-tools-0:4.6.3-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedsamba-dc-0:4.6.3-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedsamba-dc-libs-0:4.6.3-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedsamba-debuginfo-0:4.6.3-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedsamba-devel-0:4.6.3-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedsamba-krb5-printing-0:4.6.3-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedsamba-libs-0:4.6.3-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedsamba-pidl-0:4.6.3-5.el6rhs.noarch as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedsamba-python-0:4.6.3-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedsamba-test-0:4.6.3-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedsamba-test-libs-0:4.6.3-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedsamba-vfs-glusterfs-0:4.6.3-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedsamba-winbind-0:4.6.3-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedsamba-winbind-clients-0:4.6.3-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedsamba-winbind-krb5-locator-0:4.6.3-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedsamba-winbind-modules-0:4.6.3-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Fixedtdb-tools-0:1.3.12-1.1.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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:2778
Workaroundctdb-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 Samba on RHEL-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-7redhat_csaf
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-0:4.6.3-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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.
Workaroundldb-tools-0:1.1.29-1.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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.
Workaroundlibldb-0:1.1.29-1.el6rhs.src as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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.
Workaroundlibldb-0:1.1.29-1.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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.
Workaroundlibldb-debuginfo-0:1.1.29-1.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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.
Workaroundlibldb-devel-0:1.1.29-1.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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.
Workaroundlibtalloc-0:2.1.9-1.el6rhs.src as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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.
Workaroundlibtalloc-0:2.1.9-1.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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.
Workaroundlibtalloc-debuginfo-0:2.1.9-1.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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.
Workaroundlibtalloc-devel-0:2.1.9-1.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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.
Workaroundlibtdb-0:1.3.12-1.1.el6rhs.src as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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.
Workaroundlibtdb-0:1.3.12-1.1.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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.
Workaroundlibtdb-debuginfo-0:1.3.12-1.1.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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.
Workaroundlibtdb-devel-0:1.3.12-1.1.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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.
Workaroundlibtevent-0:0.9.31-1.el6rhs.src as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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.
Workaroundlibtevent-0:0.9.31-1.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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.
Workaroundlibtevent-debuginfo-0:0.9.31-1.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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.
Workaroundlibtevent-devel-0:0.9.31-1.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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.
Workaroundpyldb-0:1.1.29-1.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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.
Workaroundpyldb-devel-0:1.1.29-1.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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.
Workaroundpytalloc-0:2.1.9-1.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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.
Workaroundpytalloc-devel-0:2.1.9-1.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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.
Workaroundpython-tdb-0:1.3.12-1.1.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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.
Workaroundpython-tevent-0:0.9.31-1.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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-5.el6rhs.src as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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-5.el6rhs.noarch as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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-5.el6rhs.noarch as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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.
Workaroundtdb-tools-0:1.3.12-1.1.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6redhat_csaf
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.

cvss

Technical severity, 0–10. One row per scoring source.

7.5

010

base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · medium–high · 5.9–7.5

v2.06mediumAV:N/AC:M/Au:S/C:P/I:P/A:Pprimary · NVD / NIST USexploitability 6.8 · impact 6.4

v3.17.5highCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:Hprimary · NVD / NIST USexploitability 1.6 · impact 5.9

v3.05.9mediumCVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:Lsecondary · Red Hat Product Security US

v3.17.5highAV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:Hsecondary · FSTEC (BDU) RU

v3.17.1highCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H/E:Psecondary · CVSS-BT (t0sche)

weaknesses

The CWE weakness classes this flaw belongs to.

CWE-362USprimaryCWE-59USprimaryCWE-362USCWE-362US

exploits (1)

Public proof-of-concept and weaponised exploit code.

EDB-41740Samba 4.5.2 - Symlink Race Permits Opening Files Outside Share Directoryfunctional · exploit_db

affected products (96)

Products and version ranges known to be affected.

Samba Samba≤ 4.6.1enisa_euvdEU
Samba Samba≤ 4.5.7enisa_euvdEU
Samba Samba≤ 4.4.11enisa_euvdEU
Samba Team Samba≤ 4.4.11fstec_bduRU
Samba Team Samba≤ 4.5.7fstec_bduRU
Samba Team Samba≤ 4.6.1fstec_bduRU
ООО «РусБИТех-Астра» Astra Linux Common Edition≤ 2.12 «Орёл»fstec_bduRU
Сообщество свободного программного обеспечения Debian GNU/Linux≤ 9fstec_bduRU
Сообщество свободного программного обеспечения Debian GNU/Linux≤ 8fstec_bduRU
Сообщество свободного программного обеспечения Debian GNU/Linux≤ 10fstec_bduRU
debian debian linux= 8.0nvdUScpe:2.3:o:debian:debian_linux:*:*:*:*:*:*:*:*
redhat enterprise linux= 6.0nvdUScpe:2.3:o:redhat:enterprise_linux:*:*:*:*:*:*:*:*
redhat enterprise linux= 7.0nvdUScpe:2.3:o:redhat:enterprise_linux:*:*:*:*:*:*:*:*
samba samba< 4.4.12nvdUScpe:2.3:a:samba:samba:*:*:*:*:*:*:*:*
samba samba4.5.0 → 4.5.7nvdUScpe:2.3:a:samba:samba:*:*:*:*:*:*:*:*
samba samba4.6.0 → 4.6.1nvdUScpe:2.3:a:samba:samba:*:*:*:*:*:*:*:*
ctdb-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 Samba on RHEL-7all versionsfixedredhat_csafUS
ctdb-0:4.6.3-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6all versionsfixedredhat_csafUS
ctdb-tests-0:4.6.3-4.el7rhgs.x86_64 as a component of Red Hat Gluster 3.2 Samba on RHEL-7all versionsfixedredhat_csafUS
ctdb-tests-0:4.6.3-5.el6rhs.x86_64 as a component of Red Hat Gluster 3.3 Samba on RHEL-6all versionsfixedredhat_csafUS

showing 20 of 96

advisories (2)

Vendor and ecosystem advisories describing this.

RHSA-2017:2338Red Hat Security Advisory: samba security update2017-08-01csaf · redhat_csafUS
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.
RHSA-2017:2778Red Hat Security Advisory: samba security, bug fix, and enhancement update2017-09-21csaf · redhat_csafUS
An update for samba is now available for Red Hat Gluster Storage 3.3 for RHEL 6. 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.

also known as (4)

Other names and identifiers for this entity.

sources

Which sources assert this record, and when.

cnnvd enisa_euvd fstec_bdu nvd redhat_csaf NVD CVE.org MITRE

published 2018-03-12modified 2026-06-17

related (6,474)

Related entries.

ID	severity	EPSS	exploitable	published
CVE-2026-81963US	high7.8OT critical	0.39% (33rd)	KEV	2026-09-08
Improper link resolution before file access ('link following') in Windows Update Stack allows an authorized attacker to elevate privileges locally.
CVE-2026-41091US	—OT critical	8.20% (95th)	KEV	2026-05-20
Improper link resolution before file access ('link following') in Microsoft Defender allows an authorized attacker to elevate privileges locally.
CVE-2025-62215US	—OT critical	4.46% (91st)	KEV	2025-11-11
Concurrent execution using shared resource with improper synchronization ('race condition') in Windows Kernel allows an authorized attacker to elevate privileges locally.
CVE-2025-60710US	—OT critical	4.61% (92nd)	KEV	2025-11-11
Improper link resolution before file access ('link following') in Host Process for Windows Tasks allows an authorized attacker to elevate privileges locally.
CVE-2025-39964US	medium5.5OT critical	1.57% (75th)	KEV	2025-10-13
In the Linux kernel, the following vulnerability has been resolved: crypto: af_alg - Disallow concurrent writes in af_alg_sendmsg Issuing two writes to the same af_alg socket is…

+6469 more

references (34)

External citations — patches, advisories, analysis.

scry

Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.

Free scan