LiveActive security incident?Get immediate response
CVE Record

CVE-2017-12150: It was found that samba before 4.4.16, 4.5.x before 4.5.14, and 4.6.x before 4.6.8 did not enforce "SMB sig...

It was found that samba before 4.4.16, 4.5.x before 4.5.14, and 4.6.x before 4.6.8 did not enforce "SMB signing" when certain configuration options were enabled. A remote attacker could launch a man-in-the-middle attack and retrieve information in plain-text.

HighCVSS 7.4Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This Samba flaw could cause organizations to believe SMB traffic was protected by signing when, under certain configurations, it was not enforced. An attacker positioned between client and server could intercept traffic and read sensitive information in clear text. The source bundle does not show confirmed active exploitation.

Executive priority

Treat this as a high-priority legacy remediation item wherever Samba still supports business file sharing or identity workflows. The urgency is greatest on networks where attackers could gain local network position or intercept east-west traffic.

Technical view

CVE-2017-12150 is a CWE-300 channel security weakness in Samba. Before 4.4.16, 4.5.14, and 4.6.8, Samba did not enforce SMB signing when certain options were enabled, enabling unauthenticated network man-in-the-middle attacks with high confidentiality and integrity impact.

Likely exposure

Exposure is most likely where Samba provides SMB file or domain services on untrusted, shared, or segmented networks and relies on SMB signing for protection. Internet exposure is not required; an attacker needs a network position between SMB clients and servers.

Exploitation context

The CVSS vector is network, high complexity, no privileges, and no user interaction. The bundle marks KEV as false and provides no cited evidence of active exploitation. The practical prerequisite is man-in-the-middle network positioning.

Researcher notes

The source bundle names affected Samba release ranges but does not include full configuration trigger details. Validate against the Samba advisory and downstream vendor errata before making product-specific exposure claims. Avoid assuming exploitation unless newer evidence is supplied.

Mitigation direction

  • Upgrade Samba to vendor-supported fixed packages for the deployed branch.
  • Use Samba 4.4.16, 4.5.14, 4.6.8, or later where applicable.
  • Review Samba, Red Hat, Debian, NetApp, and HPE guidance for product-specific packages.
  • Limit SMB access to trusted networks and reduce unnecessary network paths.
  • Confirm SMB signing expectations after patching using administrative configuration review.

Validation and detection

  • Inventory systems running Samba and record exact package versions.
  • Identify SMB services that rely on signing for confidentiality or integrity protection.
  • Check configuration for the specific signing-related options called out by vendor advisories.
  • Verify installed vendor packages include the CVE-2017-12150 fix.
  • Review network segmentation for paths allowing interception between SMB clients and servers.
Prepared
Confidence
high
Sources
10

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-300: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2017-12150 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.4 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
11Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.4CVSS 3.0HighCVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N2.25.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

7.4High
CVSS 3.0 vector shape for CVE-2017-12150Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Sambasamba4.6.8, 4.5.14, 4.4.16, 4.7.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-300 · source CWE mapping

Channel Accessible by Non-Endpoint

Channel Accessible by Non-Endpoint represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.