CVE-2020-3132 json
Cisco Email Security Appliance Shortened URL Denial of Service Vulnerability
published 6y ago modified 4mo ago also EUVD-2020-24403
- cvss
- 6.8
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.5%
- EPSS 1.5% chance of exploitation in 30 days, percentile 74%
- public exploits
- 0
- none known
Summary
A vulnerability in the email message scanning feature of Cisco AsyncOS Software for Cisco Email Security Appliance (ESA) could allow an unauthenticated, remote attacker to cause a temporary denial of service (DoS) condition on an affected device. The vulnerability is due to inadequate parsing mechanisms for specific email body components. An attacker could exploit this vulnerability by sending a malicious email containing a high number of shortened URLs through an affected device. A successful exploit could allow the attacker to consume processing resources, causing a DoS condition on an affected device. To successfully exploit this vulnerability, certain conditions beyond the control of the attacker must occur.
Patch / fix
- cisco cloud_email_security 12.5.1-037, 13.0.0-375
- cisco email_security_appliance 12.5.1-037, 13.0.0-375
Is CVE-2020-3132 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
1.51% chance of exploitation in the next 30 days, higher than 74% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 6.8 | CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:N/A:H |
| NVD | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 7.1 | AV:N/AC:M/Au:N/C:N/I:N/A:C |
Affected products
- Cisco Cisco Email Security Appliance (ESA)
Classification
- Weakness
-
- CWE-400 Uncontrolled Resource Consumption
References
Sources
- CVE List CVE-2020-3132
- NVD CVE-2020-3132
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.