All versions of Samba are vulnerable to a server memory information leak bug over SMB1 if a client can write data to a share. Some SMB1 write requests were not correctly range checked to ensure the client had sent enough data to fulfill the write, allowing server memory contents to be written into the file (or printer) instead of client supplied data. The client cannot control the area of the server memory that is written to the file (or printer).
Mitigation: As this is an SMB1-only vulnerability, it can be avoided by setting the server to only use SMB2 via adding: server min protocol = SMB2_02 to the [global] section of your smb.conf and restarting smbd.
Acknowledgments: Name: Yihan Lian and Zhibin Hu (Qihoo 360 Gear Team), Stefan Metzmacher (SerNet), Jeremy Allison (Google)
External References: https://www.samba.org/samba/security/CVE-2017-12163.html
Created samba tracking bugs for this issue: Affects: fedora-all [bug 1493441]
This issue has been addressed in the following products: Red Hat Enterprise Linux 6 Via RHSA-2017:2791 https://access.redhat.com/errata/RHSA-2017:2791
This issue has been addressed in the following products: Red Hat Enterprise Linux 7 Via RHSA-2017:2790 https://access.redhat.com/errata/RHSA-2017:2790
This issue has been addressed in the following products: Red Hat Enterprise Linux 6 Via RHSA-2017:2789 https://access.redhat.com/errata/RHSA-2017:2789
This issue has been addressed in the following products: Red Hat Gluster Storage 3.3 for RHEL 6 Red Hat Gluster Storage 3.3 for RHEL 7 Via RHSA-2017:2858 https://access.redhat.com/errata/RHSA-2017:2858