CVE-2019-19920

NameCVE-2019-19920
Descriptionsa-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.
SourceCVE (at NVD; CERT, LWN, oss-sec, fulldisc, bugtraq, EDB, Metasploit, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, Mageia, GitHub code/issues, web search, more)
ReferencesDLA-2062-1
NVD severityhigh
Debian Bugs947198

Vulnerable and fixed packages

The table below lists information on source packages.

Source PackageReleaseVersionStatus
sa-exim (PTS)jessie4.2.1-14vulnerable
jessie (security)4.2.1-14+deb8u1fixed
stretch4.2.1-16vulnerable
buster4.2.1-17vulnerable
sid4.2.1-18vulnerable

The information below is based on the following data on fixed versions.

PackageTypeReleaseFixed VersionUrgencyOriginDebian Bugs
sa-eximsource(unstable)(unfixed)947198
sa-eximsourcejessie4.2.1-14+deb8u1DLA-2062-1

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

Search for package or bug name: Reporting problems