A flaw was found in the way samba client before samba 4.4.16, samba 4.5.14 and samba 4.6.8 used encryption with the max protocol set as SMB3. The connection could lose the requirement for signing and encrypting to any DFS redirects, allowing an attacker to read or alter the contents of the connection via a man-in-the-middle attack.
The product does not adequately verify the identity of actors at both ends of a communication channel, or does not adequately ensure the integrity of the channel, in a way that allows the channel to be accessed or influenced by an actor that is not an endpoint.
Weaknesses in this category are related to the design and implementation of data confidentiality and integrity. Frequently these deal with the use of encoding techniques, encryption libraries, and hashing algorithms. The weaknesses in this category could lead to a degradation of the quality data if they are not addressed.
Link | Tags |
---|---|
https://security.netapp.com/advisory/ntap-20170921-0001/ | third party advisory |
https://access.redhat.com/errata/RHSA-2017:2790 | third party advisory vendor advisory |
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-12151 | issue tracking third party advisory |
http://www.securityfocus.com/bid/100917 | vdb entry third party advisory |
https://support.hpe.com/hpsc/doc/public/display?docLocale=en_US&docId=emr_na-hpesbux03817en_us | third party advisory |
https://www.debian.org/security/2017/dsa-3983 | third party advisory vendor advisory |
https://access.redhat.com/errata/RHSA-2017:2858 | third party advisory vendor advisory |
http://www.securitytracker.com/id/1039401 | vdb entry third party advisory |
https://www.samba.org/samba/security/CVE-2017-12151.html | mitigation vendor advisory |