CVE-2019-8337 json
In msmtp 1.8.2 and mpop 1.4.3, when tls_trust_file has its default configuration, certificate-verification results are not properly checked.
published 7y ago modified 4mo ago also EUVD-2019-17727
- cvss
- 5.3
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 60%
- public exploits
- 0
- none known
Summary
In msmtp 1.8.2 and mpop 1.4.3, when tls_trust_file has its default configuration, certificate-verification results are not properly checked.
Patch / fix
- mpop Debian 14, Debian 13, Debian 12 1.4.3-1
- msmtp Debian 14, Debian 13, Debian 12 1.8.3-1
debian advisories DEBIAN-CVE-2019-8337
- mpop Ubuntu 20.04 LTS 1.4.3-1
ubuntu advisories UBUNTU-CVE-2019-8337
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- mstmp openSUSE Tumbleweed 1.8.16-1.1
opensuse advisories openSUSE-SU-2024:11064-1
- msmtp Arch Linux 1.8.3-1
arch linux advisories AVG-905
- gitlab.marlam.de/marlam/mpop@b51a6c6 commit
- marlam.de/mpop/news/mpop-1-4-3/ advisory
- marlam.de/msmtp/news/ advisory
Is CVE-2019-8337 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.92% chance of exploitation in the next 30 days, higher than 60% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 5.3 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-295 Improper Certificate Validation
References
-
gitlab.marlam.de
/marlam/mpop/commit/b51a6c6b8b83bf0913cc52fa2ff64307e987a5b8
patch, third-party-advisory
-
marlam.de
/mpop/news/mpop-1-4-3/
patch, third-party-advisory
-
marlam.de
/msmtp/news/
patch, vendor-advisory
Sources
- CVE List CVE-2019-8337
- NVD CVE-2019-8337
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.