Home › Intelligence › Brief
VULNERABILITY BRIEF🔴 Critical Vulnerability

Critical SMBv1 Remote Code Execution Vulnerability (CVE‑2017‑0145) Impacts Windows Systems

CVE‑2017‑0145 is a critical remote‑code‑execution flaw in Microsoft’s SMBv1 server that can be triggered by crafted network packets. It affects legacy Windows versions that still run SMBv1, and it underscores the need for robust vulnerability‑management controls to satisfy audit and compliance expectations.

LiveThreat™ Intelligence · 📅 October 07, 2026· 📰 nvd.nist.gov
🔴
Severity
Critical
VU
Type
Vulnerability
🎯
Confidence
High
🏢
Affected
1 sector(s)
✅
Actions
4 recommended
📰
Source
nvd.nist.gov

Critical SMBv1 Remote Code Execution Vulnerability (CVE‑2017‑0145) Impacts Windows Systems

What It Is – CVE‑2017‑0145 is a remote code execution flaw in the SMBv1 server component of multiple Microsoft Windows releases. Crafted SMB packets can trigger arbitrary code execution with SYSTEM privileges.

Exploitability – Actively exploited in the wild (e.g., the “EternalBlue” attacks). CVSS v3.1 base score 9.8 (Critical). Public PoCs and exploit kits are available.

Affected Products – Microsoft Windows 7, Windows Server 2008 R2, Windows Server 2012, and other legacy Windows versions that still have SMBv1 enabled.

Why It Matters for Trust & Control Assurance

  • Demonstrates the need for continuous vulnerability‑management controls (identifying, patching, and de‑commissioning insecure protocols) that map to a single VCF control objective and satisfy multiple frameworks (e.g., NIST CSF 2.0, ISO 27001).
  • Provides concrete evidence for auditors that you maintain a defensible audit trail of patch deployment and protocol hardening.
  • Highlights the importance of continuous control monitoring to prove due‑diligence when enterprise buyers demand verifiable trust signals.

Recommended Actions

  • Deploy Microsoft’s security update that disables SMBv1 or patches the flaw.
  • Verify remediation via authenticated scanning or endpoint detection tools.
  • If SMBv1 is not required, permanently disable the protocol through Group Policy or system configuration.
  • Document the remediation steps in your control evidence repository to support audit readiness.

Source: CISA KEV – CVE‑2017‑0145

📰 Original Source
https://nvd.nist.gov/vuln/detail/CVE-2017-0145 ↗

This LiveThreat Intelligence Brief is an independent analysis. Read the original reporting at the link above.

From the Verisq platform · Trust Operations

Answer one control objective. Answer ten frameworks.

The Verisq Common Framework is a spine of 84 control objectives that SOC 2, ISO 27001, NIST CSF, CMMC, HIPAA, PCI DSS, HITRUST, GDPR, ISO 42001 and NIST AI RMF map onto — each graded honestly. Satisfy an objective once and every framework that recognizes it lights up at its real strength.

See how the Verisq Common Framework works →