{"id":"CVE-2019-3461","aliases":["DEBIAN-CVE-2019-3461","DLA-1640-1","DSA-4365-1","EUVD-2019-13100","GHSA-qwp6-cgv8-84vv","UBUNTU-CVE-2019-3461","USN-4077-1"],"status":"published","title":"Debian tmpreaper version 1.6.13+nmu1 has a race condition when doing a (bind) mount via rename()...","description":"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.","severity":{"version":"3.0","score":7,"vector":"CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-09","score":0.00253,"percentile":0.16843,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-362"],"published":"2019-01-10T00:00:00Z","modified":"2026-09-21T07:01:24Z","fixes":[{"ecosystem":"Debian:12","package":"tmpreaper","fixed_in":["1.6.14"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"tmpreaper","fixed_in":["1.6.14"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"tmpreaper","fixed_in":["1.6.14"],"sources":["osv"]},{"ecosystem":"Debian:8","package":"tmpreaper","fixed_in":["1.6.13+nmu1+deb8u1"],"sources":["osv"]},{"ecosystem":"Debian:9","package":"tmpreaper","fixed_in":["1.6.13+nmu1+deb9u1"],"sources":["osv"]},{"ecosystem":"Ubuntu:16.04:LTS","package":"tmpreaper","fixed_in":["1.6.13+nmu1+deb9u1build0.16.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:18.04:LTS","package":"tmpreaper","fixed_in":["1.6.13+nmu1+deb9u1build0.18.04.1"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Debian:12","package":"tmpreaper","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.6.14"}]}]},{"source":"osv","ecosystem":"Debian:13","package":"tmpreaper","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.6.14"}]}]},{"source":"osv","ecosystem":"Debian:14","package":"tmpreaper","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.6.14"}]}]},{"source":"osv","ecosystem":"Debian:8","package":"tmpreaper","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.6.13+nmu1+deb8u1"}]}],"versions":["1.6.13+nmu1"]},{"source":"osv","ecosystem":"Debian:9","package":"tmpreaper","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.6.13+nmu1+deb9u1"}]}],"versions":["1.6.13+nmu1"]},{"source":"osv","ecosystem":"Ubuntu:14.04:LTS","package":"tmpreaper","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.6.13+nmu1"]},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"tmpreaper","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.6.13+nmu1+deb9u1build0.16.04.1"}]}],"versions":["1.6.13+nmu1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"tmpreaper","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.6.13+nmu1+deb9u1build0.18.04.1"}]}],"versions":["1.6.13+nmu1","1.6.13+nmu1build1"]},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"tmpreaper","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.6.13+nmu1+deb9u1build0.16.04.1"}]}],"versions":["1.6.13+nmu1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"tmpreaper","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.6.13+nmu1+deb9u1build0.18.04.1"}]}],"versions":["1.6.13+nmu1","1.6.13+nmu1build1"]}],"products":[{"vendor":"debian","product":"debian_linux"},{"vendor":"debian","product":"tmpreaper"},{"vendor":"debian gnu/linux","product":"tmpreaper"}],"references":[{"url":"https://lists.debian.org/debian-lts-announce/2019/01/msg00017.html","tags":["mailing-list","x_refsource_MLIST","x_transferred","Vendor Advisory","advisory"]},{"url":"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918956","tags":["x_refsource_MISC","x_transferred","Mailing List","Vendor Advisory","advisory"]},{"url":"https://lists.debian.org/debian-security-announce/2019/msg00003.html","tags":["vendor-advisory","x_refsource_DEBIAN","x_transferred","Mailing List","Vendor Advisory","advisory"]},{"url":"https://usn.ubuntu.com/4077-1/","tags":["vendor-advisory","x_refsource_UBUNTU","x_transferred","web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2019-3461"},{"url":"https://github.com/advisories/GHSA-qwp6-cgv8-84vv"},{"url":"https://security-tracker.debian.org/tracker/CVE-2019-3461","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2019-3461","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-4077-1","tags":["advisory"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2019-3461","tags":["report"]}],"sources":{"cve":[{"id":"CVE-2019-3461","description":"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.","status":"published","published":"2019-02-04T18:00:00Z","modified":"2024-09-16T22:56:42.618Z","updated_at":"2026-11-02T14:20:23.048861Z"}],"euvd":[{"id":"EUVD-2019-13100","description":"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.","status":"published","published":"2019-02-04T18:00:00Z","modified":"2024-09-16T22:56:42Z","updated_at":"2026-11-03T00:54:58.273879Z"}],"ghsa":[{"id":"GHSA-qwp6-cgv8-84vv","title":"Debian tmpreaper version 1.6.13+nmu1 has a race condition when doing a (bind) mount via rename()...","description":"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.","status":"published","published":"2022-05-14T00:55:31Z","modified":"2023-02-02T05:02:35Z","cvss":[{"version":"3.0","score":7,"vector":"CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"cwes":["CWE-362"],"updated_at":"2026-11-02T14:51:28.259401Z"}],"nvd":[{"id":"CVE-2019-3461","description":"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.","status":"published","published":"2019-02-04T18:29:00.247Z","modified":"2026-06-17T02:35:09.55Z","cvss":[{"version":"3.0","score":7,"vector":"CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high","assessor":"primary"},{"version":"2.0","score":4.4,"vector":"AV:L/AC:M/Au:N/C:P/I:P/A:P","level":"medium","assessor":"primary"}],"cwes":["CWE-362"],"updated_at":"2026-11-02T14:05:02.989216Z"}],"osv":[{"id":"CVE-2019-3461","description":"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.","status":"published","published":"2019-02-04T18:29:00.247Z","modified":"2026-03-15T22:28:26.31922Z","cvss":[{"version":"3.0","score":7,"vector":"CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:44:12.363788Z"},{"id":"DEBIAN-CVE-2019-3461","description":"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.","status":"published","published":"2019-02-04T18:29:00.247Z","modified":"2026-09-21T07:01:24.331170556Z","cvss":[{"version":"3.0","score":7,"vector":"CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:45:32.221385Z"},{"id":"UBUNTU-CVE-2019-3461","description":"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.","status":"published","published":"2019-02-04T00:00:00Z","modified":"2026-02-04T03:30:23.889343Z","cvss":[{"version":"3.0","score":7,"vector":"CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:54:21.213407Z"},{"id":"DLA-1640-1","title":"tmpreaper - security update","status":"published","published":"2019-01-24T00:00:00Z","modified":"2026-03-09T01:23:15.945086Z","updated_at":"2026-11-02T15:46:09.777694Z"},{"id":"DSA-4365-1","title":"tmpreaper - security update","status":"published","published":"2019-01-10T00:00:00Z","modified":"2026-03-09T02:10:13.872749Z","updated_at":"2026-11-02T15:46:16.862196Z"},{"id":"USN-4077-1","title":"tmpreaper vulnerability","description":"It was discovered that tmpreaper incorrectly handled certain mount operations. A\nlocal attacker could possibly use this issue to create arbitrary files, leading\nto privilege escalation.\n","status":"published","published":"2019-07-29T15:55:31Z","modified":"2026-04-27T15:27:17.208967Z","updated_at":"2026-11-02T16:58:14.019824Z"}]}}