CVE-2020-3548 is a medium severity (CVSS 5.3) denial of service flaw in the TLS handling of Cisco AsyncOS for Email Security Appliance. An unauthenticated remote attacker can drive CPU use high and slow the device. Cisco lists release 13.5.1-277 and earlier as affected and has no workaround, so check the advisory bug for fixed releases.
What's affected
- Cisco AsyncOS for Email Security Appliance, release 13.5.1-277 and earlier, per the advisory.
- Fixed release: the advisory page I fetched does not name one and points to bug ID CSCvu35999 for details. Confirm the fixed release there.
- No workarounds exist.
The record scores it 5.3 (Medium) with vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L. The record does not flag it as a CISA Known Exploited Vulnerability, and none of the pages I read report exploitation in the wild.
How to check if you're exposed
On the appliance, run the version command at the CLI or open the System Administration page and read the AsyncOS release. Compare it with Cisco's fixed release for your train, which is listed under the bug ID in the advisory.
What to do now
- Inventory every ESA, virtual and hardware.
- Read the AsyncOS release on each one.
- Open bug CSCvu35999 through Cisco's bug search and note the first fixed release for your train.
- Schedule an upgrade to that release or later.
- Watch CPU graphs on mail gateways for sustained spikes during TLS heavy periods while you wait.
After you patch, record the new version for Cisco ESA AsyncOS in your asset inventory, and confirm it with the same check you used above. A fix that was never verified is easy to forget, and an inventory that shows versions is what lets you answer the next advisory in minutes instead of days.
Why it matters
The weakness is CWE-407, inefficient algorithmic complexity. The TLS code does more work than it should for certain incoming packets, so a series of crafted packets keeps the CPU busy. The device keeps working, but response time and performance drop.
For a mail gateway that is a real operational risk. Delayed mail, slow scanning and queue growth all follow from a pegged CPU, and the attacker needs no account. The score stays moderate because there is no data loss or code execution.
To check open source components in your own projects for known CVEs like this one, try the free in-browser dependency scan at gold.safeguard.sh/scan, or look the CVE up in the Gold directory.
Quick check
Does the device stop working?
The record says the affected device would still be operative, but response time and overall performance may be degraded. It is a slowdown, not a crash.
How do I find every place Cisco ESA AsyncOS is used?
Start with an inventory of installed software and versions, because you cannot patch what you have not found. Check servers, build hosts, test copies and anything a vendor bundles. For open source libraries, a dependency scan or SBOM gives the same list for your code.
Sources
Last reviewed: 19 October 2026.