In the critical issue, Cisco fixed a vulnerability in the single sign-on (SSO) implementation of Cisco BroadWorks Application Delivery Platform and Cisco BroadWorks Xtended Services Platform that could allow an unauthenticated, remote attacker to forge the credentials required to access an affected system. This vulnerability is due to the method used to validate SSO tokens.
An attacker could exploit this vulnerability by authenticating to the application with forged credentials. A successful exploit could allow the attacker to commit toll fraud or to execute commands at the privilege level of the forged account.
If that account is an Administrator account, the attacker would have the ability to view confidential information, modify customer settings, or modify settings for other users. To exploit this vulnerability, the attacker would need a valid user ID associated with an affected Cisco BroadWorks system.
Cisco released software updates that address this vulnerability, according to an advisory. There are no workarounds that address this vulnerability.
This vulnerability affects Cisco BroadWorks Application Delivery Platform and Cisco BroadWorks Xtended Services Platform if they are running a vulnerable release of Cisco BroadWorks and have one of the following applications enabled:
- AuthenticationService
- BWCallCenter
- BWReceptionist
- CustomMediaFilesRetrieval
- ModeratorClientApp
- PublicECLQuery
- PublicReporting
- UCAPI
- Xsi-Actions
- Xsi-Events
- Xsi-MMTel
- Xsi-VTR
In addition, Cisco cleared a high-rated vulnerability in the RADIUS message processing feature of Cisco Identity Services Engine (ISE) could allow an unauthenticated, remote attacker to cause the affected system to stop processing RADIUS packets.
This vulnerability is due to improper handling of certain RADIUS accounting requests. An attacker could exploit this vulnerability by sending a crafted authentication request to a network access device (NAD) that uses Cisco ISE for authentication, authorization, and accounting (AAA). This would eventually result in the NAD sending a RADIUS accounting request packet to Cisco ISE. An attacker could also exploit this vulnerability by sending a crafted RADIUS accounting request packet to Cisco ISE directly if the RADIUS shared secret ends up known.
A successful exploit could allow the attacker to cause the RADIUS process to unexpectedly restart, resulting in authentication or authorization timeouts and denying legitimate users access to the network or service. Clients already authenticated to the network would not be affected.
To recover the ability to process RADIUS packets, a manual restart of the affected Policy Service Node (PSN) may end up required.
Cisco released software updates that address this vulnerability, according to an advisory. There are no workarounds that address this vulnerability.
This vulnerability affects Cisco ISE PSNs configured with RADIUS. If Cisco ISE sees use for TACACS only, then the device does not suffer from the issue.
RADIUS comes enabled by default and cannot end up disabled. A user may need to configure the default RADIUS policies to deny access to all users and devices if Cisco ISE sees use for TACACS only.
For the exploit to be successful, attackers must have one of the following:
- Valid user credentials
- A NAD shared secret that can connect to Cisco ISE
- Access to a NAD that connects to a Cisco ISE deployment configured with MAC Authentication Bypass (MAB) so the authentication policy succeeds even if there is no user
To determine whether a node in the Cisco ISE deployment is a PSN, use the following steps:
- Log in to the Cisco ISE web-based management interface.
- Click the menu icon.
- Choose Administration > System > Deployment.
- Look at the Personas column in the table for the nodes in the deployment. If a node has Policy Service listed, the node suffers from this vulnerability. If Policy Service is not listed, the node is not vulnerable.
If a deployment ends up used for TACACS only and the RADIUS policy is at DenyAccess, the deployment is not vulnerable.
To determine whether a deployment has a DenyAccess RADIUS policy in effect, use the following steps:
- Log in to the Cisco ISE web-based management interface.
- Click the menu icon.
- Choose Policy > Policy Sets. If RADIUS never deployed, only the Default policy should be visible. If there is more than one policy listed, this deployment might be serving as a RADIUS server.
- Click the arrow to check the Default policy.
In the Authentication Policy section, verify the following:
— All rules end up disabled except the Default rule.
— Under Default > Options, all options are REJECT or DROP.
In the Authorization Policy – Local Exceptions section, verify disabled rules.
In the Authorization Policy – Global Exceptions section, verify all rules ended up disabled.
In the Authorization Policy section, verify the following:
— All rules ended up disabled except the Default rule.
— The Default rule’s profile is DenyAccess.

