CVE Vulnerabilities

CVE-2019-5603

Improper Resource Shutdown or Release

Published: Jul 26, 2019 | Modified: Mar 01, 2023
CVSS 3.x
7.8
HIGH
Source:
NVD
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS 2.x
7.2 HIGH
AV:L/AC:L/Au:N/C:C/I:C/A:C
RedHat/V2
RedHat/V3
Ubuntu

In FreeBSD 12.0-STABLE before r350261, 12.0-RELEASE before 12.0-RELEASE-p8, 11.3-STABLE before r350263, 11.3-RELEASE before 11.3-RELEASE-p1, and 11.2-RELEASE before 11.2-RELEASE-p12, system calls operating on file descriptors as part of mqueuefs did not properly release the reference allowing a malicious user to overflow the counter allowing access to files, directories, and sockets opened by processes owned by other users.

Weakness

The product does not release or incorrectly releases a resource before it is made available for re-use.

Affected Software

Name Vendor Start Version End Version
Freebsd Freebsd 11.0 (including) 11.0 (including)
Freebsd Freebsd 11.2 (including) 11.2 (including)
Freebsd Freebsd 11.2-p10 (including) 11.2-p10 (including)
Freebsd Freebsd 11.2-p11 (including) 11.2-p11 (including)
Freebsd Freebsd 11.2-p2 (including) 11.2-p2 (including)
Freebsd Freebsd 11.2-p3 (including) 11.2-p3 (including)
Freebsd Freebsd 11.2-p4 (including) 11.2-p4 (including)
Freebsd Freebsd 11.2-p5 (including) 11.2-p5 (including)
Freebsd Freebsd 11.2-p6 (including) 11.2-p6 (including)
Freebsd Freebsd 11.2-p7 (including) 11.2-p7 (including)
Freebsd Freebsd 11.2-p8 (including) 11.2-p8 (including)
Freebsd Freebsd 11.2-p9 (including) 11.2-p9 (including)
Freebsd Freebsd 11.2-rc3 (including) 11.2-rc3 (including)
Freebsd Freebsd 11.3 (including) 11.3 (including)
Freebsd Freebsd 12.0 (including) 12.0 (including)
Freebsd Freebsd 12.0-p1 (including) 12.0-p1 (including)
Freebsd Freebsd 12.0-p2 (including) 12.0-p2 (including)
Freebsd Freebsd 12.0-p3 (including) 12.0-p3 (including)
Freebsd Freebsd 12.0-p4 (including) 12.0-p4 (including)
Freebsd Freebsd 12.0-p5 (including) 12.0-p5 (including)
Freebsd Freebsd 12.0-p6 (including) 12.0-p6 (including)
Freebsd Freebsd 12.0-p7 (including) 12.0-p7 (including)

Potential Mitigations

  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
  • For example, languages such as Java, Ruby, and Lisp perform automatic garbage collection that releases memory for objects that have been deallocated.

References