Cisco fixed a vulnerability in the DNS-based Authentication of Named Entities (DANE) email verification component of its AsyncOS Software for Email Security Appliance (ESA) that could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition on an affected device.

This vulnerability is due to insufficient error handling in DNS name resolution by the affected software.

An attacker could exploit this vulnerability by sending specially formatted email messages that are processed by an affected device.

A successful exploit could allow the attacker to cause the device to become unreachable from management interfaces or to process additional email messages for a period of time until the device recovers, resulting in a DoS condition. Continued attacks could cause the device to become completely unavailable, resulting in a persistent DoS condition.

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

Schneider Bold

This vulnerability affects Cisco ESA devices if they are running a vulnerable release of Cisco AsyncOS Software with the DANE feature enabled and with the downstream mail servers configured to send bounce messages. The DANE feature is not enabled by default.

Cisco Cloud Email Security includes Cisco ESA and Cisco Secure Email and Web Manager, formerly Cisco Security Management Appliance (SMA), as part of the service solution. Cisco provides regular maintenance of the products included in this solution. Customers can also request a software upgrade by contacting Cisco Cloud Email Security support.

To determine whether DANE is configured, check the web UI page Mail Policies > Destination Controls > Add Destination and verify whether the DANE Support option is enabled.

In a workaround, users may configure bounce messages from Cisco ESA instead of from downstream dependent mail servers to prevent exploitation of this vulnerability. While this workaround has been deployed and was proven successful in a test environment, users 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.

There were other high rated vulnerabilities, including:

Click here for more notices on the Cisco Advisory Page.

Pin It on Pinterest

Share This