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.
The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.
Link | Tags |
---|---|
https://lists.debian.org/debian-lts-announce/2019/01/msg00017.html | mailing list vendor advisory |
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918956 | mailing list vendor advisory |
https://lists.debian.org/debian-security-announce/2019/msg00003.html | mailing list vendor advisory |
https://usn.ubuntu.com/4077-1/ | vendor advisory |