Issued:

2014-04-09

Updated:

2014-04-09

RHSA-2014:0383 - Moderate: samba4 security update

Synopsis

Moderate: samba4 security update

Type/Severity

Security Advisory Moderate

Topic

Updated samba4 packages that fix three security issues are now available for Red Hat Enterprise Linux 6.

The Red Hat Security Response Team has rated this update as having Moderate security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.

Description

Samba is an open-source implementation of the Server Message Block (SMB) or Common Internet File System (CIFS) protocol, which allows PC-compatible machines to share files, printers, and other information.

It was found that certain Samba configurations did not enforce the password lockout mechanism. A remote attacker could use this flaw to perform password guessing attacks on Samba user accounts. Note: this flaw only affected Samba when deployed as a Primary Domain Controller. (CVE-2013-4496)

A flaw was found in Samba's "smbcacls" command, which is used to set or get ACLs on SMB file shares. Certain command line options of this command would incorrectly remove an ACL previously applied on a file or a directory, leaving the file or directory without the intended ACL. (CVE-2013-6442)

A flaw was found in the way the pam_winbind module handled configurations that specified a non-existent group as required. An authenticated user could possibly use this flaw to gain access to a service using pam_winbind in its PAM configuration when group restriction was intended for access to the service. (CVE-2012-6150)

Red Hat would like to thank the Samba project for reporting CVE-2013-4496 and CVE-2013-6442, and Sam Richardson for reporting CVE-2012-6150. Upstream acknowledges Andrew Bartlett as the original reporter of CVE-2013-4496, and Noel Power as the original reporter of CVE-2013-6442.

All users of Samba are advised to upgrade to these updated packages, which contain backported patches to correct these issues. After installing this update, the smb service will be restarted automatically.

Solution

Before applying this update, make sure all previously released errata relevant to your system have been applied.

This update is available via the Red Hat Network. Details on how to use the Red Hat Network to apply this update are available at https://access.redhat.com/site/articles/11258

Affected Products

Updated Packages

• samba4-debuginfo-4.0.0-61.el6_5.rc4.ppc64.rpm
• samba4-devel-4.0.0-61.el6_5.rc4.i686.rpm
• samba4-winbind-krb5-locator-4.0.0-61.el6_5.rc4.ppc64.rpm
• samba4-4.0.0-61.el6_5.rc4.x86_64.rpm
• samba4-common-4.0.0-61.el6_5.rc4.i686.rpm
• samba4-pidl-4.0.0-61.el6_5.rc4.s390x.rpm
• samba4-python-4.0.0-61.el6_5.rc4.x86_64.rpm
• samba4-debuginfo-4.0.0-61.el6_5.rc4.s390x.rpm
• samba4-libs-4.0.0-61.el6_5.rc4.s390x.rpm
• samba4-winbind-clients-4.0.0-61.el6_5.rc4.s390x.rpm
• samba4-test-4.0.0-61.el6_5.rc4.i686.rpm
• samba4-client-4.0.0-61.el6_5.rc4.i686.rpm
• samba4-common-4.0.0-61.el6_5.rc4.x86_64.rpm
• samba4-python-4.0.0-61.el6_5.rc4.i686.rpm
• samba4-dc-libs-4.0.0-61.el6_5.rc4.ppc64.rpm
• samba4-swat-4.0.0-61.el6_5.rc4.i686.rpm
• samba4-devel-4.0.0-61.el6_5.rc4.x86_64.rpm
• samba4-libs-4.0.0-61.el6_5.rc4.i686.rpm
• samba4-4.0.0-61.el6_5.rc4.src.rpm
• samba4-libs-4.0.0-61.el6_5.rc4.ppc64.rpm
• samba4-common-4.0.0-61.el6_5.rc4.ppc64.rpm
• samba4-winbind-4.0.0-61.el6_5.rc4.x86_64.rpm
• samba4-dc-4.0.0-61.el6_5.rc4.i686.rpm
• samba4-swat-4.0.0-61.el6_5.rc4.x86_64.rpm
• samba4-libs-4.0.0-61.el6_5.rc4.x86_64.rpm
• samba4-winbind-4.0.0-61.el6_5.rc4.s390x.rpm
• samba4-pidl-4.0.0-61.el6_5.rc4.x86_64.rpm
• samba4-winbind-krb5-locator-4.0.0-61.el6_5.rc4.x86_64.rpm
• samba4-debuginfo-4.0.0-61.el6_5.rc4.i686.rpm
• samba4-python-4.0.0-61.el6_5.rc4.ppc64.rpm
• samba4-pidl-4.0.0-61.el6_5.rc4.i686.rpm
• samba4-test-4.0.0-61.el6_5.rc4.ppc64.rpm
• samba4-swat-4.0.0-61.el6_5.rc4.ppc64.rpm
• samba4-client-4.0.0-61.el6_5.rc4.ppc64.rpm
• samba4-dc-libs-4.0.0-61.el6_5.rc4.s390x.rpm
• samba4-4.0.0-61.el6_5.rc4.s390x.rpm
• samba4-winbind-krb5-locator-4.0.0-61.el6_5.rc4.s390x.rpm
• samba4-winbind-clients-4.0.0-61.el6_5.rc4.x86_64.rpm
• samba4-client-4.0.0-61.el6_5.rc4.s390x.rpm
• samba4-common-4.0.0-61.el6_5.rc4.s390x.rpm
• samba4-test-4.0.0-61.el6_5.rc4.s390x.rpm
• samba4-dc-libs-4.0.0-61.el6_5.rc4.i686.rpm
• samba4-pidl-4.0.0-61.el6_5.rc4.ppc64.rpm
• samba4-winbind-clients-4.0.0-61.el6_5.rc4.i686.rpm
• samba4-test-4.0.0-61.el6_5.rc4.x86_64.rpm
• samba4-client-4.0.0-61.el6_5.rc4.x86_64.rpm
• samba4-winbind-krb5-locator-4.0.0-61.el6_5.rc4.i686.rpm
• samba4-4.0.0-61.el6_5.rc4.ppc64.rpm
• samba4-4.0.0-61.el6_5.rc4.i686.rpm
• samba4-devel-4.0.0-61.el6_5.rc4.s390x.rpm
• samba4-winbind-clients-4.0.0-61.el6_5.rc4.ppc64.rpm
• samba4-swat-4.0.0-61.el6_5.rc4.s390x.rpm
• samba4-dc-libs-4.0.0-61.el6_5.rc4.x86_64.rpm
• samba4-winbind-4.0.0-61.el6_5.rc4.ppc64.rpm
• samba4-dc-4.0.0-61.el6_5.rc4.s390x.rpm
• samba4-dc-4.0.0-61.el6_5.rc4.ppc64.rpm
• samba4-dc-4.0.0-61.el6_5.rc4.x86_64.rpm
• samba4-python-4.0.0-61.el6_5.rc4.s390x.rpm
• samba4-debuginfo-4.0.0-61.el6_5.rc4.x86_64.rpm
• samba4-winbind-4.0.0-61.el6_5.rc4.i686.rpm
• samba4-devel-4.0.0-61.el6_5.rc4.ppc64.rpm

Fixes

• This content is not included.BZ - 1036897
• This content is not included.BZ - 1044099
• This content is not included.BZ - 1072792

CVEs

• CVE-2013-4496
• CVE-2012-6150
• CVE-2013-6442

References

• https://access.redhat.com/security/updates/classification/#moderate
• Content from www.samba.org is not included.Content from www.samba.org is not included.https://www.samba.org/samba/security/CVE-2012-6150
• Content from www.samba.org is not included.Content from www.samba.org is not included.https://www.samba.org/samba/security/CVE-2013-4496
• Content from www.samba.org is not included.Content from www.samba.org is not included.https://www.samba.org/samba/security/CVE-2013-6442

Additional information

• The Red Hat security contact is This content is not included.secalert@redhat.com. More contact details at https://access.redhat.com/security/team/contact/.
• Offline Security Data data is available for integration with other systems. See Offline Security Data API to get started.