First published: Thu Dec 10 2015(Updated: )
As per upstream samba advisory: Versions of Samba from 3.2.0 to 4.3.2 inclusive do not ensure that signing is negotiated when creating an encrypted client connection to a server. Without this a man-in-the-middle attack could downgrade the connection and connect using the supplied credentials as an unsigned, unencrypted connection. The following mitigation was suggested by upstream: When using the smbclient command, always add the argument "--signing=required" when using the "-e" or "--encrypt" argument. Alternatively, set the variable "client signing = mandatory" in the [global] section of the smb.conf file on any client using encrypted connections. To protect a Samba server exporting encrypted shares against a downgrade attack set the variable "smb encrypt = mandatory" in the smb.conf definition of the encrypted shares.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Samba Samba | >=3.2.0<4.1.22 | |
Samba Samba | >=4.2.0<4.2.7 | |
Samba Samba | >=4.3.0<4.3.3 | |
Debian Debian Linux | =7.0 | |
Debian Debian Linux | =8.0 | |
Canonical Ubuntu Linux | =12.04 | |
Canonical Ubuntu Linux | =14.04 | |
Canonical Ubuntu Linux | =15.04 | |
Canonical Ubuntu Linux | =15.10 | |
redhat/samba | <4.1.22 | 4.1.22 |
redhat/samba | <4.2.7 | 4.2.7 |
redhat/samba | <4.3.3 | 4.3.3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.