Cisco fixed a vulnerability rated high in the proxy service of Cisco AsyncOS for Cisco Web Security Appliance (WSA) that could allow an unauthenticated, remote attacker to exhaust system memory and cause a denial of service (DoS) condition on an affected device.

This is just one of five vulnerabilities Cisco released rated high and 10 others rated medium.

This vulnerability is due to improper memory management in the proxy service of an affected device. An attacker could exploit this vulnerability by establishing a large number of HTTPS connections to the affected device. A successful exploit could allow the attacker to cause the system to stop processing new connections, which could result in a DoS condition. Manual intervention may be required to recover from this situation.

CVE-2021-34698 is the case number for the vulnerability, which has a CVSS base score of 8.6.

Cisco released software updates that address this vulnerability, according to an advisory. In addition, there are workarounds that address this vulnerability.

Schneider Bold

This vulnerability affects Cisco AsyncOS for Cisco WSA, both virtual and hardware appliances.

Products affected, and updates, include:

  • Versions 11.5 and 11.8 are not affected
  • Version 12.0, update to 12.0.3-005
  • Version 12.5, update to 12.5.2-007
  • Version 14.0, update to 14.0.1-014

Indicators of compromise include: Use the grep CLI command and search in the proxylogs for the string Accept handlers have been Disabled. If any line shows up in the terminal, the proxy process may be saturated and a device reload may be required to recover the normal functions.

Alternatively, obtain the Proxy Track Stats logs from the Cisco WSA (through Secure Copy Protocol or FTP) and search for an INFO line like the one in this example: INFO: MALLOC’ed memory size 361150328 MMAP’ed memory 448790528. If the first number (361150328 in this case), keeps increasing up to the second number (448790528), the device memory allocation is approaching its limit, and a device reload is necessary.

There is a workaround that addresses this vulnerability. Customers can use the hidden diagnostic > PROXY > KICK command to restart the proxy process and reclaim memory.

While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Users should be aware any workaround or mitigation implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.

Click here for more information on all the other vulnerabilities.

Pin It on Pinterest

Share This