• 37 minutes to read

Security Bulletin

Microsoft Security Bulletin MS11-004 - Important

Vulnerability in Internet Information Services (IIS) FTP Service Could Allow Remote Code Execution (2489256)

Published: February 08, 2011 | Updated: March 08, 2011

Version: 2.0

General Information

Executive Summary

This security update resolves a publicly disclosed vulnerability in Microsoft Internet Information Services (IIS) FTP Service. The vulnerability could allow remote code execution if an FTP server receives a specially crafted FTP command. FTP Service is not installed by default on IIS.

This security update is rated Important for Microsoft FTP Service 7.0 for IIS 7.0 and Microsoft FTP Service 7.5 for IIS 7.0 when installed on all supported editions of Windows Vista and Windows Server 2008, and for Microsoft FTP Service 7.5 for Internet Information Services 7.5 on all supported editions of Windows 7 and 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 modifying the way that the IIS FTP Service handles specially crafted FTP commands. 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. Microsoft Knowledge Base Article 2489256 documents the currently known issues that customers may experience when installing this security update. The article also documents recommended solutions for these issues.

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 Vista Service Pack 1 and Windows Vista Service Pack 2 Microsoft FTP Service 7.0 for IIS 7.0[1]

Microsoft FTP Service 7.5 for IIS 7.0[1]		 Remote Code Execution Important None
Windows Vista x64 Edition Service Pack 1 and Windows Vista x64 Edition Service Pack 2 Microsoft FTP Service 7.0 for IIS 7.0[1]

Microsoft FTP Service 7.5 for IIS 7.0[1]		 Remote Code Execution Important None
Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2 Microsoft FTP Service 7.0 for IIS 7.0[1]*

Microsoft FTP Service 7.5 for IIS 7.0[1]*		 Remote Code Execution Important None
Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2 Microsoft FTP Service 7.0 for IIS 7.0[1]*

Microsoft FTP Service 7.5 for IIS 7.0[1]*		 Remote Code Execution Important None
Windows 7 for 32-bit Systems and Windows 7 for 32-bit Systems Service Pack 1 Microsoft FTP Service 7.5 for IIS 7.5 Remote Code Execution Important None
Windows 7 for x64-based Systems and Windows 7 for x64-based Systems Service Pack 1 Microsoft FTP Service 7.5 for IIS 7.5 Remote Code Execution Important None
Windows Server 2008 R2 for x64-based Systems and Windows Server 2008 R2 for x64-based Systems Service Pack 1 Microsoft FTP Service 7.5 for IIS 7.5* Remote Code Execution Important None
Windows Server 2008 R2 for Itanium-based Systems and Windows Server 2008 R2 for Itanium-based Systems Service Pack 1 Microsoft FTP Service 7.5 for IIS 7.5 Remote Code Execution Important None
[1]Not the default FTP Service for this operating system **\*Server Core installation affected.** This update applies, with the same severity rating, to supported editions of Windows Server 2008 or Windows Server 2008 R2 as indicated, whether or not installed using the Server Core installation option. For more information on this installation option, see the TechNet articles, [Managing a Server Core Installation](http://technet.microsoft.com/en-us/library/ee441255(ws.10).aspx) and [Servicing a Server Core Installation](http://technet.microsoft.com/en-us/library/ff698994(ws.10).aspx). 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](http://www.microsoft.com/windowsserver2008/en/us/compare-core-installation.aspx). **Non-Affected Software**

Operating System Component
Windows XP Service Pack 3 Microsoft FTP Service 5.1 for IIS 5.1
Windows XP Professional x64 Edition Service Pack 2 Microsoft FTP Service 5.1 for IIS 6.0
Windows Server 2003 Service Pack 2 Microsoft FTP Service 6.0 for IIS 6.0
Windows Server 2003 x64 Edition Service Pack 2 Microsoft FTP Service 6.0 for IIS 6.0
Windows Server 2003 with SP2 for Itanium-based Systems Microsoft FTP Service 6.0 for IIS 6.0
Windows Vista Service Pack 1 and Windows Vista Service Pack 2 Microsoft FTP Service 6.0 for IIS 7.0[1]
Microsoft FTP Service 6.0 for IIS 7.5[1]
Windows Vista x64 Edition Service Pack 1 and Windows Vista x64 Edition Service Pack 2 Microsoft FTP Service 6.0 for IIS 7.0[1]
Microsoft FTP Service 6.0 for IIS 7.5[1]
Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2 Microsoft FTP Service 6.0 for IIS 7.0[1]
Microsoft FTP Service 6.0 for IIS 7.5[1]
Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2 Microsoft FTP Service 6.0 for IIS 7.0[1]
Microsoft FTP Service 6.0 for IIS 7.5[1]
Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2 Microsoft FTP Service 6.0 for IIS 7.0[1]
Microsoft FTP Service 6.0 for IIS 7.5[1]

[1]The default FTP Service for this operating system

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.

I have IIS installed but have not enabled FTP. Do I need to apply this update?
This vulnerability only affects systems on which the listed versions of FTP Service is enabled. If an affected version of FTP Service is installed but not enabled, the update will still be offered through automatic updating.

How can I verify which version of the FTP Service is installed on my system?
On Windows Vista and Windows Server 2008, if ftpsvc.dll exists in the %SystemRoot%\system32\inetsrv directory, then the system contains a version of FTP Service affected by this vulnerability (Microsoft FTP Service 7.0 or Microsoft FTP Service 7.5). If the system contains ftpsvc2.dll in this directory, that indicates the presence of Microsoft FTP Service 6.0 on the system, which is not affected by this vulnerability.

Is my system affected by this vulnerability if the FTP Service is set up to disable anonymous authentication?
Yes. This vulnerability occurs before authentication, so a malicious client can compromise a vulnerable system even if it is configured to not allow anonymous authentication.

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.

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 IIS FTP Service Heap Buffer Overrun Vulnerability - CVE-2010-3972 Aggregate Severity Rating
Microsoft FTP Service 7.0 for IIS 7.0 when installed on Windows Vista Service Pack 1 and Windows Vista Service Pack 2 Important 
Remote Code Execution		 Important
Microsoft FTP Service 7.5 for IIS 7.0 when installed on Windows Vista Service Pack 1 and Windows Vista Service Pack 2 Important 
Remote Code Execution		 Important
Microsoft FTP Service 7.0 for IIS 7.0 when installed on Windows Vista x64 Edition Service Pack 1 and Windows Vista x64 Edition Service Pack 2 Important 
Remote Code Execution		 Important
Microsoft FTP Service 7.5 for IIS 7.0 when installed on Windows Vista x64 Edition Service Pack 1 and Windows Vista x64 Edition Service Pack 2 Important 
Remote Code Execution		 Important
Microsoft FTP Service 7.0 for IIS 7.0 when installed on Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2* Important 
Remote Code Execution		 Important
Microsoft FTP Service 7.5 for IIS 7.0 when installed on Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2* Important 
Remote Code Execution		 Important
Microsoft FTP Service 7.0 for IIS 7.0 when installed on Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2* Important 
Remote Code Execution		 Important
Microsoft FTP Service 7.5 for IIS 7.0 when installed on Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2* Important 
Remote Code Execution		 Important
Internet Information Services 7.5 on Windows 7 for 32-bit Systems and Windows 7 for 32-bit Systems Service Pack 1 Important 
Remote Code Execution		 Important
Internet Information Services 7.5 on Windows 7 for x64-based Systems and Windows 7 for x64-based Systems Service Pack 1 Important 
Remote Code Execution		 Important
Internet Information Services 7.5 on Windows Server 2008 R2 for x64-based Systems and Windows Server 2008 R2 for x64-based Systems Service Pack 1* Important 
Remote Code Execution		 Important
Internet Information Services 7.5 on Windows Server 2008 R2 for Itanium-based Systems and Windows Server 2008 R2 for Itanium-based Systems Service Pack 1 Important 
Remote Code Execution		 Important
**\*Server Core installation affected.** This update applies, with the same severity rating, to supported editions of Windows Server 2008 or Windows Server 2008 R2 as indicated, whether or not installed using the Server Core installation option. For more information on this installation option, see the TechNet articles, [Managing a Server Core Installation](http://technet.microsoft.com/en-us/library/ee441255(ws.10).aspx) and [Servicing a Server Core Installation](http://technet.microsoft.com/en-us/library/ff698994(ws.10).aspx). 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](http://www.microsoft.com/windowsserver2008/en/us/compare-core-installation.aspx). IIS FTP Service Heap Buffer Overrun Vulnerability - CVE-2010-3972 ----------------------------------------------------------------- A vulnerability exists in the FTP Service in Microsoft Internet Information Services (IIS) 7.0 and Microsoft Internet Information Services (IIS) 7.5. The vulnerability could allow remote code execution. To view this vulnerability as a standard entry in the Common Vulnerabilities and Exposures list, see [CVE-2010-3972](http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2010-3972). #### Mitigating Factors for IIS FTP Service Heap Buffer Overrun Vulnerability - CVE-2010-3972 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: - FTP Service is not installed by default on Internet Information Services (IIS). - FTP Service is not automatically started after installation. - No FTP Site is automatically created even when FTP service is installed and started. #### Workarounds for IIS FTP Service Heap Buffer Overrun Vulnerability - CVE-2010-3972 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: - **Stop and disable the FTP Service** Run the following command from a command prompt as an administrator: ``` sc stop ftpsvc sc config ftpsvc start= disabled ``` **Impact of workaround.** Clients will not be able to connect to the FTP server and upload or download files using the FTP Service. **How to undo the workaround.** Run the following command from a command prompt as an administrator: ``` sc config ftpsvc start= auto sc start ftpsvc ``` - **Block FTP inbound traffic at the edge firewall** Block the following port at the firewall: TCP Port 21 This port is used to initiate a connection with the affected component. Blocking this port at the edge firewall will help protect systems that are behind that firewall from attempts to exploit this vulnerability. Microsoft recommends that you block all unsolicited inbound communication from the Internet to help prevent attacks that may use other ports. For more information about ports, see the TechNet article, [TCP and UDP Port Assignments](http://go.microsoft.com/fwlink/?linkid=21312). **Impact of Workaround.** Applications and services may use the affected port. Blocking connectivity to the port may cause various applications or services to not function. **How to undo the workaround.** Unblock TCP port 21 at the firewall. For more information about ports, see the TechNet article, [TCP and UDP Port Assignments](http://go.microsoft.com/fwlink/?linkid=21312). #### FAQ for IIS FTP Service Heap Buffer Overrun Vulnerability - CVE-2010-3972 **What is the scope of the vulnerability?**  This is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts in the context of the local system. **What causes the vulnerability?**  This vulnerability is caused by the way that the Microsoft IIS FTP service handles specially crafted FTP commands. **What might an attacker use the vulnerability to do?**  An attacker who successfully exploited this vulnerability could cause remote code execution on the target system in the context of the running local system. **How could an attacker exploit the vulnerability?**  An attacker could exploit this vulnerability by sending a specially crafted FTP command to the FTP server. **What systems are primarily at risk from the vulnerability?**  Systems where Microsoft IIS 7.0 and 7.5 and FTP services are used are primarily at risk. **What does the update do?**  This update modifies the way that the Microsoft IIS FTP service handles specially crafted FTP commands. **When this security bulletin was issued, had this vulnerability been publicly disclosed?**  Yes. This vulnerability has been publicly disclosed. It has been assigned Common Vulnerability and Exposure number [CVE-2010-3972](http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2010-3972). **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. ### 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](http://go.microsoft.com/fwlink/?linkid=69903). The [Microsoft TechNet Security Web site](http://go.microsoft.com/fwlink/?linkid=21132) provides additional information about security in Microsoft products. Security updates are available from [Microsoft Update](http://go.microsoft.com/fwlink/?linkid=40747) and [Windows Update](http://update.microsoft.com). Security updates are also available from the [Microsoft Download Center](http://go.microsoft.com/fwlink/?linkid=21129). 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](http://go.microsoft.com/fwlink/?linkid=96155). 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](http://go.microsoft.com/fwlink/?linkid=97900). **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](http://support.microsoft.com/kb/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](http://www.microsoft.com/technet/security/tools/mbsahome.mspx). The following table provides the MBSA detection summary for this security update. | Software | MBSA | |----------------------------------------------------------------------------------------------------------------------|------| | Windows Vista Service Pack 1 and Windows Vista Service Pack 2 | Yes | | Windows Vista x64 Edition Service Pack 1 and Windows Vista x64 Edition Service Pack 2 | Yes | | Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2 | Yes | | Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2 | Yes | | Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2 | Yes | | 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](http://www.microsoft.com/technet/security/tools/mbsahome.mspx) 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](http://technet.microsoft.com/en-us/wsus/default.aspx). **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 Vista Service Pack 1 and Windows Vista Service Pack 2 | No | No | Yes | Yes | | Windows Vista x64 Edition Service Pack 1 and Windows Vista x64 Edition Service Pack 2 | No | No | Yes | Yes | | Windows Server 2008 for 32-bit Systems and Windows Server 2008 for 32-bit Systems Service Pack 2 | No | No | Yes | Yes | | Windows Server 2008 for x64-based Systems and Windows Server 2008 for x64-based Systems Service Pack 2 | No | No | Yes | Yes | | Windows Server 2008 for Itanium-based Systems and Windows Server 2008 for Itanium-based Systems Service Pack 2 | No | No | Yes | Yes | | 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](http://technet.microsoft.com/en-us/sms/bb676799.aspx). 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](http://update.microsoft.com/microsoftupdate) and that are supported by [Windows Server Update Services](http://go.microsoft.com/fwlink/?linkid=50120). For more information about the SMS 2003 ITMU, see [SMS 2003 Inventory Tool for Microsoft Updates](http://technet.microsoft.com/en-us/sms/bb676783.aspx). For more information about SMS scanning tools, see [SMS 2003 Software Update Scanning Tools](http://technet.microsoft.com/en-us/sms/bb676786.aspx). See also [Downloads for Systems Management Server 2003](http://technet.microsoft.com/en-us/sms/bb676766.aspx). 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](http://technet.microsoft.com/en-us/library/bb735860.aspx). For more information about SMS, visit the [SMS Web site](http://go.microsoft.com/fwlink/?linkid=21158). For more detailed information, see [Microsoft Knowledge Base Article 910723](http://support.microsoft.com/kb/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](http://technet2.microsoft.com/windowsvista/en/library/4279e239-37a4-44aa-aec5-4e70fe39f9de1033.mspx?mfr=true) components included with [Application Compatibility Toolkit](http://www.microsoft.com/downloads/details.aspx?familyid=24da89e9-b581-47b0-b45e-492dd6da2971&displaylang=en). 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. Security Update Deployment -------------------------- **Affected Software** For information about the specific security update for your affected software, click the appropriate link: #### Windows Vista (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 Microsoft FTP Service 7.0 for IIS 7.0 when installed on all supported 32-bit editions of Windows Vista:
ftp70_x86_kb2489256.msp /q
For Microsoft FTP Service 7.5 for IIS 7.0 when installed on all supported 32-bit editions of Windows Vista:
ftp75_x86_kb2489256.msp /q
For Microsoft FTP Service 7.0 for IIS 7.0 when installed on all supported x64-based editions of Windows Vista:
ftp70_x64_kb2489256.msp /q
For Microsoft FTP Service 7.5 for IIS 7.0 when installed on all supported x64-based editions of Windows Vista:
ftp75_x64_kb2489256.msp /q
Installing without restarting For Microsoft FTP Service 7.0 for IIS 7.0 when installed on all supported 32-bit editions of Windows Vista:
ftp70_x86_kb2489256.msp /norestart
For Microsoft FTP Service 7.5 for IIS 7.0 when installed on all supported 32-bit editions of Windows Vista:
ftp75_x86_kb2489256.msp /norestart
For Microsoft FTP Service 7.0 for IIS 7.0 when installed on all supported x64-based editions of Windows Vista:
ftp70_x64_kb2489256.msp /norestart
For Microsoft FTP Service 7.5 for IIS 7.0 when installed on all supported x64-based editions of Windows Vista:
ftp75_x64_kb2489256.msp /norestart
Further information See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required? This update does not require a restart. The installer stops the required services, applies the update, and then restarts the services. However, if the required services cannot be stopped for any reason, or if required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.
HotPatching Not applicable.
Removal Information WUSA.exe does not support uninstall of updates. To uninstall an update installed by WUSA, click Control Panel, and then click Security. Under Windows Update, click View installed updates and select from the list of updates.
File Information See Microsoft Knowledge Base Article 2489256
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](http://support.microsoft.com/kb/824684). This security update supports the following setup switches.

Supported Security Update Installation Switches
Switch Description
**/help** Displays usage dialog box.
Setup Modes
**/q** Sets user interface level.
Install Options
**/extract \[directory\]** Extract the package to the specified directory.
Restart Options
**/norestart** Does not restart when installation has completed.
**/forcerestart** Always restarts the computer after installation.
**/promptrestart** Prompts the user to restart if necessary.
Logging Options
**/l\[i|w|e|a|r|u|c|m|o|p|v|x| + |!|\*\] <LogFile>** Sets logging options.
i – status messages
w – non-fatal warnings
e – all error messages
a – startup of actions
r – action-specific records
u – user request
c – initial UI parameters
m – out-of-memory or fatal exit information
o – out-of-disk-space messages
p – terminal properties
v – verbose output
x – extra debugging information
+ – append to existing log file
! – flush each line to the log
\* – log all information, except for v and x options
**/log <LogFile>** Equivalent of /l\* <LogFile>
**Note** You can combine these switches into one command. For backward compatibility, the security update also supports many of the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see [Microsoft Knowledge Base Article 262841](http://support.microsoft.com/kb/262841).

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.

Windows Server 2008 (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 Microsoft FTP Service 7.0 for IIS 7.0 when installed on all supported 32-bit editions of Windows Server 2008:
ftp70_x86_kb2489256.msp /q
For Microsoft FTP Service 7.5 for IIS 7.0 when installed on all supported 32-bit editions of Windows Server 2008:
ftp75_x86_kb2489256.msp /q
For Microsoft FTP Service 7.0 for IIS 7.0 when installed on all supported x64-based editions of Windows Server 2008:
ftp70_x64_kb2489256.msp /q
For Microsoft FTP Service 7.5 for IIS 7.0 when installed on all supported x64-based editions of Windows Server 2008:
ftp75_x64_kb2489256.msp /q
Installing without restarting For Microsoft FTP Service 7.0 for IIS 7.0 when installed on all supported 32-bit editions of Windows Server 2008:
ftp70_x86_kb2489256.msp /norestart
For Microsoft FTP Service 7.5 for IIS 7.0 when installed on all supported 32-bit editions of Windows Server 2008:
ftp75_x86_kb2489256.msp /norestart
For Microsoft FTP Service 7.0 for IIS 7.0 when installed on all supported x64-based editions of Windows Server 2008:
ftp70_x64_kb2489256.msp /norestart
For Microsoft FTP Service 7.5 for IIS 7.0 when installed on all supported x64-based editions of Windows Server 2008:
ftp75_x64_kb2489256.msp /norestart
Further information See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required? This update does not require a restart. The installer stops the required services, applies the update, and then restarts the services. However, if the required services cannot be stopped for any reason, or if required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.
HotPatching Not applicable.
Removal Information WUSA.exe does not support uninstall of updates. To uninstall an update installed by WUSA, click Control Panel, and then click Security. Under Windows Update, click View installed updates and select from the list of updates.
File Information See Microsoft Knowledge Base Article 2489256
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](http://support.microsoft.com/kb/824684). This security update supports the following setup switches.

Supported Security Update Installation Switches
Switch Description
**/help** Displays usage dialog box.
Setup Modes
**/q** Sets user interface level.
Install Options
**/extract \[directory\]** Extract the package to the specified directory.
Restart Options
**/norestart** Does not restart when installation has completed.
**/forcerestart** Always restarts the computer after installation.
**/promptrestart** Prompts the user to restart if necessary.
Logging Options
**/l\[i|w|e|a|r|u|c|m|o|p|v|x| + |!|\*\] <LogFile>** Sets logging options.
i – status messages
w – non-fatal warnings
e – all error messages
a – startup of actions
r – action-specific records
u – user request
c – initial UI parameters
m – out-of-memory or fatal exit information
o – out-of-disk-space messages
p – terminal properties
v – verbose output
x – extra debugging information
+ – append to existing log file
! – flush each line to the log
\* – log all information, except for v and x options
**/log <LogFile>** Equivalent of /l\* <LogFile>
**Note** You can combine these switches into one command. For backward compatibility, the security update also supports many of the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see [Microsoft Knowledge Base Article 262841](http://support.microsoft.com/kb/262841).

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.

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 all supported 32-bit editions of Windows 7:
Windows6.1-KB2489256-x86.msu /quiet
For all supported x64-based editions of Windows 7:
Windows6.1-KB2489256-x64.msu /quiet
Installing without restarting For all supported 32-bit editions of Windows 7:
Windows6.1-KB2489256-x86.msu /quiet /norestart
For all supported x64-based editions of Windows 7:
Windows6.1-KB2489256-x64.msu /quiet /norestart
Further information See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required? This update does not require a restart. The installer stops the required services, applies the update, and then restarts the services. However, if the required services cannot be stopped for any reason, or if required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.
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 2489256
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](http://support.microsoft.com/kb/824684). This security update supports the following setup 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](http://technet.microsoft.com/en-us/library/dd871148(ws.10).aspx). **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. #### 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 all supported x64-based editions of Windows Server 2008 R2:
Windows6.1-KB2489256-x64.msu /quiet
For all supported Itanium-based editions of Windows Server 2008 R2:
Windows6.1-KB2489256-ia64.msu /quiet
Installing without restarting For all supported x64-based editions of Windows Server 2008 R2:
Windows6.1-KB2489256-x64.msu /quiet /norestart
For all supported Itanium-based editions of Windows Server 2008 R2:
Windows6.1-KB2489256-ia64.msu /quiet /norestart
Further information See the subsection, Detection and Deployment Tools and Guidance
Restart Requirement
Restart required? This update does not require a restart. The installer stops the required services, applies the update, and then restarts the services. However, if the required services cannot be stopped for any reason, or if required files are being used, this update will require a restart. If this behavior occurs, a message appears that advises you to restart.
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 2489256
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](http://support.microsoft.com/kb/824684). This security update supports the following setup 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](http://technet.microsoft.com/en-us/library/dd871148(ws.10).aspx). **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. ### Other Information #### 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](http://www.microsoft.com/security/msrc/mapp/partners.mspx). #### Support - Customers in the U.S. and Canada can receive technical support from [Security Support](http://go.microsoft.com/fwlink/?linkid=21131) 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](http://support.microsoft.com/). - 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](http://go.microsoft.com/fwlink/?linkid=21155). #### 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. #### 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. *Built at 2014-04-18T13:49:36Z-07:00*