CVE Vulnerabilities

CVE-2019-10161

Improper Access Control

Published: Jul 30, 2019 | Modified: Nov 21, 2024
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
8.8 IMPORTANT
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Ubuntu
MEDIUM

It was discovered that libvirtd before versions 4.10.1 and 5.4.1 would permit read-only clients to use the virDomainSaveImageGetXMLDesc() API, specifying an arbitrary path which would be accessed with the permissions of the libvirtd process. An attacker with access to the libvirtd socket could use this to probe the existence of arbitrary files, cause denial of service or cause libvirtd to execute arbitrary programs.

Weakness

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

Affected Software

Name Vendor Start Version End Version
Libvirt Redhat * 4.10.1 (excluding)
Libvirt Redhat 5.0.0 (including) 5.4.1 (excluding)
Libvirt Ubuntu bionic *
Libvirt Ubuntu cosmic *
Libvirt Ubuntu devel *
Libvirt Ubuntu disco *
Libvirt Ubuntu eoan *
Libvirt Ubuntu focal *
Libvirt Ubuntu groovy *
Libvirt Ubuntu hirsute *
Libvirt Ubuntu precise/esm *
Libvirt Ubuntu trusty *
Libvirt Ubuntu trusty/esm *
Libvirt Ubuntu xenial *
Red Hat Enterprise Linux 6 RedHat libvirt-0:0.10.2-64.el6_10.2 *
Red Hat Enterprise Linux 7 RedHat libvirt-0:4.5.0-10.el7_6.12 *
Red Hat Enterprise Linux 8 RedHat virt:rhel-8000020190618154454.f8e95b4e *
Red Hat Enterprise Linux 8 Advanced Virtualization RedHat virt:8.0.0-8000020190620145550.f8e95b4e *
Red Hat Virtualization 4 for Red Hat Enterprise Linux 7 RedHat redhat-release-virtualization-host-0:4.3.4-1.el7ev *
Red Hat Virtualization 4 for Red Hat Enterprise Linux 7 RedHat redhat-virtualization-host-0:4.3.4-20190620.3.el7_6 *

Extended Description

Access control involves the use of several protection mechanisms such as:

When any mechanism is not applied or otherwise fails, attackers can compromise the security of the product by gaining privileges, reading sensitive information, executing commands, evading detection, etc. There are two distinct behaviors that can introduce access control weaknesses:

Potential Mitigations

  • Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
  • Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References