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.
ebarrettoVersion 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.
Upstream:released (1.6.14)
Ubuntu 12.04 ESM (Precise Pangolin):DNE
Ubuntu 14.04 ESM (Trusty Tahr):needed
Ubuntu 16.04 LTS (Xenial Xerus):released (1.6.13+nmu1+deb9u1build0.16.04.1)
Ubuntu 18.04 LTS (Bionic Beaver):released (1.6.13+nmu1+deb9u1build0.18.04.1)
Ubuntu 19.10 (Eoan Ermine):not-affected (1.6.14)
Ubuntu 20.04 (Focal Fossa):not-affected (1.6.14)
More Information

Updated: 2020-01-29 19:02:49 UTC (commit 40f18bf14da5fb50662e1f861ea594a462b207fe)