ID CVE-2020-1930
Summary A command execution issue was found in Apache SpamAssassin prior to 3.4.3. Carefully crafted nefarious rule configuration (.cf) files can be configured to run system commands similar to CVE-2018-11805. With this bug unpatched, exploits can be injected in a number of scenarios including the same privileges as spamd is run which may be elevated though doing so remotely is difficult. In addition to upgrading to SA 3.4.4, we again recommend that users should only use update channels or 3rd party .cf files from trusted places. If you cannot upgrade, do not use 3rd party rulesets, do not use sa-compile and do not run spamd as an account with elevated privileges.
References
Vulnerable Configurations
  • cpe:2.3:a:apache:spamassassin:-:*:*:*:*:*:*:*
    cpe:2.3:a:apache:spamassassin:-:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:spamassassin:3.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:apache:spamassassin:3.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:spamassassin:3.0.2:*:*:*:*:*:*:*
    cpe:2.3:a:apache:spamassassin:3.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:spamassassin:3.0.3:*:*:*:*:*:*:*
    cpe:2.3:a:apache:spamassassin:3.0.3:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:spamassassin:3.0.4:*:*:*:*:*:*:*
    cpe:2.3:a:apache:spamassassin:3.0.4:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:spamassassin:3.0.6:*:*:*:*:*:*:*
    cpe:2.3:a:apache:spamassassin:3.0.6:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:spamassassin:3.1.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:spamassassin:3.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:spamassassin:3.1.1:*:*:*:*:*:*:*
    cpe:2.3:a:apache:spamassassin:3.1.1:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:spamassassin:3.1.2:*:*:*:*:*:*:*
    cpe:2.3:a:apache:spamassassin:3.1.2:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:spamassassin:3.1.3:*:*:*:*:*:*:*
    cpe:2.3:a:apache:spamassassin:3.1.3:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:spamassassin:3.1.4:*:*:*:*:*:*:*
    cpe:2.3:a:apache:spamassassin:3.1.4:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:spamassassin:3.1.5:*:*:*:*:*:*:*
    cpe:2.3:a:apache:spamassassin:3.1.5:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:spamassassin:3.1.6:*:*:*:*:*:*:*
    cpe:2.3:a:apache:spamassassin:3.1.6:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:spamassassin:3.1.7:*:*:*:*:*:*:*
    cpe:2.3:a:apache:spamassassin:3.1.7:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:spamassassin:3.1.8:*:*:*:*:*:*:*
    cpe:2.3:a:apache:spamassassin:3.1.8:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:spamassassin:3.2.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:spamassassin:3.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:spamassassin:3.2.1:*:*:*:*:*:*:*
    cpe:2.3:a:apache:spamassassin:3.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:spamassassin:3.2.2:*:*:*:*:*:*:*
    cpe:2.3:a:apache:spamassassin:3.2.2:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:spamassassin:3.2.3:*:*:*:*:*:*:*
    cpe:2.3:a:apache:spamassassin:3.2.3:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:spamassassin:3.2.4:*:*:*:*:*:*:*
    cpe:2.3:a:apache:spamassassin:3.2.4:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:spamassassin:3.2.5:*:*:*:*:*:*:*
    cpe:2.3:a:apache:spamassassin:3.2.5:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:spamassassin:3.3.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:spamassassin:3.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:spamassassin:3.3.1:*:*:*:*:*:*:*
    cpe:2.3:a:apache:spamassassin:3.3.1:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:spamassassin:3.3.2:*:*:*:*:*:*:*
    cpe:2.3:a:apache:spamassassin:3.3.2:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:spamassassin:3.4.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:spamassassin:3.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:spamassassin:3.4.1:*:*:*:*:*:*:*
    cpe:2.3:a:apache:spamassassin:3.4.1:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:spamassassin:3.4.2:*:*:*:*:*:*:*
    cpe:2.3:a:apache:spamassassin:3.4.2:*:*:*:*:*:*:*
CVSS
Base: 9.3 (as of 02-02-2020 - 04:15)
Impact:
Exploitability:
CWE CWE-78
CAPEC
  • OS Command Injection
    In this type of an attack, an adversary injects operating system commands into existing application functions. An application that uses untrusted input to build command strings is vulnerable. An adversary can leverage OS command injection in an application to elevate privileges, execute arbitrary commands and compromise the underlying operating system.
  • Argument Injection
    An attacker changes the behavior or state of a targeted application through injecting data or command syntax through the targets use of non-validated and non-filtered arguments of exposed services or methods.
  • Command Delimiters
    An attack of this type exploits a programs' vulnerabilities that allows an attacker's commands to be concatenated onto a legitimate command with the intent of targeting other resources such as the file system or database. The system that uses a filter or a blacklist input validation, as opposed to whitelist validation is vulnerable to an attacker who predicts delimiters (or combinations of delimiters) not present in the filter or blacklist. As with other injection attacks, the attacker uses the command delimiter payload as an entry point to tunnel through the application and activate additional attacks through SQL queries, shell commands, network scanning, and so on.
  • Command Line Execution through SQL Injection
    An attacker uses standard SQL injection methods to inject data into the command line for execution. This could be done directly through misuse of directives such as MSSQL_xp_cmdshell or indirectly through injection of data into the database that would be interpreted as shell commands. Sometime later, an unscrupulous backend application (or could be part of the functionality of the same application) fetches the injected data stored in the database and uses this data as command line arguments without performing proper validation. The malicious data escapes that data plane by spawning new commands to be executed on the host.
  • Exploiting Multiple Input Interpretation Layers
    An attacker supplies the target software with input data that contains sequences of special characters designed to bypass input validation logic. This exploit relies on the target making multiples passes over the input data and processing a "layer" of special characters with each pass. In this manner, the attacker can disguise input that would otherwise be rejected as invalid by concealing it with layers of special/escape characters that are stripped off by subsequent processing steps. The goal is to first discover cases where the input validation layer executes before one or more parsing layers. That is, user input may go through the following logic in an application: <parser1> --> <input validator> --> <parser2>. In such cases, the attacker will need to provide input that will pass through the input validator, but after passing through parser2, will be converted into something that the input validator was supposed to stop.
Access
VectorComplexityAuthentication
NETWORK MEDIUM NONE
Impact
ConfidentialityIntegrityAvailability
COMPLETE COMPLETE COMPLETE
cvss-vector via4 AV:N/AC:M/Au:N/C:C/I:C/A:C
redhat via4
rpms
  • spamassassin-0:3.4.2-10.el8
  • spamassassin-debuginfo-0:3.4.2-10.el8
  • spamassassin-debugsource-0:3.4.2-10.el8
refmap via4
bugtraq 20200203 [SECURITY] [DSA 4615-1] spamassassin security update
confirm https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7648
debian DSA-4615
fedora
  • FEDORA-2020-24dac7d890
  • FEDORA-2020-bd20036cdc
mlist
  • [announce] 20200130 [CVE-2020-1930] Apache SpamAssassin Nefarious rule configuration (.cf) files can be configured to run system commands
  • [debian-lts-announce] 20200218 [SECURITY] [DLA 2107-1] spamassassin security update
suse openSUSE-SU-2020:0446
ubuntu
  • USN-4265-1
  • USN-4265-2
Last major update 02-02-2020 - 04:15
Published 30-01-2020 - 18:15
Last modified 02-02-2020 - 04:15
Back to Top