CVE-2019-3461

Publication date 4 February 2019

Last updated 24 July 2024

Ubuntu priority

Medium

Why this priority?

Cvss 3 Severity Score

7.0 · High

Score breakdown

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.

Read the notes from the security team

Status

Package Ubuntu Release Status
tmpreaper 24.10 oracular
Not affected
24.04 LTS noble
Not affected
23.10 mantic
Not affected
23.04 lunar
Not affected
22.10 kinetic
Not affected
22.04 LTS jammy
Not affected
21.10 impish
Not affected
21.04 hirsute
Not affected
20.10 groovy
Not affected
20.04 LTS focal
Not affected
19.10 eoan
Not affected
19.04 disco
Not affected
18.10 cosmic Ignored end of life
18.04 LTS bionic
Fixed 1.6.13+nmu1+deb9u1build0.18.04.1
16.04 LTS xenial
Fixed 1.6.13+nmu1+deb9u1build0.16.04.1
14.04 LTS trusty Ignored end of ESM support, was needed

Notes

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.

Severity score breakdown

Parameter Value
Base score 7.0 · High
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

References

Related Ubuntu Security Notices (USN)

Other references