Objavljena je revizija sigurnosnog upozorenja s oznakom MS11-009, prvotno objavljenog 9. veljače 2011. Otkriven je propust u JScript i VBScript komponenti Microsoft Windows operacijskih sustava. Do propusta dolazi zbog korupcije memorije u JScript i VBScript stroju prilikom obrade skripti na web stranicama. Kako bi iskoristio propust, udaljeni napadač mora navesti korisnika na otvaranje posebno oblikovane stranice sa zlonamjerno oblikovanim skriptama, nakon čega dolazi do otkrivanja osjetljivih informacija koje se mogu iskoristiti za daljnje napade. Revizija je izdana zbog izmjena popisa ranjivih sustava. Svim korisnicima se savjetuje korištenje dostupne zakrpe.
Microsoft Security Bulletin MS11-009 - Important
Vulnerability in JScript and VBScript Scripting Engines Could Allow Information Disclosure (2475792)
Published: February 08, 2011 | Updated: March 08, 2011
Version: 2.0
General Information
Executive Summary
This security update resolves a privately reported vulnerability in the JScript and VBScript scripting engines. The vulnerability could allow information disclosure if a user visited a specially crafted Web site. An attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to convince users to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes users to the attacker's Web site.
This security update is rated Important for all supported editions of Windows 7 and Moderate for all supported editions of Windows Server 2008 R2. For more information, see the subsection, Affected and Non-Affected Software, in this section.
The security update addresses the vulnerability by correcting the manner in which the JScript and VBScript scripting engines process scripts in Web pages. For more information about the vulnerability, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.
Recommendation. The majority of customers have automatic updating enabled and will not need to take any action because this security update will be downloaded and installed automatically. Customers who have not enabled automatic updating need to check for updates and install this update manually. For information about specific configuration options in automatic updating, see Microsoft Knowledge Base Article 294871.
For administrators and enterprise installations, or end users who want to install this security update manually, Microsoft recommends that customers apply the update at the earliest opportunity using update management software, or by checking for updates using the Microsoft Update service.
See also the section, Detection and Deployment Tools and Guidance, later in this bulletin.
Known Issues. None
Top of sectionTop of section
Affected and Non-Affected Software
The following software have been tested to determine which versions or editions are affected. Other versions or editions are either past their support life cycle or are not affected. To determine the support life cycle for your software version or edition, visit Microsoft Support Lifecycle.
Affected Software
Operating System Component Maximum Security Impact Aggregate Severity Rating Bulletins Replaced by this Update
Windows 7 for 32-bit Systems and Windows 7 for 32-bit Systems Service Pack 1
JScript 5.8
Information Disclosure
Important
None
Windows 7 for 32-bit Systems and Windows 7 for 32-bit Systems Service Pack 1
VBScript 5.8
Information Disclosure
Important
MS10-022
Windows 7 for x64-based Systems and Windows 7 for x64-based Systems Service Pack 1
JScript 5.8
Information Disclosure
Important
None
Windows 7 for x64-based Systems and Windows 7 for x64-based Systems Service Pack 1
VBScript 5.8
Information Disclosure
Important
MS10-022
Windows Server 2008 R2 for x64-based Systems and Windows Server 2008 R2 for x64-based Systems Service Pack 1
JScript 5.8**
Information Disclosure
Moderate
None
Windows Server 2008 R2 for x64-based Systems and Windows Server 2008 R2 for x64-based Systems Service Pack 1
VBScript 5.8**
Information Disclosure
Moderate
MS10-022
Windows Server 2008 R2 for Itanium-based Systems and Windows Server 2008 R2 for Itanium-based Systems Service Pack 1
JScript 5.8
Information Disclosure
Moderate
None
Windows Server 2008 R2 for Itanium-based Systems and Windows Server 2008 R2 for Itanium-based Systems Service Pack 1
VBScript 5.8
Information Disclosure
Moderate
MS10-022
**Server Core installation not affected. The vulnerabilities addressed by this update do not affect supported editions of Windows Server 2008 or Windows Server 2008 R2 as indicated, when installed using the Server Core installation option. For more information on this installation option, see the TechNet articles, Managing a Server Core Installation and Servicing a Server Core Installation. Note that the Server Core installation option does not apply to certain editions of Windows Server 2008 and Windows Server 2008 R2; see Compare Server Core Installation Options.
Non-Affected Software
Operating System Component
Windows XP Service Pack 3
JScript 5.7
JScript 5.8
VBScript 5.7
VBScript 5.8
Windows XP Professional x64 Edition Service Pack 2
JScript 5.6
JScript 5.7
JScript 5.8
VBScript 5.6
VBScript 5.7
VBScript 5.8
Windows Server 2003 Service Pack 2
JScript 5.6
JScript 5.7
JScript 5.8
VBScript 5.6
VBScript 5.7
VBScript 5.8
Windows Server 2003 x64 Edition Service Pack 2
JScript 5.6
JScript 5.7
JScript 5.8
VBScript 5.6
VBScript 5.7
VBScript 5.8
Windows Server 2003 with SP2 for Itanium-based Systems
JScript 5.6
JScript 5.7
VBScript 5.6
VBScript 5.7
Windows Vista Service Pack 1 and Windows Vista Service Pack 2
JScript 5.7
JScript 5.8
VBScript 5.7
VBScript 5.8
Windows Vista x64 Edition Service Pack 1 and Windows Vista x64 Edition Service Pack 2
JScript 5.7
JScript 5.8
VBScript 5.7
VBScript 5.8
Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2
JScript 5.7
JScript 5.8
VBScript 5.7
VBScript 5.8
Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2
JScript 5.7
JScript 5.8
VBScript 5.7
VBScript 5.8
Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2
JScript 5.7
VBScript 5.7
Top of sectionTop of section
Frequently Asked Questions (FAQ) Related to This Security Update
Why was this bulletin revised on March 8, 2011?
Microsoft clarified the Affected Software to include Windows 7 for 32-bit Systems Service Pack 1, Windows 7 for x64-based Systems Service Pack 1, Windows Server 2008 R2 for x64-based Systems Service Pack 1, and Windows Server 2008 R2 for Itanium-based Systems Service Pack 1.
Customers of the original release version of Windows 7 for 32-bit Systems, Windows 7 for x64-based Systems, Windows Server 2008 R2 for x64-based Systems, and Windows Server 2008 R2 for Itanium-based Systems, who have already applied this security update do not need to take any action. Customers who have updated these operating systems with the corresponding Service Pack 1 need to apply this security update.
Where are the file information details?
Refer to the reference tables in the Security Update Deployment section for the location of the file information details.
I am using an older release of the software discussed in this security bulletin. What should I do?
The affected software listed in this bulletin have been tested to determine which releases are affected. Other releases are past their support life cycle. For more information about the product lifecycle, visit the Microsoft Support Lifecycle Web site.
It should be a priority for customers who have older releases of the software to migrate to supported releases to prevent potential exposure to vulnerabilities. To determine the support lifecycle for your software release, see Select a Product for Lifecycle Information. For more information about service packs for these software releases, see Lifecycle Supported Service Packs.
Customers who require custom support for older software must contact their Microsoft account team representative, their Technical Account Manager, or the appropriate Microsoft partner representative for custom support options. Customers without an Alliance, Premier, or Authorized Contract can contact their local Microsoft sales office. For contact information, visit the Microsoft Worldwide Information Web site, select the country in the Contact Information list, and then click Go to see a list of telephone numbers. When you call, ask to speak with the local Premier Support sales manager. For more information, see the Microsoft Support Lifecycle Policy FAQ.
Top of sectionTop of section
Vulnerability Information
Severity Ratings and Vulnerability Identifiers
The following severity ratings 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 February bulletin summary. For more information, see Microsoft Exploitability Index.
Vulnerability Severity Rating and Maximum Security Impact by Affected Software
Affected Software Scripting Engines Information Disclosure Vulnerability - CVE-2011-0031 Aggregate Severity Rating
JScript 5.8 and VBScript 5.8 on Windows 7 for 32-bit Systems and Windows 7 for 32-bit Systems Service Pack 1
Important
Information Disclosure
Important
JScript 5.8 and VBScript 5.8 on Windows 7 for x64-based Systems and Windows 7 for x64-based Systems Service Pack 1
Important
Information Disclosure
Important
JScript 5.8 and VBScript 5.8 on Windows Server 2008 R2 for x64-based Systems and Windows Server 2008 R2 for x64-based Systems Service Pack 1**
Moderate
Information Disclosure
Moderate
JScript 5.8 and VBScript 5.8 on Windows Server 2008 R2 for Itanium-based Systems and Windows Server 2008 R2 for Itanium-based Systems Service Pack 1
Moderate
Information Disclosure
Moderate
**Server Core installation not affected. The vulnerabilities addressed by this update do not affect supported editions of Windows Server 2008 or Windows Server 2008 R2 as indicated, when installed using the Server Core installation option. For more information on this installation option, see the TechNet articles, Managing a Server Core Installation and Servicing a Server Core Installation. Note that the Server Core installation option does not apply to certain editions of Windows Server 2008 and Windows Server 2008 R2; see Compare Server Core Installation Options.
Top of sectionTop of section
Scripting Engines Information Disclosure Vulnerability - CVE-2011-0031
An information disclosure vulnerability exists in the JScript and VBScript scripting engines due to a memory corruption error. An attacker who successfully exploited this vulnerability could read data not intended to be disclosed. Note that this vulnerability would not allow an attacker to execute code or to elevate their user rights directly, but it could be used to obtain information that could be used to try to further compromise the affected system.
To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see CVE-2011-0031.
Mitigating Factors for Scripting Engines Information Disclosure Vulnerability - CVE-2011-0031
Mitigation refers to a setting, common configuration, or general best-practice, existing in a default state, that could reduce the severity of exploitation of a vulnerability. The following mitigating factors may be helpful in your situation:
•
In a Web-based attack scenario, an attacker could host a Web site that contains a Web page that is used to exploit this vulnerability. In addition, compromised Web sites and Web sites that accept or host user-provided content or advertisements could contain specially crafted content that could exploit this vulnerability. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to convince users to visit the Web site, typically by getting them to click a link in an e-mail message or Instant Messenger message that takes users to the attacker’s Web site.
•
By default, all supported versions of Microsoft Outlook, Microsoft Outlook Express, and Windows Mail open HTML e-mail messages in the Restricted sites zone, which disables script and ActiveX controls, removing the risk of an attacker being able to use this vulnerability to execute malicious code. If a user clicks a link in an e-mail message, the user could still be vulnerable to exploitation of this vulnerability through the Web-based attack scenario.
•
By default, Internet Explorer on Windows Server 2008 and Windows Server 2008 R2 runs in a restricted mode that is known as Enhanced Security Configuration. This mode mitigates this vulnerability. See the FAQ section of this security update for more information about Internet Explorer Enhanced Security Configuration.
Top of sectionTop of section
Workarounds for Scripting Engines Information Disclosure Vulnerability - CVE-2011-0031
Workaround refers to a setting or configuration change that does not correct the underlying vulnerability but would help block known attack vectors before you apply the update. Microsoft has tested the following workarounds and states in the discussion whether a workaround reduces functionality:
•
Set Internet and Local intranet security zone settings to "High" to block ActiveX Controls and Active Scripting in these zones
You can help protect against exploitation of this vulnerability by changing your settings for the Internet security zone to block ActiveX controls and Active Scripting. You can do this by setting your browser security to High.
To raise the browsing security level in Internet Explorer, follow these steps:
1.
On the Internet Explorer Tools menu, click Internet Options.
2.
In the Internet Options dialog box, click the Security tab, and then click the Internet icon.
3.
Under Security level for this zone, move the slider to High. This sets the security level for all Web sites you visit to High.
Note If no slider is visible, click Default Level, and then move the slider to High.
Note Setting the level to High may cause some Web sites to work incorrectly. If you have difficulty using a Web site after you change this setting, and you are sure the site is safe to use, you can add that site to your list of trusted sites. This will allow the site to work correctly even with the security setting set to High.
Impact of workaround. There are side effects to blocking ActiveX Controls and Active Scripting. Many Web sites that are on the Internet or on an intranet use ActiveX or Active Scripting to provide additional functionality. For example, an online e-commerce site or banking site may use ActiveX Controls to provide menus, ordering forms, or even account statements. Blocking ActiveX Controls or Active Scripting is a global setting that affects all Internet and intranet sites. If you do not want to block ActiveX Controls or Active Scripting for such sites, use the steps outlined in "Add sites that you trust to the Internet Explorer Trusted sites zone".
Add sites that you trust to the Internet Explorer Trusted sites zone
After you set Internet Explorer to block ActiveX controls and Active Scripting in the Internet zone and in the Local intranet zone, you can add sites that you trust to the Internet Explorer Trusted sites zone. This will allow you to continue to use trusted Web sites exactly as you do today, while helping to protect yourself from this attack on untrusted sites. We recommend that you add only sites that you trust to the Trusted sites zone.
To do this, follow these steps:
1.
In Internet Explorer, click Tools, click Internet Options, and then click the Security tab.
2.
In the Select a Web content zone to specify its current security settings box, click Trusted Sites, and then click Sites.
3.
If you want to add sites that do not require an encrypted channel, click to clear the Require server verification (https:) for all sites in this zone check box.
4.
In the Add this Web site to the zone box, type the URL of a site that you trust, and then click Add.
5.
Repeat these steps for each site that you want to add to the zone.
6.
Click OK two times to accept the changes and return to Internet Explorer.
Note Add any sites that you trust not to take malicious action on your system. Two in particular that you may want to add are *.windowsupdate.microsoft.com and *.update.microsoft.com. These are the sites that will host the update, and it requires an ActiveX Control to install the update.
•
Configure Internet Explorer to prompt before running Active Scripting or to disable Active Scripting in the Internet and Local intranet security zone
You can help protect against exploitation of this vulnerability by changing your settings to prompt before running Active Scripting or to disable Active Scripting in the Internet and Local intranet security zone. To do this, follow these steps:
1.
In Internet Explorer, click Internet Options on the Tools menu.
2.
Click the Security tab.
3.
Click Internet, and then click Custom Level.
4.
Under Settings, in the Scripting section, under Active Scripting, click Prompt or Disable, and then click OK.
5.
Click Local intranet, and then click Custom Level.
6.
Under Settings, in the Scripting section, under Active Scripting, click Prompt or Disable, and then click OK.
7.
Click OK two times to return to Internet Explorer.
Note Disabling Active Scripting in the Internet and Local intranet security zones may cause some Web sites to work incorrectly. If you have difficulty using a Web site after you change this setting, and you are sure the site is safe to use, you can add that site to your list of trusted sites. This will allow the site to work correctly.
Impact of workaround. There are side effects to prompting before running Active Scripting. Many Web sites that are on the Internet or on an intranet use Active Scripting to provide additional functionality. For example, an online e-commerce site or banking site may use Active Scripting to provide menus, ordering forms, or even account statements. Prompting before running Active Scripting is a global setting that affects all Internet and intranet sites. You will be prompted frequently when you enable this workaround. For each prompt, if you feel you trust the site that you are visiting, click Yes to run Active Scripting. If you do not want to be prompted for all these sites, use the steps outlined in "Add sites that you trust to the Internet Explorer Trusted sites zone".
Add sites that you trust to the Internet Explorer Trusted sites zone
After you set Internet Explorer to require a prompt before it runs ActiveX controls and Active Scripting in the Internet zone and in the Local intranet zone, you can add sites that you trust to the Internet Explorer Trusted sites zone. This will allow you to continue to use trusted Web sites exactly as you do today, while helping to protect you from this attack on untrusted sites. We recommend that you add only sites that you trust to the Trusted sites zone.
To do this, follow these steps:
1.
In Internet Explorer, click Tools, click Internet Options, and then click the Security tab.
2.
In the Select a Web content zone to specify its current security settings box, click Trusted Sites, and then click Sites.
3.
If you want to add sites that do not require an encrypted channel, click to clear the Require server verification (https:) for all sites in this zone check box.
4.
In the Add this Web site to the zone box, type the URL of a site that you trust, and then click Add.
5.
Repeat these steps for each site that you want to add to the zone.
6.
Click OK two times to accept the changes and return to Internet Explorer.
Note Add any sites that you trust not to take malicious action on your system. Two in particular that you may want to add are *.windowsupdate.microsoft.com and *.update.microsoft.com. These are the sites that will host the update, and it requires an ActiveX Control to install the update.
Top of sectionTop of section
FAQ for Scripting Engines Information Disclosure Vulnerability - CVE-2011-0031
What is the scope of the vulnerability?
This is an information disclosure vulnerability. An attacker who successfully exploited this vulnerability would be able to read data which was not intended to be disclosed. Note that this vulnerability would not allow an attacker to execute code or to elevate their user rights directly, but it could be used to obtain information that could be used to try to further compromise the affected system.
What causes the vulnerability?
The vulnerability is caused by the way that the JScript and VBScript scripting engines process scripts in Web pages. When the scripting engine attempts to load the decoded script into memory in order to run it, memory corruption can occur. The consequences of the disclosure of that information depend on the nature of the information itself.
What is JScript?
JScript is an interpreted, object-based scripting language that is often used to make Web sites more flexible or interactive. JScript scripts can run only in the presence of an interpreter or host, such as Active Server Pages (ASP), Internet Explorer, or Windows Script Host. More specifically, JScript is the Microsoft implementation of the ECMA 262 language specification (ECMAScript Edition 3). For more information, see the MSDN Article, JScript Fundamentals, or visit the Web site, ECMA International.
What is VBScript?
VBScript (Visual Basic Script) is an interpreted, object-based scripting language that is often used to make Web sites more flexible or interactive. VBScript scripts can run only in the presence of an interpreter or host, such as Active Server Pages (ASP), Internet Explorer, or Windows Script Host. For more information, see the MSDN article, VBScript Fundamentals.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability would be able to read data which was not intended to be disclosed.
How could an attacker exploit the vulnerability?
An attacker could host a specially crafted Web site that is designed to exploit this vulnerability and then convince a user to visit the Web site. This could also include compromised Web sites and Web sites that accept or host user-provided content or advertisements. These Web sites could contain specially crafted content that could exploit these vulnerabilities. In all cases, however, an attacker would have no way to force users to visit these Web sites. Instead, an attacker would have to convince users to visit the Web site, typically by getting them to click a link in an e-mail message or in an Instant Messenger message that takes users to the attacker's Web site. It could also be possible to display specially crafted Web content by using banner advertisements or by using other methods to deliver Web content to affected systems.
What systems are primarily at risk from the vulnerability?
Client, workstation, or terminal server systems where Internet Explorer is used to browse Web pages are primarily at risk.
I am running Internet Explorer for Windows Server 2008, or Windows Server 2008 R2. Does this mitigate this vulnerability?
Yes. By default, Internet Explorer on Windows Server 2008 and Windows Server 2008 R2 runs in a restricted mode that is known as Enhanced Security Configuration. Enhanced Security Configuration is a group of preconfigured settings in Internet Explorer that can reduce the likelihood of a user or administrator downloading and running specially crafted Web content on a server. This is a mitigating factor for Web sites that you have not added to the Internet Explorer Trusted sites zone.
What does the update do?
This security update addresses the vulnerability by correcting the manner in which the JScript and VBScript scripting engines process scripts in Web pages.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through coordinated vulnerability disclosure.
When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers when this security bulletin was originally issued.
Top of sectionTop of section
Top of sectionTop of section
Update Information
Detection and Deployment Tools and Guidance
Security Central
Manage the software and security updates you need to deploy to the servers, desktop, and mobile systems in your organization. For more information see the TechNet Update Management Center. The Microsoft TechNet Security Web site provides additional information about security in Microsoft products.
Security updates are available from Microsoft Update and Windows Update. Security updates are also available from the Microsoft Download Center. You can find them most easily by doing a keyword search for "security update."
Finally, security updates can be downloaded from the Microsoft Update Catalog. The Microsoft Update Catalog provides a searchable catalog of content made available through Windows Update and Microsoft Update, including security updates, drivers and service packs. By searching using the security bulletin number (such as, "MS07-036"), you can add all of the applicable updates to your basket (including different languages for an update), and download to the folder of your choosing. For more information about the Microsoft Update Catalog, see the Microsoft Update Catalog FAQ.
Detection and Deployment Guidance
Microsoft provides detection and deployment guidance for security updates. This guidance contains recommendations and information that can help IT professionals understand how to use various tools for detection and deployment of security updates. For more information, see Microsoft Knowledge Base Article 961747.
Microsoft Baseline Security Analyzer
Microsoft Baseline Security Analyzer (MBSA) allows administrators to scan local and remote systems for missing security updates as well as common security misconfigurations. For more information about MBSA, visit Microsoft Baseline Security Analyzer.
The following table provides the MBSA detection summary for this security update.
Software MBSA
Windows 7 for 32-bit Systems and Windows 7 for 32-bit Systems Service Pack 1
Yes
Windows 7 for x64-based Systems and Windows 7 for x64-based Systems Service Pack 1
Yes
Windows Server 2008 R2 for x64-based Systems and Windows Server 2008 R2 for x64-based Systems Service Pack 1
Yes
Windows Server 2008 R2 for Itanium-based Systems and Windows Server 2008 R2 for Itanium-based Systems Service Pack 1
Yes
Note For customers using legacy software not supported by the latest release of MBSA, Microsoft Update, and Windows Server Update Services, please visit Microsoft Baseline Security Analyzer and reference the Legacy Product Support section on how to create comprehensive security update detection with legacy tools.
Windows Server Update Services
Windows Server Update Services (WSUS) enables information technology administrators to deploy the latest Microsoft product updates to computers that are running the Windows operating system. For more information about how to deploy security updates using Windows Server Update Services, see the TechNet article, Windows Server Update Services.
Systems Management Server
The following table provides the SMS detection and deployment summary for this security update.
Software SMS 2.0 SMS 2003 with SUIT SMS 2003 with ITMU Configuration Manager 2007
Windows 7 for 32-bit Systems and Windows 7 for 32-bit Systems Service Pack 1
No
No
Yes
Yes
Windows 7 for x64-based Systems and Windows 7 for x64-based Systems Service Pack 1
No
No
Yes
Yes
Windows Server 2008 R2 for x64-based Systems and Windows Server 2008 R2 for x64-based Systems Service Pack 1
No
No
Yes
Yes
Windows Server 2008 R2 for Itanium-based Systems and Windows Server 2008 R2 for Itanium-based Systems Service Pack 1
No
No
Yes
Yes
For SMS 2.0 and SMS 2003, the Security Update Inventory Tool (SUIT) can be used by SMS to detect security updates. See also Downloads for Systems Management Server 2.0.
For SMS 2003, the SMS 2003 Inventory Tool for Microsoft Updates (ITMU) can be used by SMS to detect security updates that are offered by Microsoft Update and that are supported by Windows Server Update Services. For more information about the SMS 2003 ITMU, see SMS 2003 Inventory Tool for Microsoft Updates. For more information about SMS scanning tools, see SMS 2003 Software Update Scanning Tools. See also Downloads for Systems Management Server 2003.
System Center Configuration Manager 2007 uses WSUS 3.0 for detection of updates. For more information about Configuration Manager 2007 Software Update Management, visit System Center Configuration Manager 2007.
For more information about SMS, visit the SMS Web site.
For more detailed information, see Microsoft Knowledge Base Article 910723: Summary list of monthly detection and deployment guidance articles.
Update Compatibility Evaluator and Application Compatibility Toolkit
Updates often write to the same files and registry settings required for your applications to run. This can trigger incompatibilities and increase the time it takes to deploy security updates. You can streamline testing and validating Windows updates against installed applications with the Update Compatibility Evaluator components included with Application Compatibility Toolkit.
The Application Compatibility Toolkit (ACT) contains the necessary tools and documentation to evaluate and mitigate application compatibility issues before deploying Microsoft Windows Vista, a Windows Update, a Microsoft Security Update, or a new version of Windows Internet Explorer in your environment.
Top of sectionTop of section
Security Update Deployment
Affected Software
For information about the specific security update for your affected software, click the appropriate link:
Windows 7 (all editions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
Inclusion in Future Service Packs
The update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user intervention
For JScript 5.8 and VBScript 5.8 on all supported 32-bit editions of Windows 7:
Windows6.1-KB2475792-x86.msu /quiet
For JScript 5.8 and VBScript 5.8 on all supported x64-based editions of Windows 7:
Windows6.1-KB2475792-x64.msu /quiet
Installing without restarting
For JScript 5.8 and VBScript 5.8 on all supported 32-bit editions of Windows 7:
Windows6.1-KB2475792-x86.msu /quiet /norestart
For JScript 5.8 and VBScript 5.8 on all supported x64-based editions of Windows 7:
Windows6.1-KB2475792-x64.msu /quiet /norestart
Further information
See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?
In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.
To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012.
HotPatching
Not applicable.
Removal Information
To uninstall an update installed by WUSA, use the /Uninstall setup switch or click Control Panel, click System and Security, and then under Windows Update, click View installed updates and select from the list of updates.
File Information
See Microsoft Knowledge Base Article 2475792
Registry Key Verification
Note A registry key does not exist to validate the presence of this update.
Deployment Information
Installing the Update
When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
This security update supports the following setup switches.
Supported Security Update Installation Switches
Switch Description
/?, /h, /help
Displays help on supported switches.
/quiet
Suppresses the display of status or error messages.
/norestart
When combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation.
/warnrestart:<seconds>
When combined with /quiet, the installer will warn the user before initiating restart.
/promptrestart
When combined with /quiet, the installer will prompt before initiating restart.
/forcerestart
When combined with /quiet, the installer will forcefully close applications and initiate restart.
/log:<file name>
Enables logging to specified file.
/extract:<destination>
Extracts the package contents to the destination folder.
/uninstall /kb:<KB Number>
Uninstalls the security update.
Note For more information about the wusa.exe installer, see "Windows Update Stand-alone Installer" in the TechNet article, Miscellaneous Changes in Windows 7.
Verifying That the Update Has Been Applied
•
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.
•
File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.
1.
Click Start and then enter an update file name in the Search box.
2.
When the file appears under Programs, right-click the file name and click Properties.
3.
On the General tab, compare the file size with the file information tables provided in the bulletin KB article.
Note Depending on the edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed.
4.
You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
5.
Finally, you can also click the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.
Top of sectionTop of section
Top of sectionTop of section
Windows Server 2008 R2 (all editions)
Reference Table
The following table contains the security update information for this software. You can find additional information in the subsection, Deployment Information, in this section.
Inclusion in Future Service Packs
The update for this issue will be included in a future service pack or update rollup
Deployment
Installing without user intervention
For JScript 5.8 and VBScript 5.8 on all supported x64-based editions of Windows Server 2008 R2:
Windows6.1-KB2475792-x64.msu /quiet
For JScript 5.8 and VBScript 5.8 on all supported Itanium-based editions of Windows Server 2008 R2:
Windows6.1-KB2475792-ia64.msu /quiet
Installing without restarting
For JScript 5.8 and VBScript 5.8 on all supported x64-based editions of Windows Server 2008 R2:
Windows6.1-KB2475792-x64.msu /quiet /norestart
For JScript 5.8 and VBScript 5.8 on all supported Itanium-based editions of Windows Server 2008 R2:
Windows6.1-KB2475792-ia64.msu /quiet /norestart
Further information
See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required?
In some cases, this update does not require a restart. If the required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.
To help reduce the chance that a restart will be required, stop all affected services and close all applications that may use the affected files prior to installing the security update. For more information about the reasons why you may be prompted to restart, see Microsoft Knowledge Base Article 887012.
HotPatching
Not applicable.
Removal Information
To uninstall an update installed by WUSA, use the /Uninstall setup switch or click Control Panel, click System and Security, and then under Windows Update, click View installed updates and select from the list of updates.
File Information
See Microsoft Knowledge Base Article 2475792
Registry Key Verification
Note A registry key does not exist to validate the presence of this update.
Deployment Information
Installing the Update
When you install this security update, the installer checks whether one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.
For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.
This security update supports the following setup switches.
Supported Security Update Installation Switches
Switch Description
/?, /h, /help
Displays help on supported switches.
/quiet
Suppresses the display of status or error messages.
/norestart
When combined with /quiet, the system will not be restarted after installation even if a restart is required to complete installation.
/warnrestart:<seconds>
When combined with /quiet, the installer will warn the user before initiating restart.
/promptrestart
When combined with /quiet, the installer will prompt before initiating restart.
/forcerestart
When combined with /quiet, the installer will forcefully close applications and initiate restart.
/log:<file name>
Enables logging to specified file.
/extract:<destination>
Extracts the package contents to the destination folder.
/uninstall /kb:<KB Number>
Uninstalls the security update.
Note For more information about the wusa.exe installer, see "Windows Update Stand-alone Installer" in the TechNet article, Miscellaneous Changes in Windows 7.
Verifying That the Update Has Been Applied
•
Microsoft Baseline Security Analyzer
To verify that a security update has been applied to an affected system, you may be able to use the Microsoft Baseline Security Analyzer (MBSA) tool. See the section, Detection and Deployment Tools and Guidance, earlier in this bulletin for more information.
•
File Version Verification
Because there are several editions of Microsoft Windows, the following steps may be different on your system. If they are, see your product documentation to complete these steps.
1.
Click Start and then enter an update file name in the Start Search box.
2.
When the file appears under Programs, right-click the file name and click Properties.
3.
On the General tab, compare the file size with the file information tables provided in the bulletin KB article.
Note Depending on the edition of the operating system, or the programs that are installed on your system, some of the files that are listed in the file information table may not be installed.
4.
You can also click the Details tab and compare information, such as file version and date modified, with the file information tables provided in the bulletin KB article.
Note Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.
5.
Finally, you can also click the Previous Versions tab and compare file information for the previous version of the file with the file information for the new, or updated, version of the file.
Top of sectionTop of section
Top of sectionTop of section
Top of sectionTop of section
Other Information
Acknowledgments
Microsoft thanks the following for working with us to help protect customers:
•
Yamata Li of Palo Alto Networks for reporting the Scripting Engines Information Disclosure Vulnerability (CVE-2011-0031)
Top of sectionTop of section
Microsoft Active Protections Program (MAPP)
To improve security protections for customers, Microsoft provides vulnerability information to major security software providers in advance of each monthly security update release. Security software providers can then use this vulnerability information to provide updated protections to customers via their security software or devices, such as antivirus, network-based intrusion detection systems, or host-based intrusion prevention systems. To determine whether active protections are available from security software providers, please visit the active protections Web sites provided by program partners, listed in Microsoft Active Protections Program (MAPP) Partners.
Top of sectionTop of section
Support
•
Customers in the U.S. and Canada can receive technical support from Security Support or 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates. For more information about available support options, see Microsoft Help and Support.
•
International customers can receive support from their local Microsoft subsidiaries. There is no charge for support that is associated with security updates. For more information about how to contact Microsoft for support issues, visit the International Support Web site.
Top of sectionTop of section
Disclaimer
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.
Top of sectionTop of section
Revisions
•
V1.0 (February 8, 2011): Bulletin published.
•
V2.0 (March 8, 2011): Clarified the Affected Software to include Windows 7 for 32-bit Systems Service Pack 1, Windows 7 for x64-based Systems Service Pack 1, Windows Server 2008 R2 for x64-based Systems Service Pack 1, and Windows Server 2008 R2 for Itanium-based Systems Service Pack 1. See the entry to the section, Frequently Asked Questions (FAQ) Related to This Security Update, that explains this revision.
Posljednje sigurnosne preporuke