Cisco has a workaround and is working on a fix for a vulnerability in the interprocess communication (IPC) channel of its AnyConnect Secure Mobility Client Software that could allow an authenticated, local attacker to cause a targeted AnyConnect user to execute a malicious script.

The high-severity labeled vulnerability is due to a lack of authentication to the IPC listener. An attacker could exploit this vulnerability by sending crafted IPC messages to the AnyConnect client IPC listener. A successful exploit could allow an attacker to cause the targeted AnyConnect user to execute a script. This script would execute with the privileges of the targeted AnyConnect user.

However, to successfully exploit this vulnerability, an attacker would need all of the following:

  1. Valid user credentials on the system on which the AnyConnect client is being run by the targeted user
  2. To be able to log in to that system while the targeted user either has an active AnyConnect session established or establishes a new AnyConnect session
  3. To be able to execute code on that system

Cisco has not released software updates that address this vulnerability, however, there are workarounds that address this vulnerability, according to an advisory.

This vulnerability affects all versions of the Cisco AnyConnect Secure Mobility Client Software for the following platforms if they have a vulnerable configuration:

Schneider Bold
  • AnyConnect Secure Mobility Client for Windows
  • AnyConnect Secure Mobility Client for MacOS
  • AnyConnect Secure Mobility Client for Linux

The following configuration settings are in the AnyConnectLocalPolicy.xml file. The AnyConnectLocalPolicy.xml file is in the following locations:
Windows::\ProgramData\Cisco\Cisco AnyConnect Secure Mobility Client\
macOS: /opt/cisco/anyconnect/
Linux: /opt/cisco/anyconnect/

This vulnerability affects all versions of the Cisco AnyConnect Secure Mobility Client Software 4.9.04053 and later if RestrictScriptWebDeploy is set to the default value of false.

To verify the RestrictScriptWebDeploy configuration setting on a VPN client system, open the AnyConnectLocalPolicy.xml file and look for the following line: false

If RestrictScriptWebDeploy is set to false, the RestrictScriptWebDeploy is disabled and the device is affected by this vulnerability. If RestrictScriptWebDeploy is set to true, the RestrictScriptWebDeploy is enabled and the device is not affected by this vulnerability.

In addition, this vulnerability affects all versions of the Cisco AnyConnect Secure Mobility Client Software earlier than 4.9.04053 if BypassDownloader is set to the default value of false.

To verify the BypassDownloader configuration setting on a VPN client system, open the AnyConnectLocalPolicy.xml file and look for the following line: false

If Bypass Downloader is set to false, the BypassDownloader is disabled and the device is affected by this vulnerability. If BypassDownloader is set to true, the BypassDownloader is enabled and the device is not affected by this vulnerability.

Users should note by setting the BypassDownloader to true is not a recommended configuration.

Details about the vulnerability are as follows:

  • This vulnerability is not exploitable on laptops used by a single user, but instead requires valid logins for multiple users on the end-user device.
  • This vulnerability is not remotely exploitable, as it requires local credentials on the end-user device for the attacker to take action on the local system.
  • This vulnerability is not a privilege elevation exploit. The scripts run at the user level by default. If the local AnyConnect user manually raises the privilege of the User Interface process, the scripts would run at elevated privileges.
  • This vulnerability’s CVSS score is high (7.3) because, for configurations where the vulnerability is exploitable, it allows one user access to another user’s data and execution space.

The recommended workaround is to upgrade to Release 4.9.04053 and edit the AnyConnectLocalPolicy.xml file to set RestrictScriptWebDeploy to true. Ensure that BypassDownloader is set to false. The new AnyConnectLocalPolicy.xml file would then end up deployed to end machines using an out-of-band method of deployment.

Pin It on Pinterest

Share This