CVE-2017-12151
CVE-2017-12151 Vulnerability Analysis & Exploit Intelligence
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.
Published Updated Sources: cvelistV5, redhat
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Unreported
no source claims exploitation
EPSS
5%
chance of exploitation in 30 days
CVSS base
7.4
HIGH
Affected scope
The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.
Vendors (1)
Products (1)
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 7.4 | CVSS 3.0 | HIGH | — | — | cvelistV5 |
Weakness & attack patterns
- CWE-300
Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.
- T1040Network Sniffing
- T1185Man in the Browser
- T1557Adversary-in-the-Middle
References
9 on the record
- security.netapp.com/advisory/ntap-20170921-0001/
x_refsource_CONFIRM
- access.redhat.com/errata/RHSA-2017:2790
vendor-advisory, x_refsource_REDHAT
- bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-12151
x_refsource_CONFIRM
- www.securityfocus.com/bid/100917
vdb-entry, x_refsource_BID
- support.hpe.com/hpsc/doc/public/display?docLocale=en_US&docId=emr_na-hpesbux03817en_us
x_refsource_CONFIRM
- www.debian.org/security/2017/dsa-3983
vendor-advisory, x_refsource_DEBIAN
- access.redhat.com/errata/RHSA-2017:2858
vendor-advisory, x_refsource_REDHAT
- www.securitytracker.com/id/1039401
vdb-entry, x_refsource_SECTRACK
Elsewhere on this site
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.