| Name | CVE-2019-19920 |
| Description | sa-exim 4.2.1 allows attackers to execute arbitrary code if they can write a .cf file or a rule. This occurs because Greylisting.pm relies on eval (rather than direct parsing and/or use of the taint feature). This issue is similar to CVE-2018-11805. |
| Source | CVE (at NVD; CERT, LWN, oss-sec, fulldisc, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more) |
| References | DLA-2062-1 |
| Debian Bugs | 947198 |
Vulnerable and fixed packages
The table below lists information on source packages.
| Source Package | Release | Version | Status |
|---|
| sa-exim (PTS) | sid, bookworm, bullseye | 4.2.1-20 | fixed |
The information below is based on the following data on fixed versions.
Notes
[buster] - sa-exim <no-dsa> (Minor issue; can be fixed via point release)
[stretch] - sa-exim <no-dsa> (Minor issue; can be fixed via point release)
https://bugs.debian.org/946829#24
https://marc.info/?l=spamassassin-users&m=157668107325768&w=2
https://marc.info/?l=spamassassin-users&m=157668305026635&w=2
The issue is "effectively" mitigating due to the CVE-2018-11805 fix in
spamassassin, making the Greylisting.pm non-functional (and so a functional
regression as well as tracked in #946829). The security implications are
as well documented in /usr/share/doc/sa-exim/README.greylisting.gz