Cisco Applied Mitigation Bulletin-
Contents
Cisco Response
Device-Specific Mitigation and Identification
Additional Information
Cisco Security Procedures
Related Information
Microsoft announced eight security bulletins that address 24 vulnerabilities as part of the monthly security bulletin release on October 14, 2014. A summary of these bulletins is on the Microsoft website at http://technet.microsoft.com/en-us/security/bulletin/ms14-oct. 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, or can be exploited using web-based attacks (these include but are not limited to cross-site scripting, phishing, and web-based email threats) or email attachments are in the following list:
The vulnerabilities that have a network mitigation, including web and email security issues, are in the following list. Cisco devices provide several countermeasures for the vulnerabilities that have a network attack vector, which will be discussed in detail later in this document.
-
MS14-059, Vulnerability in ASP.NET MVC Could Allow Security Feature Bypass(2990942]: This vulnerability has been assigned CVE identifier CVE-2014-4075. This vulnerability can be exploited remotely without authentication and requires user interaction. The attack vector is via cross-site scripting and phishing. Successful exploitation of this vulnerability may allow information disclosure, which enables an attacker to learn information about the affected device. The attack vector is the HTTP protocol using TCP port 80 and the HTTPS protocol using TCP port 443. Due to the nature of cross-site scripting vulnerabilities, no additional information will be presented in this bulletin.
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.
Information about vulnerable, unaffected, and fixed software is available in the Microsoft Security Bulletin Summary for October 2014, which is available at the following link: https://technet.microsoft.com/library/security/ms14-oct
MS14-060, Vulnerability in OLE Could Allow Remote Code Execution(3000869): This vulnerability has been assigned Common Vulnerabilities and Exposures (CVE) identifier CVE-2014-4114. This vulnerability can be exploited remotely without authentication and requires user interaction. Successful exploitation of the vulnerability that is associated with CVE-2014-4114 may allow arbitrary code execution or information disclosure, which enables an attacker to learn information about the affected device.Cisco ASA 5500 and 5500-X 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.
The attack vectors for exploitation are through IPv4 and IPv6 packets using the following protocols and ports:
- NetBIOS over TCP/IP (NBT) using TCP port 139
- UAAC using TCP port 145
-
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 October 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.
-
The vulnerabilities that have a client software attack vector, can be exploited locally on the vulnerable device, require user interaction, or can be exploited using web-based attacks (these include but are not limited to cross-site scripting, phishing, and web-based email threats) or email attachments are in the following list:
These vulnerabilities are mitigated most successfully at the endpoint through software updates, user education, desktop administration best practices, and endpoint protection software such as Host Intrusion Prevention Systems (HIPS) or antivirus products.
The vulnerabilities that have a network mitigation, including web and email security issues, are in the following list. Cisco devices provide several countermeasures for these vulnerabilities. This section of the document provides an overview of these techniques.
Cisco IOS Software can provide effective means of exploit prevention and exploit identification using transit access control lists (tACLs).
This protection mechanism filters and drops, as well as verifies the source IP address of, packets that are attempting to exploit the vulnerability that has a network attack vector.
Effective means of exploit prevention and exploit identification can also be provided by Cisco ASA 5500 and 5500-X 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 methods:
- Transit access control lists (tACLs)
- Application layer protocol inspection
These protection mechanisms filter and drop, as well as verify the source IP address of, packets that are attempting to exploit the vulnerabilities that have a network attack vector.
Effective exploit prevention can also be provided by the Cisco ACE Application Control Engine Appliance and Module using application protocol inspection.
Cisco IOS NetFlow and Flexible NetFlow records can provide visibility into network-based exploitation attempts.
Effective use of Cisco Intrusion Prevention System (IPS) event actions provides visibility into and protection against attacks that attempt to exploit these vulnerabilities.
-
Organizations are advised to follow their standard risk evaluation and mitigation processes to determine the potential impact of these vulnerabilities. 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 IOS Routers and Switches
- Cisco ASA, Cisco ASASM, and Cisco FWSM Firewalls
- Cisco Intrusion Prevention System
- Sourcefire Intrusion Prevention System
Cisco IOS Routers and Switches
Mitigation: Transit Access Control Lists
For MS14-060, to protect the network from traffic that enters the network at ingress access points, which may include Internet connection points, partner and supplier connection points, or VPN connection points, administrators are advised to deploy transit access control lists (tACLs) to perform policy enforcement. Administrators can construct a tACL by explicitly permitting only authorized traffic to enter the network at ingress access points or permitting authorized traffic to transit the network in accordance with existing security policies and configurations. A tACL workaround cannot provide complete protection against this vulnerability when the attack originates from a trusted source address. The tACL policy denies unauthorized IPv4 and IPv6 packets sourced on TCP ports 139 and 145 that are sent to affected devices. In the following example, 192.168.60.0/24 and 2001:DB8:1:60::/64 represent the IP address space that is used by the affected devices. Care should be taken to allow required traffic for routing and administrative access prior to denying all unauthorized traffic. Additional information about tACLs is in Transit Access Control Lists: Filtering at Your Edge.
! !-- Include explicit permit statements for trusted sources that !-- require access on the vulnerable TCP ports ! access-list 150 permit tcp host 192.168.100.1 eq 139 192.168.60.0 0.0.0.255 access-list 150 permit tcp host 192.168.100.1 eq 145 192.168.60.0 0.0.0.255 ! !-- The following vulnerability-specific access control entries !-- (ACEs) can aid in identification of attacks ! access-list 150 deny tcp any eq 139 192.168.60.0 0.0.0.255 access-list 150 deny tcp any eq 145 192.168.60.0 0.0.0.255 ! !-- Permit or deny all other Layer 3 and Layer 4 traffic in accordance !-- with existing security policies and configurations ! !-- Explicit deny for all other IP traffic ! access-list 150 deny ip any any ! ! !-- Create the corresponding IPv6 tACL ! ipv6 access-list IPv6-Transit-ACL-Policy ! !-- Include explicit permit statements for trusted sources that !-- require access on the vulnerable TCP ports ! permit tcp host 2001:DB8::100:1 eq 139 2001:DB8:1:60::/64 permit tcp host 2001:DB8::100:1 eq 145 2001:DB8:1:60::/64 ! !-- The following vulnerability-specific ACEs can !-- aid in identification of attacks to global and !-- link-local addresses ! deny tcp any eq 139 2001:DB8:1:60::/64 deny tcp any eq 145 2001:DB8:1:60::/64 ! !-- Permit or deny all other Layer 3 and Layer 4 traffic in !-- accordance with existing security policies and configurations !-- and allow IPv6 neighbor discovery packets, which !-- include neighbor solicitation packets and neighbor !-- advertisement packets ! permit icmp any any nd-ns permit icmp any any nd-na ! !-- Explicit deny for all other IPv6 traffic ! deny ipv6 any any ! ! !-- Apply tACLs to interface in the ingress direction ! interface GigabitEthernet0/0 ip access-group 150 in ipv6 traffic-filter IPv6-Transit-ACL-Policy in
Note that filtering with an interface access list will elicit the transmission of ICMP unreachable messages back to the source of the filtered traffic. Generating these messages could have the undesired effect of increasing CPU utilization on the device. In Cisco IOS Software, ICMP unreachable generation is limited to one packet every 500 milliseconds by default. ICMP unreachable message generation can be disabled using the interface configuration commands no ip unreachables and no ipv6 unreachables. ICMP unreachable rate limiting can be changed from the default using the global configuration commands ip icmp rate-limit unreachable interval-in-ms and ipv6 icmp error-interval interval-in-ms.
For information about how to use the Cisco IOS command-line interface to gauge the effectiveness of the tACL, see the Cisco Security Intelligence Operations white paper Identifying the Effectiveness of Security Mitigations Using Cisco IOS Software.
Identification: IPv4 and IPv6 Traffic Flow Identification Using Cisco IOS NetFlow and Flexible NetFlow
Administrators can configure Cisco IOS NetFlow and Cisco IOS Flexible NetFlow on Cisco IOS routers and switches to aid in the identification of IPv4 and IPv6 traffic flows that may be attempts to exploit this vulnerability. Administrators are advised to investigate flows to determine whether they are attempts to exploit this vulnerability or whether they are legitimate traffic flows. Administrators can also configure filters to highlight traffic on individual ports to identify traffic flows that may be attempts to exploit the vulnerability mentioned in this document. For additional information, see the Cisco IOS NetFlow and Cisco IOS Flexible NetFlow section of the paper Identifying the Effectiveness of Security Mitigations Using Cisco IOS Software.
Cisco ASA, Cisco ASASM, and Cisco FWSM Firewalls
Mitigation: Transit Access Control Lists
For MS14-060, to protect the network from traffic that enters the network at ingress access points, which may include Internet connection points, partner and supplier connection points, or VPN connection points, administrators are advised to deploy tACLs to perform policy enforcement. Administrators can construct a tACL by explicitly permitting only authorized traffic to enter the network at ingress access points or permitting authorized traffic to transit the network in accordance with existing security policies and configurations. A tACL workaround cannot provide complete protection against this vulnerability when the attack originates from a trusted source address.
The tACL policy denies unauthorized IPv4 and IPv6 packets sourced on TCP ports 139 and 145 that are sent to affected devices. In the following example, 192.168.60.0/24 and 2001:DB8:1:60::/64 represent the IP address space that is used by the affected devices, and the hosts at 192.168.100.1 and 2001:DB8::100:1 are considered trusted sources that require access to the affected devices. Care should be taken to allow required traffic for routing and administrative access prior to denying all unauthorized traffic.
For additional information about tACLs, see Transit Access Control Lists: Filtering at Your Edge.
! !-- Include explicit permit statements for trusted sources !-- that require access on the vulnerable TCP ports ! access-list tACL-Policy extended permit tcp host 192.168.100.1 eq 139
192.168.60.0 255.255.255.0 access-list tACL-Policy extended permit tcp host 192.168.100.1 eq 145
192.168.60.0 255.255.255.0 ! !-- The following vulnerability-specific access control entries !-- (ACEs) can aid in identification of attacks ! access-list tACL-Policy extended deny tcp any eq 139 192.168.60.0 255.255.255.0 access-list tACL-Policy extended deny tcp any eq 145 192.168.60.0 255.255.255.0 ! !-- Permit or deny all other Layer 3 and Layer 4 traffic in accordance !-- with existing security policies and configurations ! !-- Explicit deny for all other IP traffic ! access-list tACL-Policy extended deny ip any 192.168.60.0 255.255.255.0 ! ! !-- Create the corresponding IPv6 tACL ! ! !-- Include explicit permit statements for trusted sources that !-- require access on the vulnerable TCP ports ! ipv6 access-list IPv6-tACL-Policy permit tcp host 2001:DB8::100:1 eq 139 2001:DB8:1:60::/64 ipv6 access-list IPv6-tACL-Policy permit tcp host 2001:DB8::100:1 eq 145 2001:DB8:1:60::/64 ! !-- The following vulnerability-specific ACEs can !-- aid in identification of attacks ! ipv6 access-list IPv6-tACL-Policy deny tcp any eq 139 2001:DB8:1:60::/64 ipv6 access-list IPv6-tACL-Policy deny tcp any eq 145 2001:DB8:1:60::/64 ! !-- Permit or deny all other Layer 3 and Layer 4 traffic in !-- accordance with existing security policies and configurations ! ! !-- Explicit deny for all other IPv6 traffic ! ipv6 access-list IPv6-tACL-Policy deny ip any any ! ! !-- Apply tACLs to interfaces in the ingress direction ! access-group tACL-Policy in interface outside access-group IPv6-tACL-Policy in interface outsideFor information about using the Cisco firewall command-line interface to gauge the effectiveness of tACLs, see the Cisco Security Intelligence Operations white paper Identification of Security Exploits with Cisco ASA, Cisco ASASM, and Cisco FWSM Firewalls.
Starting in Cisco ASA Software Release 9.0, ACLs (namely unified ACLs) support IPv4 and IPv6 addresses. A mix of IPv4 and IPv6 addresses can be specified for the source and destination of the ACL. The any4 and any6 keywords were added to represent IPv4-only and IPv6-only traffic, respectively.
The IPv4 and IPv6 access list entries (ACEs) presented in the IPv4 and IPv6 ACLs of this section could also be incorporated in one unified ACL.
For additional information about unified ACLs, see the Adding an Extended Access List section of the Cisco ASA configuration guide.
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 these vulnerabilities.
CVE ID Signature Release Signature ID Signature Name Enabled Severity Fidelity* CVE-2014-4117 S828 4732-0 Microsoft Office Web Apps Remote Code Execution Yes High 85 CVE-2014-4126 S828 4728-0 Microsoft Internet Explorer Memory Corruption Vulnerability Yes High 85 CVE-2014-4127 S828 4726-0 Microsoft Internet Explorer Memory Corruption Vulnerability Yes High 85 CVE-2014-4128 S828 4727-0 Microsoft Internet Explorer Memory Corruption Vulnerability Yes High 85 CVE-2014-4129 S828 4713-0 Microsoft Internet Explorer Use After Free Yes High 85 CVE-2014-4130 S828 4714-0 Microsoft Internet Explorer Use After Free Yes High 85 CVE-2014-4132 S828 4730-0 Microsoft Internet Explorer Use After Free Yes High 85 CVE-2014-4133 S828 4721-0 Microsoft Internet Explorer Memory Corruption Yes High 80 CVE-2014-4134 S828 4721-0 Microsoft Internet Explorer Remote Code Execution Yes High 80 CVE-2014-4138 S828 4716-0 Microsoft Internet Explorer Memory Corruption Yes High 80 * 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.
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 about using Cisco Security Manager to view the activity from a Cisco IPS sensor, see Identification of Malicious Traffic Using Cisco Security Manager white paper.
Sourcefire Signature Information
The following Sourcefire Snort signatures are available for the Microsoft October 2014 Security Update.
Microsoft Advisory ID Microsoft Advisory Name Applicable Rules MS14-056 Microsoft Internet Explorer Remote Code Execution 1:32137 through 1:32138, 1:32153 through 32164, 1:32166 through 1:32169, 1:32182 through 1:32185
MS14-057 Vulnerabilities in .NET Framework Could Allow Remote Code Execution 1:32139 through 1:32140, 1:32149 through 1:32152 MS14-058 Vulnerability in Kernel-Mode Driver Could Allow Elevation of Privilege 1:32141 through 1:32146, 1:32190 through 1:32191 MS14-059 Vulnerability in ASP.NET MVC Could Allow Security Feature Bypass 1:7070 MS14-061 Vulnerability in Microsoft Word and Office Web Apps Could Allow Remote Code Execution 1:32147 through 1:32148 For information about using Sourcefire Snort and Sourcefire Next Generation IPS, reference Sourcefire Next-Generation Security.
-
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.
-
Show Less
-
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 2.0 (SP2) | 3.5 (Base, SP1) | 3.5.1 (Base) | 4.0 (Base) | 4.5 (Base) | 4.5.1 (Base) | 4.5.2 (Base) ASP.NET MVC 2.0 (Base) | 3.0 (Base) | 4.0 (Base) | 5.0 (Base) | 5.1 (Base) Internet Explorer 6.0 (Base) | 7.0 (Base) | 8.0 (Base) | 9.0 (Base) | 10.0 (Base) | 11.0 (Base) Office 2007 (SP3) | 2010 (Base, SP1, SP2) Office Compatibility Pack SP3 (Base) Office for Mac 2011 (Base) Windows 7 for 32-bit systems (SP1) | for x64-based systems (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 (SP2) | Datacenter Edition, 64-bit (Itanium) (SP2) | Datacenter Edition x64 (AMD/EM64T) (SP2) | Enterprise Edition (SP2) | Enterprise Edition, 64-bit (Itanium) (SP2) | Enterprise Edition x64 (AMD/EM64T) (SP2) | Standard Edition (SP2) | Standard Edition, 64-bit (Itanium) (SP2) | Standard Edition x64 (AMD/EM64T) (SP2) | Web Edition (SP2) Windows Server 2008 Datacenter Edition (SP2) | Datacenter Edition, 64-bit (SP2) | Itanium-Based Systems Edition (SP2) | Enterprise Edition (SP2) | Enterprise Edition, 64-bit (SP2) | Essential Business Server Standard (SP2) | Essential Business Server Premium (SP2) | Essential Business Server Premium, 64-bit (SP2) | Standard Edition (SP2) | Standard Edition, 64-bit (SP2) | Web Server (SP2) | Web Server, 64-bit (SP2) Windows Server 2008 R2 x64-Based Systems Edition (SP1) | Itanium-Based Systems Edition (SP1) Windows Server 2012 Original Release (Base) Windows Server 2012 R2 Original Release (Base) Windows Vista Home Basic (SP2) | Home Premium (SP2) | Business (SP2) | Enterprise (SP2) | Ultimate (SP2) | Home Basic x64 Edition (SP2) | Home Premium x64 Edition (SP2) | Business x64 Edition (SP2) | Enterprise x64 Edition (SP2) | Ultimate x64 Edition (SP2) Word 2007 (SP3) | 2010 (SP1, SP2) SharePoint Foundation 2010 (SP1, SP2) Office Web Apps 2010 (Base, SP1, SP2)
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 | Home Premium | Business | Enterprise | Ultimate | Home Basic x64 Edition | Home Premium x64 Edition | Business x64 Edition | Enterprise x64 Edition | Ultimate x64 Edition
-
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