First published: Thu Mar 25 2021(Updated: )
In Apache SpamAssassin before 3.4.5, malicious rule configuration (.cf) files can be configured to run system commands without any output or errors. With this, exploits can be injected in a number of scenarios. In addition to upgrading to SA version 3.4.5, users should only use update channels or 3rd party .cf files from trusted places.
Credit: security@apache.org
Affected Software | Affected Version | How to fix |
---|---|---|
debian/spamassassin | 3.4.2-1+deb10u3 3.4.6-1 4.0.0-6 4.0.0-7 | |
debian/spamassassin | <=3.4.2-1<=3.4.2-1+deb10u2 | 4.0.0~0.0svn1879217-1 3.4.5~pre1-1 3.4.2-1+deb10u3 |
Apache SpamAssassin | <3.4.5 | |
Debian | =9.0 | |
Debian | =10.0 | |
Fedora | =32 | |
Fedora | =33 | |
Fedora | =34 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2020-1946 is considered high due to the potential for system command execution without visible output.
To fix CVE-2020-1946, upgrade Apache SpamAssassin to version 3.4.5 or later.
CVE-2020-1946 affects Apache SpamAssassin versions prior to 3.4.5.
CVE-2020-1946 introduces the risk of exploits through malicious rule configuration files that can execute system commands.
Yes, Debian and Fedora distributions are affected by CVE-2020-1946 if they use vulnerable versions of Apache SpamAssassin.