HOW TO BE SAFE FROM RANSOMEWARE "TEMPORARY"
Security Update for Microsoft Windows SMB Server (4013389)
Executive Summary
This security update resolves vulnerabilities in Microsoft Windows. The most severe of the vulnerabilities could allow remote code execution if an attacker sends specially crafted messages to a Microsoft Server Message Block 1.0 (SMBv1) server.
This security update is rated Critical for all supported releases of Microsoft Windows. For more information, see the Affected Software and Vulnerability Severity Ratings section.
The security update addresses the vulnerabilities by correcting how SMBv1 handles specially crafted requests.
For more information about the vulnerabilities, see the Vulnerability Information section.
For more information about this update, see Microsoft Knowledge Base Article 4013389
Operating System
|
Updates Replaced
| ||||||
Windows Vista
| |||||||
Windows Vista Service Pack 2
(4012598) |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Important
Information Disclosure |
Critical
Remote Code Execution |
3177186 in MS16-114
|
Windows Vista x64 Edition Service Pack 2
(4012598) |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Important
Information Disclosure |
Critical
Remote Code Execution |
3177186 in MS16-114
|
Windows Server 2008
| |||||||
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Important
Information Disclosure |
Critical
Remote Code Execution |
3177186 in MS16-114
| |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Important
Information Disclosure |
Critical
Remote Code Execution |
3177186 in MS16-114
| |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Important
Information Disclosure |
Critical
Remote Code Execution |
3177186 in MS16-114
| |
Windows 7
| |||||||
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Important
Information Disclosure |
Critical
Remote Code Execution |
None
| |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Important
Information Disclosure |
Critical
Remote Code Execution | ||
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Important
Information Disclosure |
Critical
Remote Code Execution |
None
| |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Important
Information Disclosure |
Critical
Remote Code Execution | ||
Windows Server 2008 R2
| |||||||
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Important
Information Disclosure |
Critical
Remote Code Execution |
None
| |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Important
Information Disclosure |
Critical
Remote Code Execution | ||
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Important
Information Disclosure |
Critical
Remote Code Execution |
None
| |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Important
Information Disclosure |
Critical
Remote Code Execution | ||
Windows 8.1
| |||||||
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Important
Information Disclosure |
Critical
Remote Code Execution |
None
| |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Important
Information Disclosure |
Critical
Remote Code Execution | ||
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Important
Information Disclosure |
Critical
Remote Code Execution |
None
| |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Important
Information Disclosure |
Critical
Remote Code Execution | ||
Windows Server 2012 and Windows Server 2012 R2
| |||||||
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Important
Information Disclosure |
Critical
Remote Code Execution |
None
| |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Important
Information Disclosure |
Critical
Remote Code Execution | ||
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Important
Information Disclosure |
Critical
Remote Code Execution |
None
| |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Important
Information Disclosure |
Critical
Remote Code Execution | ||
Windows RT 8.1
| |||||||
Windows RT 8.1[2]
(4012216) Monthly Rollup |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Important
Information Disclosure |
Critical
Remote Code Execution | |
Windows 10
| |||||||
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Important
Information Disclosure |
Critical
Remote Code Execution | ||
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Important
Information Disclosure |
Critical
Remote Code Execution | ||
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Important
Information Disclosure |
Critical
Remote Code Execution | ||
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Important
Information Disclosure |
Critical
Remote Code Execution | ||
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Important
Information Disclosure |
Critical
Remote Code Execution | ||
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Important
Information Disclosure |
Critical
Remote Code Execution | ||
Windows Server 2016
| |||||||
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Important
Information Disclosure |
Critical
Remote Code Execution | ||
Server Core installation option
| |||||||
Windows Server 2008 for 32-bit Systems Service Pack 2(Server Core installation)
(4012598) |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Important
Information Disclosure |
Critical
Remote Code Execution |
3177186 in MS16-114
|
Windows Server 2008 for x64-based Systems Service Pack 2(Server Core installation)
(4012598) |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Important
Information Disclosure |
Critical
Remote Code Execution |
3177186 in MS16-114
|
Windows Server 2008 R2 for x64-based Systems Service Pack 1(Server Core installation)
(4012212) Security Only[1] |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Important
Information Disclosure |
Critical
Remote Code Execution |
None
|
Windows Server 2008 R2 for x64-based Systems Service Pack 1(Server Core installation)
(4012215) Monthly Rollup[1] |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Important
Information Disclosure |
Critical
Remote Code Execution | |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Important
Information Disclosure |
Critical
Remote Code Execution |
None
| |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Important
Information Disclosure |
Critical
Remote Code Execution | ||
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Important
Information Disclosure |
Critical
Remote Code Execution |
None
| |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Important
Information Disclosure |
Critical
Remote Code Execution | ||
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Critical
Remote Code Execution |
Important
Information Disclosure |
Critical
Remote Code Execution |
[1]Beginning with the October 2016 release, Microsoft has changed the update servicing model for Windows 7, Windows Server 2008 R2, Windows 8.1, Windows Server 2012, and Windows Server 2012 R2. For more information, please see this Microsoft TechNet article.
[2]This update is only available via Windows Update.
[3] Windows 10 and Windows Server 2016 updates are cumulative. The monthly security release includes all security fixes for vulnerabilities that affect Windows 10, in addition to non-security updates. The updates are available via the Microsoft Update Catalog. Please note that effective December 13, 2016, Windows 10 and Windows Server 2016 details for the Cumulative Updates will be documented in Release Notes. Please refer to the Release Notes for OS Build numbers, Known Issues, and affected file list information.
*The Updates Replaced column shows only the latest update in any chain of superseded updates. For a comprehensive list of updates replaced, go to the Microsoft Update Catalog, search for the update KB number, and then view update details (updates replaced information is provided on the Package Details tab).
Vulnerability Information
Multiple Windows SMB Remote Code Execution Vulnerabilities
Remote code execution vulnerabilities exist in the way that the Microsoft Server Message Block 1.0 (SMBv1) server handles certain requests. An attacker who successfully exploited the vulnerabilities could gain the ability to execute code on the target server.
To exploit the vulnerability, in most situations, an unauthenticated attacker could send a specially crafted packet to a targeted SMBv1 server.
The security update addresses the vulnerabilities by correcting how SMBv1 handles these specially crafted requests.
The following table contains links to the standard entry for each vulnerability in the Common Vulnerabilities and Exposures list:
Vulnerability title
|
CVE number
|
Publicly disclosed
|
Exploited
|
Windows SMB Remote Code Execution Vulnerability
|
No
|
No
| |
Windows SMB Remote Code Execution Vulnerability
|
No
|
No
| |
Windows SMB Remote Code Execution Vulnerability
|
No
|
No
| |
Windows SMB Remote Code Execution Vulnerability
|
No
|
No
| |
Windows SMB Remote Code Execution Vulnerability
|
No
|
No
|
Mitigating Factors
Microsoft has not identified any mitigating factors for these vulnerabilities.
Workarounds
The following workarounds may be helpful in your situation:
- Disable SMBv1For customers running Windows Vista and laterAlternative method for customers running Windows 8.1 or Windows Server 2012 R2 and laterFor client operating systems:
- Open Control Panel, click Programs, and then click Turn Windows features on or off.
- In the Windows Features window, clear the SMB1.0/CIFS File Sharing Support checkbox, and then click OK to close the window.
- Restart the system.
For server operating systems:- Open Server Manager and then click the Manage menu and select Remove Roles and Features.
- In the Features window, clear the SMB1.0/CIFS File Sharing Support check box, and then click OK to close the window.
- Restart the system.
Impact of workaround. The SMBv1 protocol will be disabled on the target system.How to undo the workaround. Retrace the workaround steps, and select the SMB1.0/CIFS File Sharing Support check box to restore the SMB1.0/CIFS File Sharing Support feature to an active state.
Windows SMB Information Disclosure Vulnerability – CVE-2017-0147
An information disclosure vulnerability exists in the way that the Microsoft Server Message Block 1.0 (SMBv1) server handles certain requests. An attacker who successfully exploited this vulnerability could craft a special packet, which could lead to information disclosure from the server.
To exploit the vulnerability, in most situations, an unauthenticated attacker could send a specially crafted packet to a targeted SMBv1 server.
The security update addresses the vulnerability by correcting how SMBv1 handles these specially crafted requests.
The following table contains links to the standard entry for each vulnerability in the Common Vulnerabilities and Exposures list:
Vulnerability title
|
CVE number
|
Publicly disclosed
|
Exploited
|
Windows SMB Information Disclosure Vulnerability
|
No
|
No
|
Mitigating Factors
Microsoft has not identified any mitigating factors for this vulnerability.
Workarounds
The following workarounds may be helpful in your situation:
- Disable SMBv1For customers running Windows Vista and laterAlternative method for customers running Windows 8.1 or Windows Server 2012 R2 and laterFor client operating systems:
- Open Control Panel, click Programs, and then click Turn Windows features on or off.
- In the Windows Features window, clear the SMB1.0/CIFS File Sharing Support checkbox, and then click OK to close the window.
- Restart the system.
For server operating systems:- Open Server Manager and then click the Manage menu and select Remove Roles and Features.
- In the Features window, clear the SMB1.0/CIFS File Sharing Support check box, and then click OK to close the window.
- Restart the system.
Impact of workaround. The SMBv1 protocol will be disabled on the target system.How to undo the workaround. Retrace the workaround steps, and select the SMB1.0/CIFS File Sharing Support check box to restore the SMB1.0/CIFS File Shar
No comments:
Post a Comment