CVE-2020-28020

CVE-2020-28020 is a critical-severity vulnerability in Exim with a CVSS 3.x base score of 9.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-190.

Key facts

Description

Exim 4 before 4.92 allows Integer Overflow to Buffer Overflow, in which an unauthenticated remote attacker can execute arbitrary code by leveraging the mishandling of continuation lines during header-length restriction.

Frequently asked questions

What is CVE-2020-28020?
Exim 4 before 4.92 allows Integer Overflow to Buffer Overflow, in which an unauthenticated remote attacker can execute arbitrary code by leveraging the mishandling of continuation lines during header-length restriction.
How severe is CVE-2020-28020?
CVE-2020-28020 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2020-28020 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 8% (94th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2020-28020?
CVE-2020-28020 affects Exim. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2020-28020?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2020-28020 published?
CVE-2020-28020 was published on 2021-05-06 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Exim

All CVEs affecting Exim →

Other CWE-190 (Integer Overflow or Wraparound) vulnerabilities

Browse all CWE-190 (Integer Overflow or Wraparound) vulnerabilities →

Threat intelligence

Threat-intel indicators referencing this CVE: