VDB

CVE-2020-28896

CVE-2020-28896 PUBLISHED

Reported by mitre · Published November 23, 2020

Mutt before 2.0.2 and NeoMutt before 2020-11-20 did not ensure that $ssl_force_tls was processed if an IMAP server's initial server response was invalid. The connection was not properly closed, and the code could continue attempting to authenticate. This could result in authentication credentials being exposed on an unencrypted connection, or to a machine-in-the-middle.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
muttAlpine2.0.2-r0
neomuttArch Linux20201120-1
neomuttneomutt2020-11-20

Affected products

VendorProductVersions
n/an/an/a
alpinemutt0
archneomutt0
n/an/a*
archmutt0
amazon:2mutt0

Timeline

  • Nov 23, 2020 CVE Published
  • Apr 14, 2021 EPSS Score (30 in total, the first dated here)
  • Aug 4, 2024 CVE Updated
  • Mar 6, 2026 Distribution Patch (3 in total, the first dated here)
  • Mar 6, 2026 Security Advisory (10 in total, the first dated here)
  • Aug 31, 2026 Coalition ESS Score

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2020-28896
vulnetix vdb fixes CVE-2020-28896

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2020-28896/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›