Microsoft Security Bulletin MS16-109 - Important
Security Update for Silverlight (3182373)
Published: September 13, 2016
This security update resolves a vulnerability in Microsoft Silverlight. The vulnerability could allow remote code execution if a user visits a compromised website that contains a specially crafted Silverlight application. An attacker would have no way to force a user to visit a compromised website. Instead, an attacker would have to convince the user to visit the website, typically by enticing the user to click a link in either an email or instant message that takes the user to the attacker's website.
This security update is rated Important for Microsoft Silverlight 5 and Microsoft Silverlight 5 Developer Runtime when installed on Mac or all supported releases of Microsoft Windows. For more information, see the Affected Software section.
The update addresses the vulnerability by correcting how Microsoft Silverlight allocates memory for inserting and appending strings in StringBuilder. For more information about the vulnerabilities, see the Vulnerability Information section.
For more information about this update, see Microsoft Knowledge Base Article 3182373.
Affected Software and Vulnerability Severity Ratings
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 September bulletin summary.
|Developer Tools||Microsoft Silverlight Memory Corruption Vulnerability - CVE-2016-3367||Updates Replaced|
|Microsoft Silverlight 5 when installed on Mac (3182373)||Important Remote Code Execution||3126036 in MS16-006|
|Microsoft Silverlight 5 Developer Runtime when installed on Mac (3182373)||Important Remote Code Execution||3126036 in MS16-006|
|Microsoft Silverlight 5 when installed on all supported releases of Microsoft Windows clients (3182373)||Important Remote Code Execution||3126036 in MS16-006|
|Microsoft Silverlight 5 Developer Runtime when installed on all supported releases of Microsoft Windows clients (3182373)||Important Remote Code Execution||3126036 in MS16-006|
|Microsoft Silverlight 5 when installed on all supported releases of Microsoft Windows servers (3182373)||Important Remote Code Execution||3126036 in MS16-006|
|Microsoft Silverlight 5 Developer Runtime when installed on all supported releases of Microsoft Windows servers (3182373)||Important Remote Code Execution||3126036 in MS16-006|
Which web browsers support Microsoft Silverlight applications?
To run Microsoft Silverlight applications, most web browsers, including Microsoft Internet Explorer, require Microsoft Silverlight to be installed and the corresponding plug-in to be enabled. For more information about Microsoft Silverlight, see the official site, Microsoft Silverlight. Please refer to the documentation of your browser to learn more about how to disable or remove plug-ins.
What versions of Microsoft Silverlight 5 are affected by the vulnerabilities?
Microsoft Silverlight build 5.1.50709.0, which was the current build of Microsoft Silverlight as of when this bulletin was first released, addresses the vulnerabilities and is not affected. Builds of Microsoft Silverlight previous to 5.1.50709.0 are affected.
How do I know which version and build of Microsoft Silverlight is currently installed on my system?
If Microsoft Silverlight is already installed on your computer, you can visit the Get Microsoft Silverlight page, which will indicate which version and build of Microsoft Silverlight is currently installed on your system. Alternatively, you can use the Manage Add-Ons feature of current versions of Microsoft Internet Explorer to determine the version and build information that is currently installed on your system.
You can also manually check the version number of sllauncher.exe located in the "%ProgramFiles%\Microsoft Silverlight" directory (on x86 Microsoft Windows systems) or in the "%ProgramFiles(x86)%\Microsoft Silverlight" directory (on x64 Microsoft Windows systems).
In addition, on Microsoft Windows, the version and build information of the currently installed version of Microsoft Silverlight can be found in the registry at [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Silverlight]:Version on x86 Microsoft Windows systems, or [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Silverlight]:Version on x64 Microsoft Windows systems.
On Apple Mac OS, the version and build information of the currently installed version of Microsoft Silverlight can be found as follows:
- Open the Finder.
- Select the system drive and go to the folder Internet Plug-ins - Library.
- Right-click the file Silverlight.Plugin (if your mouse has only one button, press the Ctrl key while clicking on the file) to bring up the context menu, then click Show Package Contents.
- Inside the contents folder, locate the file info.plist and open it with an editor. It will contain an entry like this, which shows you the version number: SilverlightVersion 5.1.50709.0
The version installed with this security update for Microsoft Silverlight 5 is 5.1.50709.0. If your Microsoft Silverlight 5 version number is higher than or equal to this version number, your system is not vulnerable.
How do I upgrade my version of Microsoft Silverlight?
The Microsoft Silverlight auto-update feature helps make sure that your Microsoft Silverlight installation is kept up to date with the latest version of Microsoft Silverlight, Microsoft Silverlight functionality, and security features. For more information about the Microsoft Silverlight auto-update feature, see the Microsoft Silverlight Updater. Windows users who have disabled the Microsoft Silverlight auto-update feature can enroll in Microsoft Update to obtain the latest version of Microsoft Silverlight, or can download the latest version of Microsoft Silverlight manually using the download link in the Affected Software table in the earlier section, Affected Software. For information about deploying Microsoft Silverlight in an enterprise environment, see the Silverlight Enterprise Deployment Guide.
Will this update upgrade my version of Silverlight?
The 3182373 update upgrades previous versions of Silverlight to Silverlight version 5.1.50709.0. Microsoft recommends upgrading to be protected against the vulnerability described in this bulletin.
Where can I find additional information about the Silverlight product lifecycle? For lifecycle information specific to Silverlight, see the Microsoft Silverlight Support Lifecycle Policy.
Microsoft Silverlight Memory Corruption Vulnerability - CVE-2016-3367
A remote code execution vulnerability exists when Microsoft Silverlight improperly allows applications to access objects in memory. The vulnerability could corrupt system memory, which could allow an attacker to execute arbitrary code. In a web-browsing scenario, an attacker who successfully exploited this vulnerability could obtain the same permissions as the currently logged-on user. If a user is logged on with administrative user rights, an attacker could take complete control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.
To exploit the vulnerability, an attacker could host a website that contains a specially crafted Silverlight application and then convince a user to visit the compromised website. The attacker could also take advantage of websites containing specially crafted content, including those that accept or host user-provided content or advertisements. For example, an attacker could display specially crafted web content by using banner advertisements or by using other methods to deliver web content to affected systems. However, in all cases an attacker would have no way to force a user to visit a compromised website. Instead, an attacker would have to convince a user to visit the website, typically by enticing the user to click a link in either an email or instant message. The update addresses the vulnerability by correcting how Microsoft Silverlight allocates memory for inserting and appending strings in StringBuilder.
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|
|Microsoft Silverlight Memory Corruption Vulnerability||CVE-2016-3367||No||No|
Microsoft has not identified any mitigating factors for this vulnerability.
Microsoft has not identified any workarounds for this vulnerability.
Security Update Deployment
For Security Update Deployment information, see the Microsoft Knowledge Base article referenced 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 (September 13, 2016): Bulletin published.
Page generated 2016-09-12 09:56-07:00.