Security Update for Windows Diagnostic Hub (3165479)Published: June 14, 2016Version: 1.0This security update resolves a vulnerability in Microsoft Windows.
The vulnerability could allow elevation of privilege if an attacker logs on to an affected system and runs a specially crafted application.This security update is rated Important for all supported editions of Microsoft Windows 10.
For more information, see the Affected Software section.The security update addresses the vulnerability by correcting how the Windows Diagnostics Hub Standard Collector Service sanitizes input, to help preclude unintended elevated system privileges.
For more information about the vulnerability, see the Vulnerability Information section.For more information about this update, see Microsoft Knowledge Base Article 3165479. The following software versions or editions are affected.
Versions or editions that are not listed are either past their support life cycle or are not affected.
To determine the support life cycle for your software version or edition, see Microsoft Support Lifecycle.The severity ratings indicated for each affected software assume the potential maximum impact of the vulnerability.
For information regarding the likelihood, within 30 days of this security bulletin’s release, of the exploitability of the vulnerability in relation to its severity rating and security impact, please see the Exploitability Index in the June bulletin summary.Windows 10 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.*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).Note Windows Server 2016 Technical Preview 5 is affected.
Customers running this operating system are encouraged to apply the update, which is available via Windows Update.Windows Diagnostics Hub Elevation of Privilege Vulnerability – CVE-2016-3231An elevation of privilege vulnerability exists when the Windows Diagnostics Hub Standard Collector Service fails to properly sanitize input, leading to an unsecure library loading behavior.
An attacker who successfully exploited this vulnerability could run arbitrary code with elevated system privileges.
An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.To exploit this vulnerability, an attacker would have to log on to an affected system and run a specially crafted application.
The security update addresses the vulnerability by correcting how the Windows Diagnostics Hub Standard Collector Service sanitizes input, to help preclude unintended elevated system privileges.The following table contains a link to the standard entry for each vulnerability in the Common Vulnerabilities and Exposures list:
Windows Diagnostics Hub Elevation of Privilege Vulnerability
Mitigating FactorsMicrosoft has not identified any mitigating factors for this vulnerability.WorkaroundsThe Microsoft has not identified any workarounds for this vulnerability.For Security Update Deployment information, see the Microsoft Knowledge Base article referenced here in the Executive Summary. Microsoft recognizes the efforts of those in the security community who help us protect customers through coordinated vulnerability disclosure.
See Acknowledgments for more information. The information provided in the Microsoft Knowledge Base is provided “as is” without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose.
In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages.
Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.V1.0 (June 14, 2016): Bulletin published.
Page generated 2016-06-07 13:03-07:00.