Progressive Robot Ltd hMailServer
Inefficient Algorithmic Complexity in hMailServer
Inefficient algorithmic complexity in the bounce and complaint processing of Progressive Robot hMailServer 6.3.4 and 6.3.5 allows a remote unauthenticated attacker to stop mail delivery by sending messages, when bounce processing or complaint processing is enabled or a mailing list is managed by the server (none is by default). The readers of incoming delivery status notifications (RFC 3464) and abuse feedback reports (RFC 5965) removed the blank lines at the start of the returned headers part two bytes at a time, copying the rest of the part each time, so their work grew with the square of the number of blank lines. A message shaped like such a report, whose headers part begins with a very large number of blank lines within the reader's 2 MB limit, keeps a delivery thread busy for over a minute while it is delivered, and a few such messages a minute keep every delivery thread busy.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 6.3.4, < 6.3.6
Fixed in 6.3.6
Mitigation
Upgrade to hMailServer 6.3.6, whose report readers cut the leading blank lines off once. Until then, turn bounce processing, complaint processing and list management off (the default).
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.