Public Date:
1488400: CVE-2017-12150 samba: Some code path don't enforce smb signing, when they should
It was found that samba did not enforce "SMB signing" when certain configuration options were enabled. A remote attacker could launch a man-in-the-middle attack and retrieve information in plain-text.

Find out more about CVE-2017-12150 from the MITRE CVE dictionary dictionary and NIST NVD.

CVSS v3 metrics

CVSS3 Base Score 7.4
CVSS3 Base Metrics CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Attack Vector Network
Attack Complexity High
Privileges Required None
User Interaction None
Scope Unchanged
Confidentiality High
Integrity Impact High
Availability Impact None

Red Hat Security Errata

Platform Errata Release Date
Red Hat Enterprise Linux 7 (samba) RHSA-2017:2790 2017-09-21
Red Hat Enterprise Linux 6 (samba4) RHSA-2017:2791 2017-09-21
Red Hat Enterprise Linux 6 (samba) RHSA-2017:2789 2017-09-21
Red Hat Gluster 3.3 Samba on RHEL-6 (samba) RHSA-2017:2858 2017-10-04
Red Hat Gluster 3.3 Samba on RHEL-7 (samba) RHSA-2017:2858 2017-10-04

Affected Packages State

Platform Package State
Red Hat Enterprise Linux 5 samba Will not fix
Red Hat Enterprise Linux 5 samba3x Will not fix
Unless explicitly stated as not affected, all previous versions of packages in any minor update stream of a product listed here should be assumed vulnerable, although may not have been subject to full analysis.


Red Hat would like to thank the Samba project for reporting this issue. Upstream acknowledges Stefan Metzmacher (SerNet) as the original reporter.


The missing implied signing for 'smb2mount -e', 'smbcacls -e' and 'smbcquotas -e' can be enforced by explicitly using '--signing=required' on the commandline or "client signing = required" in smb.conf.

External References

Last Modified