LiveActive security incident?Get immediate response
CVE Record

CVE-2020-28009: Exim 4 before 4.94.2 allows Integer Overflow to Buffer Overflow because get_stdinput allows unbounded reads...

Exim 4 before 4.94.2 allows Integer Overflow to Buffer Overflow because get_stdinput allows unbounded reads that are accompanied by unbounded increases in a certain size variable. NOTE: exploitation may be impractical because of the execution time needed to overflow (multiple days).

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2020-28009 is a flaw in Exim 4 before 4.94.2 where excessive standard input handling can turn an integer overflow into a buffer overflow. The source notes exploitation may be impractical because overflowing the counter could require multiple days.

Executive priority

Handle as a scheduled but real infrastructure remediation item. The flaw is memory-safety related in mail-server software, but available evidence points to difficult exploitation and no confirmed active exploitation.

Technical view

The issue is in Exim get_stdinput: unbounded reads are paired with unbounded growth of a size variable, creating an integer-overflow-to-buffer-overflow condition. The provided sources do not include CVSS, CWE, privilege context, or a confirmed exploitation chain.

Likely exposure

Exposure is limited to systems running Exim 4 before 4.94.2. Internet-facing mail servers deserve priority because Exim commonly processes untrusted mail traffic, but the provided source does not prove remote exploitability in practical conditions.

Exploitation context

CISA KEV is false in the bundle, and no cited source says this is actively exploited. The Exim note explicitly says exploitation may be impractical due to the time required to overflow the variable.

Researcher notes

Evidence is narrow: the bundle provides Exim’s STDIN advisory text and CVE metadata, but no CVSS, CWE, exploit telemetry, or detailed affected CPEs. Do not assume broader product impact beyond Exim 4 before 4.94.2.

Mitigation direction

  • Inventory Exim installations and identify versions before 4.94.2.
  • Upgrade affected Exim deployments to 4.94.2 or later.
  • Prioritize internet-facing mail infrastructure first.
  • Review Exim vendor guidance for any configuration-specific mitigations.
  • Track scanner findings until all vulnerable versions are removed.

Validation and detection

  • Confirm Exim version on each mail server.
  • Verify no production host runs Exim before 4.94.2.
  • Check vulnerability scanner results against the mail-server inventory.
  • Review change records confirming Exim upgrades completed.
  • Document any remaining exceptions with owner and deadline.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2020-28009 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.