CVE-2020-28019

CVE-2020-28019 is a high-severity vulnerability in Exim with a CVSS 3.x base score of 7.5. Its EPSS exploit-prediction score of 61% places it in the 99th percentile, indicating an elevated likelihood of exploitation. The underlying weakness is classified as CWE-665.

Key facts

Description

Exim 4 before 4.94.2 has Improper Initialization that can lead to recursion-based stack consumption or other consequences. This occurs because use of certain getc functions is mishandled when a client uses BDAT instead of DATA.

Frequently asked questions

What is CVE-2020-28019?
Exim 4 before 4.94.2 has Improper Initialization that can lead to recursion-based stack consumption or other consequences. This occurs because use of certain getc functions is mishandled when a client uses BDAT instead of DATA.
How severe is CVE-2020-28019?
CVE-2020-28019 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
Is CVE-2020-28019 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 61% (99th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2020-28019?
CVE-2020-28019 affects Exim. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2020-28019?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2020-28019 published?
CVE-2020-28019 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-665 (Improper Initialization) vulnerabilities

Browse all CWE-665 (Improper Initialization) vulnerabilities →

Threat intelligence

Threat-intel indicators referencing this CVE: