CVE-2019-19920
Published: 22 December 2019
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.
Priority
Status
Package | Release | Status |
---|---|---|
sa-exim Launchpad, Ubuntu, Debian |
bionic |
Needs triage
|
disco |
Ignored
(end of life)
|
|
eoan |
Ignored
(end of life)
|
|
focal |
Not vulnerable
(4.2.1-19)
|
|
groovy |
Not vulnerable
(4.2.1-19)
|
|
hirsute |
Not vulnerable
(4.2.1-19)
|
|
impish |
Not vulnerable
(4.2.1-19)
|
|
jammy |
Not vulnerable
(4.2.1-19)
|
|
kinetic |
Not vulnerable
(4.2.1-19)
|
|
lunar |
Not vulnerable
(4.2.1-19)
|
|
mantic |
Not vulnerable
(4.2.1-19)
|
|
trusty |
Does not exist
|
|
upstream |
Needs triage
|
|
xenial |
Released
(4.2.1-14+deb8u1build0.16.04.1)
|
Severity score breakdown
Parameter | Value |
---|---|
Base score | 8.8 |
Attack vector | Network |
Attack complexity | Low |
Privileges required | Low |
User interaction | None |
Scope | Unchanged |
Confidentiality | High |
Integrity impact | High |
Availability impact | High |
Vector | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |