ID CVE-2013-3466
Summary The EAP-FAST authentication module in Cisco Secure Access Control Server (ACS) 4.x before 4.2.1.15.11, when a RADIUS server configuration is enabled, does not properly parse user identities, which allows remote attackers to execute arbitrary commands via crafted EAP-FAST packets, aka Bug ID CSCui57636.
References
Vulnerable Configurations
  • Cisco Secure Access Control Server (ACS) 4.2.1.15.10
    cpe:2.3:a:cisco:secure_access_control_server:4.2.1.15.10
  • Cisco Secure Access Control Server (ACS) 4.2.1.15.9
    cpe:2.3:a:cisco:secure_access_control_server:4.2.1.15.9
  • Cisco Secure Access Control Server (ACS) 4.2.1.15.8
    cpe:2.3:a:cisco:secure_access_control_server:4.2.1.15.8
  • Cisco Secure Access Control Server (ACS) 4.2.1.15.7
    cpe:2.3:a:cisco:secure_access_control_server:4.2.1.15.7
  • Cisco Secure Access Control Server (ACS) 4.2.1.15.6
    cpe:2.3:a:cisco:secure_access_control_server:4.2.1.15.6
  • Cisco Secure Access Control Server (ACS) 4.2.1.15.4
    cpe:2.3:a:cisco:secure_access_control_server:4.2.1.15.4
  • Cisco Secure Access Control Server (ACS) 4.2.1.15.3
    cpe:2.3:a:cisco:secure_access_control_server:4.2.1.15.3
  • Cisco Secure Access Control Server (ACS) 4.2.1.15.2
    cpe:2.3:a:cisco:secure_access_control_server:4.2.1.15.2
  • Cisco Secure Access Control Server (ACS) 4.2.1.15.1
    cpe:2.3:a:cisco:secure_access_control_server:4.2.1.15.1
  • Cisco Secure Access Control Server (ACS) 4.2.1.15.0
    cpe:2.3:a:cisco:secure_access_control_server:4.2.1.15.0
CVSS
Base: 9.3 (as of 04-11-2016 - 15:48)
Impact:
Exploitability:
CWE CWE-287
CAPEC
  • Authentication Abuse
    An attacker obtains unauthorized access to an application, service or device either through knowledge of the inherent weaknesses of an authentication mechanism, or by exploiting a flaw in the authentication scheme's implementation. In such an attack an authentication mechanism is functioning but a carefully controlled sequence of events causes the mechanism to grant access to the attacker. This attack may exploit assumptions made by the target's authentication procedures, such as assumptions regarding trust relationships or assumptions regarding the generation of secret values. This attack differs from Authentication Bypass attacks in that Authentication Abuse allows the attacker to be certified as a valid user through illegitimate means, while Authentication Bypass allows the user to access protected material without ever being certified as an authenticated user. This attack does not rely on prior sessions established by successfully authenticating users, as relied upon for the "Exploitation of Session Variables, Resource IDs and other Trusted Credentials" attack patterns.
  • Exploiting Trust in Client (aka Make the Client Invisible)
    An attack of this type exploits a programs' vulnerabilities in client/server communication channel authentication and data integrity. It leverages the implicit trust a server places in the client, or more importantly, that which the server believes is the client. An attacker executes this type of attack by placing themselves in the communication channel between client and server such that communication directly to the server is possible where the server believes it is communicating only with a valid client. There are numerous variations of this type of attack.
  • Utilizing REST's Trust in the System Resource to Register Man in the Middle
    This attack utilizes a REST(REpresentational State Transfer)-style applications' trust in the system resources and environment to place man in the middle once SSL is terminated. Rest applications premise is that they leverage existing infrastructure to deliver web services functionality. An example of this is a Rest application that uses HTTP Get methods and receives a HTTP response with an XML document. These Rest style web services are deployed on existing infrastructure such as Apache and IIS web servers with no SOAP stack required. Unfortunately from a security standpoint, there frequently is no interoperable identity security mechanism deployed, so Rest developers often fall back to SSL to deliver security. In large data centers, SSL is typically terminated at the edge of the network - at the firewall, load balancer, or router. Once the SSL is terminated the HTTP request is in the clear (unless developers have hashed or encrypted the values, but this is rare). The attacker can utilize a sniffer such as Wireshark to snapshot the credentials, such as username and password that are passed in the clear once SSL is terminated. Once the attacker gathers these credentials, they can submit requests to the web service provider just as authorized user do. There is not typically an authentication on the client side, beyond what is passed in the request itself so once this is compromised, then this is generally sufficient to compromise the service's authentication scheme.
  • Man in the Middle Attack
    This type of attack targets the communication between two components (typically client and server). The attacker places himself in the communication channel between the two components. Whenever one component attempts to communicate with the other (data flow, authentication challenges, etc.), the data first goes to the attacker, who has the opportunity to observe or alter it, and it is then passed on to the other component as if it was never intercepted. This interposition is transparent leaving the two compromised components unaware of the potential corruption or leakage of their communications. The potential for Man-in-the-Middle attacks yields an implicit lack of trust in communication or identify between two components.
Access
VectorComplexityAuthentication
NETWORK MEDIUM NONE
Impact
ConfidentialityIntegrityAvailability
COMPLETE COMPLETE COMPLETE
nessus via4
NASL family Windows
NASL id CISCO_SECURE_ACS_FOR_WINDOWS_SA20130828.NASL
description The version of Cisco Secure Access Control Server for Windows 4.x is earlier than 4.2.1.15.11. It is, therefore, potentially affected by a remote code execution vulnerability. Due to improper parsing of user identities used for EAP-FAST authentication, a remote, unauthenticated attacker could execute arbitrary code on the remote host subject to the privileges of the user running the affected application. Note that this issue only affects Cisco Secure Access Control Server for Windows when configured as a RADIUS server.
last seen 2019-02-21
modified 2018-11-15
plugin id 69926
published 2013-09-17
reporter Tenable
source https://www.tenable.com/plugins/index.php?view=single&id=69926
title Cisco Secure Access Control Server for Windows Remote Code Execution
refmap via4
cisco 20130828 Cisco Secure Access Control Server Remote Command Execution Vulnerability
osvdb 96668
sectrack 1028958
the hacker news via4
id THN:78659A9AB6A66CCC0F6AB636A783E118
last seen 2017-01-08
modified 2013-08-30
published 2013-08-30
reporter Mohit Kumar
source http://thehackernews.com/2013/08/cisco-vulnerability-allows-remote.html
title CISCO vulnerability allows remote attacker to take control of Windows system
Last major update 07-11-2016 - 09:59
Published 29-08-2013 - 08:07
Back to Top