CVSS2
Attack Vector
NETWORK
Attack Complexity
LOW
Authentication
NONE
Confidentiality Impact
COMPLETE
Integrity Impact
COMPLETE
Availability Impact
COMPLETE
AV:N/AC:L/Au:N/C:C/I:C/A:C
CVSS3
Attack Vector
LOCAL
Attack Complexity
HIGH
Privileges Required
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
HIGH
Integrity Impact
HIGH
Availability Impact
HIGH
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
AI Score
Confidence
High
EPSS
Percentile
96.7%
This security update includes quality improvements. No new operating system features are being introduced in this update. Key changes include:
Security updates to Windows kernel, ASP.NET, Internet Explorer 11, Windows Search, Windows Storage and File Systems, Datacenter Networking, Windows Virtualization, Windows Server, Windows shell, Microsoft NTFS, Microsoft PowerShell, Windows Kernel-Mode Drivers, and Microsoft Graphics Component.
For more information about the security vulnerabilities resolved, please refer to the Security Update Guide.More InformationImportant
After installing the security updates for CVE-2017-8563, administrators need to set registry key LdapEnforceChannelBinding to enable the fix for the CVE. For more information about setting the registry key, see Microsoft Knowledge Base article 4034879.
Symptom | Workaround |
---|---|
After installing KB4025333 powershell may fail with a “Method not found” error (if you didn’t have KB3000850 installed) | This issue has been resolved by KB4038792. |
If an iSCSI target becomes unavailable, attempts to reconnect will cause a leak. Initiating a new connection to an available target will work as expected. | Microsoft is working on a resolution and will provide an update in an upcoming release. |
Japanese IME may hang in certain scenarios. | Install KB2962409 |
__
More Information about the iSCSI issue
Windows Server 2012 R2 and Server 2016 computers that experience disconnections to iSCSI attached targets may show many different symptoms. These include, but are not limited to:
This issue is caused by a locking issue on Windows Server 2012 R2 and Windows Server 2016 RS1 computers, causing connectivity issues to the iSCSI targets. The issue can occur after installing any of the following updates:Windows Server 2012 R2Release date | KB | Article title |
---|---|---|
May 16, 2017 | KB4015553 | April 18, 2017—KB4015553 (Preview of Monthly Rollup) |
May 9, 2017 | KB4019215 | May 9, 2017—KB4019215 (Monthly Rollup) |
May 9, 2017 | KB4019213 | May 9, 2017—KB4019213 (Security-only update) |
April 18, 2017 | KB4015553 | April 18, 2017—KB4015553 (Preview of Monthly Rollup) |
April 11, 2017 | KB4015550 | April 11, 2017—KB4015550 (Monthly Rollup) |
April 11, 2017 | KB4015547 | April 11, 2017—KB4015547 (Security-only update) |
March 21, 2017 | KB4012219 | March 2017 Preview of Monthly Quality Rollup for Windows 8.1 and Windows Server 2012 R2 |
**Windows Server 2016 RTM (RS1)**Release date | KB | Article title |
— | — | — |
May 16, 2017 | KB4023680 | May 26, 2017—KB4023680 (OS Build 14393.1230) |
May 9, 2017 | KB4019472 | May 9, 2017—KB4019472 (OS Build 14393.1198) |
April 11, 2017 | KB4015217 | April 11, 2017—KB4015217 (OS Build 14393.1066 and 14393.1083) |
Verification
c:\windows\system32\drivers\msiscsi.sys
The version that will expose this behavior is 6.3.9600.18624 for Windows Server 2012 R2 and version 10.0.14393.1066 for Windows Server 2016.
* The following events are logged in the System log:Event source | ID | Text |
---|---|---|
iScsiPrt | 34 | A connection to the target was lost, but the Initiator successfully reconnected to the target. Dump data contains the target name. |
iScsiPrt | 39 | The Initiator sent a task management command to reset the target. The target name is given in the dump data. |
iScsiPrt | 9 | Target did not respond in time for a SCSI request. The CDB is given in the dump data. |
Get-NetTCPConnection | Group-Object -Property State, OwningProcess | Sort Count
Or, from an administrative CMD prompt, run the following NETSTAT command together with the “Q” switch. This shows “bound” ports that are no longer connected:
NETSTAT –ANOQ
Focus on ports that are owned by the SYSTEM process.
For the three previous points, anything more than 12,000 should be considered suspect. If iSCSI targets are present in the computer, there is high probability that the issue will occur.
Resolution
If the event logs indicate that many reconnections are occurring, work with your iSCSI and network fabric vendor to help diagnose and correct the reason for the failure to maintain connections to iSCSI targets. Make sure that iSCSI targets can be accessed over the current network fabric. Install updated fixes when they become available. This article will be updated with the specific KB article number of the fix to install when it becomes available.
Note: We do not recommend that you uninstall any of the March, April, May, or June security rollups. Doing so will expose the computers to known security exploits and other bugs that are mitigated by monthly updates. We recommend that you first work with iSCSI target and network vendors to resolve the connectivity issues that are triggering target reconnects.
How to get this updateTo get the standalone package for this update, go to the Microsoft Update Catalog website.File informationFor a list of the files that are provided in this update, download the file information for update 4025333. Prerequisites You must have the following update installed:2919355 Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 update: April 2014
CVSS2
Attack Vector
NETWORK
Attack Complexity
LOW
Authentication
NONE
Confidentiality Impact
COMPLETE
Integrity Impact
COMPLETE
Availability Impact
COMPLETE
AV:N/AC:L/Au:N/C:C/I:C/A:C
CVSS3
Attack Vector
LOCAL
Attack Complexity
HIGH
Privileges Required
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
HIGH
Integrity Impact
HIGH
Availability Impact
HIGH
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
AI Score
Confidence
High
EPSS
Percentile
96.7%