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.
References
Link | Resource |
---|---|
https://lists.debian.org/debian-security-announce/2019/msg00003.html | Mailing List Vendor Advisory |
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918956 | Mailing List Vendor Advisory |
https://lists.debian.org/debian-lts-announce/2019/01/msg00017.html | Vendor Advisory |
https://usn.ubuntu.com/4077-1/ |
Information
Published : 2019-02-04 10:29
Updated : 2019-07-29 13:15
NVD link : CVE-2019-3461
Mitre link : CVE-2019-3461
JSON object : View
CWE
CWE-362
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
Products Affected
debian
- debian_linux
- tmpreaper