Skip to content
Fencer Intel
high 8.1

CVE-2017-0272 in the critical feed json

The Microsoft Server Message Block 1.0 (SMBv1) server on Microsoft Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8.1, Windows…

published 2017-05-12 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-0628

cvss
8.1
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
17.1%
EPSS 17.1% chance of exploitation in 30 days, percentile 97%
public exploits
0
none known

Summary

The Microsoft Server Message Block 1.0 (SMBv1) server on Microsoft Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8.1, Windows Server 2012 Gold and R2, Windows RT 8.1, Windows 10 Gold, 1511, 1607, and 1703, and Windows Server 2016 allows an attacker to execute remote code by the way it handles certain requests, aka "Windows SMB Remote Code Execution Vulnerability". This CVE ID is unique from CVE-2017-0277, CVE-2017-0278, and CVE-2017-0279.

Patch / fix

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSMA-18-058-02 updated cvss 8.1

Philips Intellispace Portal ISP Vulnerabilities

  • Phillips IntelliSpace Portal 7.0.x Phillips IntelliSpace Portal 8.0.x
    affected: mitigation “Users with questions regarding their specific ISP installations are advised by Philips to contact their local Philips service support team or their regional service support.” usa.philips.com

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

Exploit prediction

17.12% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 8.1 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 9.3 AV:N/AC:M/Au:N/C:C/I:C/A:C

Affected products

  • Microsoft Corporation Server Message Block 1.0

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.