CVE-2019-3461
Published: 4 February 2019
Debian tmpreaper version 1.6.13+nmu1 has a race condition when doing a (bind) mount via rename() which could result in local privilege escalation. Mounting via rename() could potentially lead to a file being placed elsewhereon the filesystem hierarchy (e.g. /etc/cron.d/) if the directory being cleaned up was on the same physical filesystem. Fixed versions include 1.6.13+nmu1+deb9u1 and 1.6.14.
Notes
Author | Note |
---|---|
ebarretto | Version on trusty needs the fix, but the fix depends on bind mounts from util-linux package. And the util-linux in trusty doesn't contain that feature. We could use another solution but I am not sure how this might affect the race condition. |
Priority
Status
Package | Release | Status |
---|---|---|
tmpreaper Launchpad, Ubuntu, Debian |
bionic |
Released
(1.6.13+nmu1+deb9u1build0.18.04.1)
|
cosmic |
Ignored
(end of life)
|
|
disco |
Not vulnerable
(1.6.14)
|
|
eoan |
Not vulnerable
(1.6.14)
|
|
impish |
Not vulnerable
(1.6.14)
|
|
groovy |
Not vulnerable
(1.6.14)
|
|
hirsute |
Not vulnerable
(1.6.14)
|
|
jammy |
Not vulnerable
(1.6.14)
|
|
kinetic |
Not vulnerable
(1.6.14)
|
|
lunar |
Not vulnerable
(1.6.14)
|
|
focal |
Not vulnerable
(1.6.14)
|
|
trusty |
Needed
|
|
upstream |
Released
(1.6.14)
|
|
xenial |
Released
(1.6.13+nmu1+deb9u1build0.16.04.1)
|
|
mantic |
Not vulnerable
(1.6.14)
|
Severity score breakdown
Parameter | Value |
---|---|
Base score | 7.0 |
Attack vector | Local |
Attack complexity | High |
Privileges required | Low |
User interaction | None |
Scope | Unchanged |
Confidentiality | High |
Integrity impact | High |
Availability impact | High |
Vector | CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |