A flaw was found in the way samba before 4.7.9 and 4.8.4 allowed the use of weak NTLMv1 authentication even when NTLMv1 was explicitly disabled. A man-in-the-middle attacker could use this flaw to read the credential and other details passed between the samba server and client.
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.
| Link | Tags |
|---|---|
| https://access.redhat.com/errata/RHSA-2018:2613 | third party advisory vendor advisory |
| https://usn.ubuntu.com/3738-1/ | third party advisory vendor advisory |
| https://access.redhat.com/errata/RHSA-2018:2612 | third party advisory vendor advisory |
| https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-1139 | third party advisory issue tracking |
| http://www.securityfocus.com/bid/105084 | third party advisory vdb entry |
| https://access.redhat.com/errata/RHSA-2018:3056 | third party advisory vendor advisory |
| https://security.netapp.com/advisory/ntap-20180814-0001/ | third party advisory |
| https://www.samba.org/samba/security/CVE-2018-1139.html | third party advisory |
| https://security.gentoo.org/glsa/202003-52 | third party advisory vendor advisory |