UBUNTU-CVE-2019-19920

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.

References

Affected packages

Ubuntu:16.04:LTS / sa-exim

Package

Name: sa-exim
Purl: pkg:deb/ubuntu/sa-exim@4.2.1-14+deb8u1build0.16.04.1?arch=source&distro=xenial

Affected ranges

Type: ECOSYSTEM
Events: Introduced

0Unknown introduced version / All previous versions are affected

Fixed

4.2.1-14+deb8u1build0.16.04.1

Affected versions

4.*

4.2.1-14build1

Ecosystem specific

{
    "availability": "No subscription required",
    "binaries": [
        {
            "binary_name": "sa-exim",
            "binary_version": "4.2.1-14+deb8u1build0.16.04.1"
        }
    ]
}

Ubuntu:Pro:18.04:LTS / sa-exim

Package

Name: sa-exim
Purl: pkg:deb/ubuntu/sa-exim@4.2.1-16?arch=source&distro=esm-apps/bionic

Affected ranges

Type: ECOSYSTEM
Events: Introduced

0Unknown introduced version / All previous versions are affected

Affected versions

4.*

4.2.1-16

Ubuntu:20.04:LTS / sa-exim

Package

Name: sa-exim
Purl: pkg:deb/ubuntu/sa-exim@4.2.1-19?arch=source&distro=focal

Affected ranges

Type: ECOSYSTEM
Events: Introduced

0Unknown introduced version / All previous versions are affected

Fixed

4.2.1-19

Affected versions

4.*

4.2.1-17

4.2.1-18

4.2.1-18build1

Ecosystem specific

{
    "availability": "No subscription required",
    "binaries": [
        {
            "binary_name": "sa-exim",
            "binary_version": "4.2.1-19"
        },
        {
            "binary_name": "sa-exim-dbgsym",
            "binary_version": "4.2.1-19"
        }
    ]
}