Microsoft Vulnerability Research Advisory MSVR13-008
Cisco Security Service IPC Message Heap Corruption Could Allow Elevation of Privilege
Published: June 18, 2013
Microsoft is providing notification of the discovery and remediation of a vulnerability in the Cisco Host Scan component of Cisco AnyConnect Secure Mobility and Cisco Secure Desktop software. The vulnerability affects the Host Scan component included in Cisco AnyConnect VPN Client and Cisco AnyConnect Secure Mobility Client software (version 3.1.00495 and earlier versions). Microsoft discovered and disclosed the vulnerability under coordinated vulnerability disclosure to the affected vendor, Cisco Systems, Inc. Cisco has remediated the vulnerability in their software.
A vulnerability exists in the way that the Cisco Security Service component (in Cisco Host Scan) handles heap allocation for IPC messages. A user running as a standard user account who successfully exploited this vulnerability could gain elevated privileges and run arbitrary code in the security context of the system account.
Microsoft Vulnerability Research reported this issue to and coordinated with Cisco to ensure remediation of this issue. The vulnerability has been assigned the entry, CVE-2013-1173, in the Common Vulnerabilities and Exposures list. For more information, see the Cisco Security Notice: Cisco Host Scan Heap Overflow Vulnerability.
- For an attack to be successful, Host Scan functionality must be enabled.
- An attacker must have valid logon credentials and be able to log on to exploit this vulnerability.
Purpose and Recommendation
Purpose of Advisory: To notify users of a vulnerability and its remediation.
Advisory Status: Advisory published.
Recommendation: Review the Suggested Actions section and configure as appropriate.
For more information about this issue, see the following references:
|Common Vulnerabilities and Exposures||CVE-2013-1173|
Affected and Non-Affected Software
This advisory discusses the following software:
|Cisco AnyConnect VPN Client version 3.1.00495 and earlier versions|
|Cisco AnyConnect Secure Mobility Client version 3.1.00495 and earlier versions|
|Cisco AnyConnect VPN Client version 3.1.01065|
|Cisco AnyConnect Secure Mobility Client version 3.1.01065|
Frequently Asked Questions
What is the scope of this advisory?
This advisory is part of a coordinated release with affected vendors to inform customers of a security issue that may affect their systems.
Is this a security vulnerability that requires Microsoft to issue a security update?
No. This vulnerability has been fixed via an update from the affected third-party vendors. The update remediates the software listed in the table, Affected Software.
What is the scope of the vulnerability?
This is an elevation of privilege vulnerability.
What causes the vulnerability?
The vulnerability is caused when the Cisco Security Service component (in Cisco Host Scan) improperly handles memory for IPC messages.
What might an attacker use this vulnerability to do?
An attacker who successfully exploited this vulnerability could gain elevated privileges and run arbitrary code in the security context of the system account.
How could an attacker exploit the vulnerability?
An attacker could exploit this vulnerability by sending specially crafted messages to the affected product.
Upgrade to the latest version of the affected products.
Microsoft thanks the following:
- Kostya Kortchinsky of Microsoft and Cisco for working toward a resolution
The information provided in this advisory is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
- V1.0 (June 18, 2013): Advisory published.
Built at 2014-04-18T13:49:36Z-07:00