-
Microsoft announced 7 security bulletins that address 31 vulnerabilities as part of the monthly security bulletin release on February 11th, 2014. A summary of these bulletins is on the Microsoft website at http://technet.microsoft.com/en-us/security/bulletin/ms14-feb. This document provides identification and mitigation techniques that administrators can deploy on Cisco network devices.
The vulnerabilities that have a client software attack vector can be exploited locally on the vulnerable device, require user interaction, can be exploited using web-based attacks (these include but are not limited to cross-site scripting, phishing, and web-based email threats), or can be exploited using email attachments and files stored on network shares are in the following list: The vulnerability that has a network mitigation is in the following list. Cisco devices provide several countermeasures for this vulnerability. This section of the document provides an overview of these techniques. Information about affected and unaffected products is available in the respective Microsoft advisories and the Cisco Alerts that are referenced in Cisco Event Response: Microsoft Security Bulletin Release for February 2014.
In addition, multiple Cisco products use Microsoft operating systems as their base operating system. Cisco products that may be affected by the vulnerabilities described in the referenced Microsoft advisories are detailed in the "Associated Products" table in the "Product Sets" section.
-
MS14-005, Vulnerability in Microsoft XML Core Services Could Allow Information Disclosure (2916036): This vulnerability has been assigned Common Vulnerabilities and Exposures (CVE) identifier CVE-2014-0266. This vulnerability can be exploited remotely without authentication and requires user interaction. Successful exploitation of this vulnerability may allow arbitrary code execution. The attack vector for exploitation of this vulnerability is through HTTP packets that typically use TCP port 80 but may also use TCP ports 3128, 8000, 8010, 8080, 8888, and 24326.
The Cisco ASA 5500 Series Adaptive Security Appliance, Cisco Catalyst 6500 Series ASA Services Module (ASASM), and Cisco Firewall Services Module (FWSM) for Cisco Catalyst 6500 Series Switches and Cisco 7600 Series Routers provide protection for potential attempts to exploit this vulnerability. For configuration and use information see the Preventing ActiveX Exploits with Cisco Firewall Application Layer Protocol Inspection Cisco Security white paper.
The Cisco ACE Application Control Engine Appliance and Module provides protection for potential attempts to exploit this vulnerability. For configuration and use information see the Preventing ActiveX Exploits with Cisco Application Control Engine Application Layer Protocol Inspection Cisco Security white paper.
Cross-site scripting and phishing could also be used to exploit this vulnerability. For additional information about cross-site scripting attacks and the methods used to exploit this vulnerability, refer to the Cisco Applied Mitigation Bulletin Understanding Cross-Site Scripting (XSS) Threat Vectors.
-
&nsbp;
-
The vulnerabilities that can be exploited locally on the vulnerable device, or require user interaction, or can be exploited using web-based attacks (these include, but are not limited to, XSS, phishing, and web-based email threats) or email attachments, are in the following list: These vulnerabilities are most successfully mitigated at the endpoint through software updates, user education, desktop administration best practices, and endpoint protection software such as Cisco Security Agent Host Intrusion Prevention System (HIPS) or antivirus products.
The vulnerability that has a network mitigation is found in the following list: Cisco devices provide several countermeasures for this vulnerability. This section of the document provides an overview of these techniques.
Effective means of exploit prevention can also be provided by the Cisco ASA 5500 Series Adaptive Security Appliance, Cisco Catalyst 6500 Series ASA Services Module (ASASM), and the Firewall Services Module (FWSM) for Cisco Catalyst 6500 Series Switches and Cisco 7600 Series Routers using the following method:- Application layer protocol inspection
Effective use of Cisco Intrusion Prevention System (IPS) event actions provides visibility into and protection against attacks that attempt to exploit this vulnerability.
Effective use of Sourcefire Intrusion Prevention System event actions provides visibility into and protection against attacks that attempt to exploit this vulnerability.
-
Organizations are advised to follow their standard risk evaluation and mitigation processes to determine the potential impact of this vulnerability. Triage refers to sorting projects and prioritizing efforts that are most likely to be successful. Cisco has provided documents that can help organizations develop a risk-based triage capability for their information security teams. Risk Triage for Security Vulnerability Announcements and Risk Triage and Prototyping can help organizations develop repeatable security evaluation and response processes.
-
Caution: The effectiveness of any mitigation technique depends on specific customer situations such as product mix, network topology, traffic behavior, and organizational mission. As with any configuration change, evaluate the impact of this configuration prior to applying the change.
Specific information about mitigation and identification is available for these devices:- Cisco ASA, Cisco ASASM, and Cisco FWSM Firewalls
- Cisco ACE
- Cisco Intrusion Prevention System
- Sourcefire Intrusion Prevention System
Cisco ASA, Cisco ASASM, and Cisco FWSM Firewalls
Mitigation: Application Layer Protocol Inspection
Application layer protocol inspection is available beginning in software release 7.2(1) for the Cisco ASA 5500 Series Adaptive Security Appliance, software release 8.5 for the Cisco Catalyst 6500 Series ASA Services Module, and in software release 4.0(1) for the Cisco Firewall Services Module. This advanced security feature performs deep packet inspection of traffic that transits the firewall. Administrators may construct an inspection policy for applications that require special handling through the configuration of inspection class maps and inspection policy maps, which are applied via a global or interface service policy. Application inspection will inspect both IPv4 and IPv6 packets matched in the class-map of the policy.
Additional information about application layer protocol inspection and the Cisco Modular Policy Framework (MPF) is in the Configuring Application Inspection section of Book 2: Cisco ASA Series Firewall CLI Configuration Guide, 9.1.
Caution: Application layer protocol inspection will decrease firewall performance. Administrators are advised to test performance impact in a lab environment before this feature is deployed in production environments.
HTTP Application Inspection
For MS14-005, by using the HTTP inspection engine on the Cisco ASA 5500 Series Adaptive Security Appliances, Cisco 6500 Series ASA Services Modules, and the Cisco Firewall Services Module, administrators can configure regular expressions (regexes) for pattern matching and construct inspection class maps and inspection policy maps. These methods can help protect against specific vulnerabilities, such as the one described in this document, and other threats that may be associated with HTTP traffic. The following HTTP application inspection configuration uses the Cisco MPF to create a policy for inspection of traffic on TCP ports 80, 3128, 8000, 8010, 8080, 8888, and 24326, which are the default ports for the Cisco IPS #WEBPORTS variable. The HTTP application inspection policy will drop connections where the HTTP response body contains any of the regexes that are configured to match the ActiveX control that is associated with this vulnerability.
Caution: The configured regexes can match text strings at any location in the body of an HTML response. Care should be taken to ensure that legitimate business applications that use matching text strings without calling the ActiveX control are not affected. Additional information about regex syntax is in Creating a Regular Expression.
Additional information about ActiveX exploits and mitigations that leverage Cisco firewall technologies is available in the Preventing ActiveX Exploits with Cisco Firewall Application Layer Protocol Inspection Cisco Security Intelligence Operations white paper.
! !-- Configure regexes for the ActiveX Class ID !-- "f5078f39-c551-11d3-89b9-0000f81fe221" and !-- "f6d90f16-9c73-11d3-b32e-00c04f990bb4" ! That are associated to MS14-005 ! regex CLSID_MS14-005-1 "[fF]5078[fF]39[-][cC]551[-] 11[dD]3[-]89[bB]9[-]0000[fF]81[fF][eE]221" regex CLSID_MS14-005-2 "[fF]6[dD]90[fF]16[-]9[cC]73[-] 11[dD]3[-][bB]32[eE][-]00[cC]04[fF]990[bB][bB]4" ! !-- Configure a regex class to match on the regular !-- expressions that are configured above ! class-map type regex match-any MS14-005_regex_class match regex CLSID_MS14-005-1 match regex CLSID_MS14-005-2 ! !-- Configure an object group for the default ports that !-- are used by the Cisco IPS #WEBPORTS variable, which !-- are TCP ports 80 (www), 3128, 8000, 8010, 8080, 8888, !-- and 24326 ! object-group service WEBPORTS tcp port-object eq www port-object eq 3128 port-object eq 8000 port-object eq 8010 port-object eq 8080 port-object eq 8888 port-object eq 24326 ! !-- Configure an access list that uses the WEBPORTS object !-- group, which will be used to match TCP packets that !-- are destined to the #WEBPORTS variable that is used !-- by a Cisco IPS device ! access-list Webports_ACL extended permit tcp any any object-group WEBPORTS ! !-- Configure a class that uses the above-configured !-- access list to match TCP packets that are destined !-- to the ports that are used by the Cisco IPS #WEBPORTS !-- variable ! class-map Webports_Class match access-list Webports_ACL ! !-- Configure an HTTP application inspection policy that !-- identifies, drops, and logs connections that contain !-- the regexes that are configured above ! policy-map type inspect http MS_Feb_2014_policy parameters ! !-- "body-match-maximum" indicates the maximum number of !-- characters in the body of an HTTP message that !-- should be searched in a body match. The default value is !-- 200 bytes. A large number such as shown here may have an !-- impact on system performance. Administrators are advised !-- to test performance impact in a lab environment before !-- this command is deployed in production environments ! body-match-maximum 1380 match response body regex class MS14-005_regex_class drop-connection log ! !-- Add the above-configured "Webports_Class" that matches !-- TCP packets that are destined to the default ports !-- that are used by the Cisco IPS #WEBPORTS variable to !-- the default policy "global_policy" and use it to !-- inspect HTTP traffic that transits the firewall ! policy-map global_policy class Webports_Class inspect http MS_Feb_2014_policy ! !-- By default, the policy "global_policy" is applied !-- globally, which results in the inspection of !-- traffic that enters the firewall from all interfaces ! service-policy global_policy global
For additional information about the configuration and use of object groups, reference the Configuring Objects and ACLs section of Book 1: Cisco ASA Series General Operations CLI Configuration Guide, 9.1.
Additional information about HTTP application inspection and the MPF is in the HTTP Inspection section of Book 2: Cisco ASA Series Firewall CLI Configuration Guide, 9.1.
For information on using the Cisco Firewall command line interface to gauge the effectiveness of application inspection, please refer to the Cisco Security Intelligence Operations white paper Identification of Security Exploits with Cisco ASA, Cisco ASASM, and Cisco FWSM Firewalls.Cisco ACE
Mitigation: Application Protocol Inspection
Application protocol inspection is available for the Cisco ACE Application Control Engine Appliance and Module. This advanced security feature performs deep packet inspection of traffic that transits the Cisco ACE device. Administrators can construct an inspection policy for applications that require special handling through the configuration of inspection class maps and inspection policy maps, which are applied via a global or interface service policy.
Additional information about application protocol inspection is in the Configuring Application Protocol Inspection section of the Security Guide vA5(1.0), Cisco ACE Application Control Engine.
HTTP Deep Packet Inspection
To conduct HTTP deep packet inspection for MS14-005, administrators can configure regular expressions (regexes) for pattern matching and construct inspection class maps and inspection policy maps. These methods can help protect against specific vulnerabilities, such as the one described in this document, and other threats that may be associated with HTTP traffic. The following HTTP application protocol inspection configuration inspects traffic on TCP ports 80, 3128, 8000, 8010, 8080, 8888, and 24326, which are the default ports for the Cisco IPS #WEBPORTS variable. The HTTP application protocol inspection policy will drop connections where the HTTP content contains any of the regexes that are configured to match the ActiveX control that is associated with this vulnerability.
Caution: The configured regexes can match text strings at any location in the content of an HTML packet. Care should be taken to ensure that legitimate business applications that use matching text strings without calling the ActiveX control are not affected.
Additional information about ActiveX exploits and mitigations that leverage the Cisco ACE Application Control Engine Appliance and Module is available in the Preventing ActiveX Exploits with Cisco Application Control Engine Application Layer Protocol Inspection Cisco Security Intelligence Operations white paper.
! !-- Configure an HTTP application inspection class that !-- looks for HTTP packets that contain the regexes for the !-- ActiveX Class ID !-- "f5078f39-c551-11d3-89b9-0000f81fe221" !-- and "f6d90f16-9c73-11d3-b32e-00c04f990bb4" !-- that are associated with MS14-005 ! ! class-map type http inspect match-any MS14-005_class match content ".*[fF]5078[fF]39[-][cC]551[-] 11[dD]3[-]89[bB]9[-]0000[fF]81[fF][eE]221.*" match content ".*[fF]6[dD]90[fF]16[-]9[cC]73[-] 11[dD]3[-][bB]32[eE][-]00[cC]04[fF]990[bB][bB]4.*" ! !-- Configure an HTTP application inspection policy that !-- identifies, resets, and logs connections that contain !-- the regexes that are configured above ! policy-map type inspect http all-match MS_Feb_2014 class MS14-005_class reset log ! !-- Configure an access list that matches TCP packets !-- that are destined to the #WEBPORTS variable that is !-- used by a Cisco IPS device ! access-list WEBPORTS line 8 extended permit tcp any any eq www access-list WEBPORTS line 16 extended permit tcp any any eq 3128 access-list WEBPORTS line 24 extended permit tcp any any eq 8000 access-list WEBPORTS line 32 extended permit tcp any any eq 8010 access-list WEBPORTS line 40 extended permit tcp any any eq 8080 access-list WEBPORTS line 48 extended permit tcp any any eq 8888 access-list WEBPORTS line 56 extended permit tcp any any eq 24326 ! !-- Configure a Layer 4 class that uses the above-configured !-- access list to match TCP packets that are destined !-- to the ports that are used by the Cisco IPS #WEBPORTS !-- variable ! class-map match-all L4_http_class match access-list WEBPORTS ! !-- Configure a Layer 4 policy that applies the HTTP application !-- inspection policy configured above to TCP packets that !-- are destined to the ports that are used by the Cisco IPS !-- #WEBPORTS variable ! policy-map multi-match L4_MS_Feb_2014 class L4_http_class inspect http policy MS_Feb_2014 ! !-- Apply the configuration globally across all interfaces, !-- which results in the inspection of all traffic that enters !-- the ACE ! service-policy input L4_MS_Feb_2014
For information on how to use the ACE command line interface to gauge the effectiveness of application inspection, please refer to the Cisco Security Intelligence Operations white paper Identification of Malicious Traffic Using Cisco ACE.Cisco Intrusion Prevention System
Mitigation: Cisco IPS Signature Event Actions
Administrators can use the Cisco IPS appliances and services modules to provide threat detection and help prevent attempts to exploit several of the vulnerabilities described in this document. The following table provides an overview of CVE identifiers and the respective Cisco IPS signatures that will trigger events on potential attempts to exploit this vulnerability.
CVE ID Signature Release Signature ID Signature Name Enabled Severity Fidelity* CVE-2014-0254 S771 3742-0 Windows Surface RT IPv6 DoS Yes Medium 80 CVE-2014-0267 S771 3746-0 Microsoft Internet Explorer Memory Corruption Vulnerability Yes High 90 CVE-2014-0269 S771 3748-0 Microsoft Internet Explorer Memory Corruption Vulnerability Yes High 85 CVE-2014-0270 S771 3747-0 Microsoft Internet Explorer Remote Memory Corruption vulnerability Yes High 90 CVE-2014-0271 S771 3686-0 Microsoft Internet Explorer Remote Memory Corruption vulnerability Yes High 85 CVE-2014-0272 S771 3749-0 Microsoft Internet Explorer Remote Memory Corruption vulnerability Yes High 85 CVE-2014-0273 S771 3689-0 Microsoft Internet Explorer Memory Corruption Vulnerability Yes High 85 CVE-2014-0274 S771 3687-0 Microsoft Internet Explorer Memory Corruption Vulnerability Yes High 85 CVE-2014-0275 S771 3674-0 Microsoft Windows Internet Explorer Memory Corruption Yes High 85 CVE-2014-0276 S771 3678-0 Microsoft Internet Explorer Memory Corruption Yes High 85 CVE-2014-0277 S771 3688-0 Microsoft Internet Explorer Memory Corruption Yes High 85 CVE-2014-0278 S771 3697-0 Microsoft Internet Explorer Memory Corruption Yes High 85 CVE-2014-0279 S771 3727-0 Microsoft Internet Explorer Use After Free Vulnerability Yes High 90 CVE-2014-0281 S771 3741-0 Microsoft Internet Explorer Use After Free Vulnerability Yes High 90 CVE-2014-0283 S771 3722-0 Microsoft Internet Explorer Memory Corruption Vulnerability No High 85 CVE-2014-0284 S771 3726-0 Microsoft Internet Explorer Memory Corruption Vulnerability Yes High 85 CVE-2014-0285 S771 3724-0 Microsoft Internet Explorer Memory Corruption Vulnerability Yes High 85 CVE-2014-0286 S771 3725-0 Microsoft Internet Explorer Memory Corruption Vulnerability No High 85 CVE-2014-0287 S771 3684-0 icrosoft Internet Explorer Remote Memory Corruption Yes High 85 CVE-2014-0288 S771 3693-0 Microsoft Internet Explorer Memory Corruption No High 85 CVE-2014-0289 S771 3715-0 Microsoft Internet Explorer Memory Corruption No High 85 CVE-2014-0290 S771 3717-0 Microsoft Internet Explorer Memory Corruption No High 85 CVE-2014-0263 S771 3685-0 Microsoft Internet Explorer Remote Memory Corruption Yes High 85 CVE-2014-0266 S771 3695-0 MSXML Information Disclosure Vulnerability Yes High 85
* Fidelity is also referred to as Signature Fidelity Rating (SFR) and is the relative measure of the accuracy of the signature (predefined). The value ranges from 0 through 100 and is set by Cisco Systems, Inc.
Administrators can configure Cisco IPS sensors to perform an event action when an attack is detected. The configured event action performs preventive or deterrent controls to help protect against an attack that is attempting to exploit the vulnerabilities listed in the preceding table.
Exploits that use spoofed IP addresses may cause a configured event action to inadvertently deny traffic from trusted sources.
Cisco IPS sensors are most effective when deployed in inline protection mode combined with the use of an event action. Automatic Threat Prevention for Cisco IPS 7.x and 6.x sensors that are deployed in inline protection mode provides threat prevention against an attack that is attempting to exploit the vulnerability that is described in this document. Threat prevention is achieved through a default override that performs an event action for triggered signatures with a riskRatingValue greater than 90.
For additional information about the risk rating and threat rating calculation, reference Risk Rating and Threat Rating: Simplify IPS Policy Management.
For information on using Cisco Security Manager to view the activity from a Cisco IPS sensor, see Identification of Malicious Traffic Using Cisco Security Manager white paper.Cisco Sourcefire Signature Information
The following Cisco Sourcefire Snort signatures are available for the Microsoft February 2014 Security Update:
Microsoft Advisory ID Applicable Rules MS14-005 1:29680 MS14-005
1:29681 MS14-005
1:29682 MS14-005
1:29683 MS14-005
1:29684 MS14-005
1:29685 MS14-005
1:29686 MS14-005
1:29687 MS14-005
1:29688 MS14-005
1:29689 MS14-005
1:29690 MS14-005
1:29691 MS14-005
1:29692 MS14-005
1:29693 MS14-005
1:29694 MS14-005
1:29695 MS14-005
1:29696 MS14-005
1:29697 MS14-005
1:29698 MS14-005
1:29699 MS14-005
1:29700 MS14-005
1:29701 MS14-005
1:29702 MS14-005
1:29703 MS14-005
1:29704 MS14-005
1:29705 MS14-006 1:29675 MS14-007 1:29713 MS14-007 1:29714 MS14-009
1:29715 MS14-010
1:29655 MS14-010
1:29667 MS14-010
1:29668 MS14-010
1:29671 MS14-010
1:29673 MS14-010
1:29674 MS14-010
1:29706
MS14-010
1:29707
MS14-010
1:29708
MS14-010
1:29709
MS14-010
1:29710 MS14-010
1:29711 MS14-010
1:29712 MS14-010
1:29716 MS14-010
1:29717 MS14-010
1:29718 MS14-010
1:29719 MS14-010
1:29720 MS14-010
1:29721 MS14-010
1:29722 MS14-010
1:29727 MS14-010
1:29728 MS14-010
1:29729 MS14-010
1:29730 MS14-010
1:29731 MS14-010
1:29732 MS14-010 1:29737 MS14-010 1:29738 MS14-010 1:29741 MS14-010 1:29742 MS14-010 1:29743 MS14-010 1:29744 MS14-011
1:23178 MS14-011 1:24296
-
THIS DOCUMENT IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR USE. YOUR USE OF THE INFORMATION ON THE DOCUMENT OR MATERIALS LINKED FROM THE DOCUMENT IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS DOCUMENT AT ANY TIME.
-
Version Description Section Date 1 Alert History
Initial Release2014-February-11 18:55 GMT
-
Complete information on reporting security vulnerabilities in Cisco products, obtaining assistance with security incidents, and registering to receive security information from Cisco, is available on Cisco's worldwide website at https://sec.cloudapps.cisco.com/security/center/resources/security_vulnerability_policy.html. This includes instructions for press inquiries regarding Cisco security notices. All Cisco security advisories are available at http://www.cisco.com/go/psirt.
-
The security vulnerability applies to the following combinations of products.
Primary Products Microsoft, Inc. .NET Framework 1.0 (SP3) | 1.1 (SP1) | 2.0 (SP2) | 3.5 (Base, SP1) | 3.5.1 (Base) | 4.0 (Base) | 4.5 (Base) | 4.5.1 (Base) Internet Explorer 6.0 (Base, SP1, SP2) | 7.0 (Base) | 8.0 (Base) | 9.0 (Base) | 10.0 (Base) | 11.0 (Base) Microsoft VBScript 5.6 (Base) | 5.7 (Base) | 5.8 (Base) Windows 7 for 32-bit systems (Base, SP1) | for x64-based systems (Base, SP1) Windows 8 for 32-bit systems (Base) | for x64-based systems (Base) Windows 8.1 for 32-bit Systems (Base) | for x64-based Systems (Base) Windows RT Original Release (Base) | 8.1 (Base) Windows Server 2003 Datacenter Edition (Base, SP1, SP2) | Datacenter Edition, 64-bit (Itanium) (Base, SP1, SP2) | Datacenter Edition x64 (AMD/EM64T) (Base, SP1, SP2) | Enterprise Edition (Base, SP1, SP2) | Enterprise Edition, 64-bit (Itanium) (Base, SP1, SP2) | Enterprise Edition x64 (AMD/EM64T) (Base, SP1, SP2) | Standard Edition (Base, SP1, SP2) | Standard Edition, 64-bit (Itanium) (Base, SP1, SP2) | Standard Edition x64 (AMD/EM64T) (Base, SP1, SP2) | Web Edition (Base, SP1, SP2) Windows Server 2008 Datacenter Edition (Base, SP1, SP2) | Datacenter Edition, 64-bit (Base, SP1, SP2) | Itanium-Based Systems Edition (Base, SP1, SP2) | Enterprise Edition (Base, SP1, SP2) | Enterprise Edition, 64-bit (Base, SP1, SP2) | Essential Business Server Standard (Base, SP1, SP2) | Essential Business Server Premium (Base, SP1, SP2) | Essential Business Server Premium, 64-bit (Base, SP1, SP2) | Standard Edition (Base, SP1, SP2) | Standard Edition, 64-bit (Base, SP1, SP2) | Web Server (Base, SP1, SP2) | Web Server, 64-bit (Base, SP1, SP2) Windows Server 2008 R2 x64-Based Systems Edition (Base, SP1) | Itanium-Based Systems Edition (Base, SP1) Windows Server 2012 Original Release (Base) Windows Server 2012 R2 Original Release (Base) Forefront Protection 2010 for Exchange Server Original Release (Base)
Associated Products Microsoft, Inc. Windows 7 for 32-bit systems | for x64-based systems Windows 8 for 32-bit systems | for x64-based systems Windows 8.1 for 32-bit Systems | for x64-based Systems Windows RT Original Release | 8.1 Windows Server 2003 Datacenter Edition | Datacenter Edition, 64-bit (Itanium) | Datacenter Edition x64 (AMD/EM64T) | Enterprise Edition | Enterprise Edition, 64-bit (Itanium) | Enterprise Edition x64 (AMD/EM64T) | Standard Edition | Standard Edition, 64-bit (Itanium) | Standard Edition x64 (AMD/EM64T) | Web Edition Windows Server 2008 Datacenter Edition | Datacenter Edition, 64-bit | Itanium-Based Systems Edition | Enterprise Edition | Enterprise Edition, 64-bit | Essential Business Server Standard | Essential Business Server Premium | Essential Business Server Premium, 64-bit | Standard Edition | Standard Edition, 64-bit | Web Server | Web Server, 64-bit Windows Server 2008 R2 x64-Based Systems Edition | Itanium-Based Systems Edition Windows Server 2012 Original Release Windows Server 2012 R2 Original Release Windows Vista Home Basic (Base, SP1, SP2) | Home Premium (Base, SP1, SP2) | Business (Base, SP1, SP2) | Enterprise (Base, SP1, SP2) | Ultimate (Base, SP1, SP2) | Home Basic x64 Edition (Base, SP1, SP2) | Home Premium x64 Edition (Base, SP1, SP2) | Business x64 Edition (Base, SP1, SP2) | Enterprise x64 Edition (Base, SP1, SP2) | Ultimate x64 Edition (Base, SP1, SP2)
-
THIS DOCUMENT IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR USE. YOUR USE OF THE INFORMATION ON THE DOCUMENT OR MATERIALS LINKED FROM THE DOCUMENT IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE ALERTS AT ANY TIME.
A standalone copy or paraphrase of the text of this document that omits the distribution URL is an uncontrolled copy and may lack important information or contain factual errors. The information in this document is intended for end users of Cisco products