SB2018022033 - Ubuntu update for libvirt
Published: February 20, 2018 Updated: October 30, 2026
Breakdown by Severity
- Low
- Medium
- High
- Critical
Description
This security bulletin contains information about 4 vulnerabilities.
1) Improper Authentication (CVE-ID: CVE-2016-5008)
CWE-ID: CWE-287 - Improper Authentication
CVSSv4: 7.4 [CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N]
The vulnerability allows a remote attacker to bypass authentication process.
The vulnerability exists due to an error in when processing authentication requests. libvirt before 2.0.0 improperly disables password checking when the password on a VNC server is set to an empty string, which allows remote attackers to bypass authentication and establish a VNC session by connecting to the server.
2) Improper Certificate Validation (CVE-ID: CVE-2017-1000256)
CWE-ID: CWE-295 - Improper Certificate Validation
CVSSv4: 9.2 [CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N]
The vulnerability allows a remote non-authenticated attacker to execute arbitrary code.
libvirt version 2.3.0 and later is vulnerable to a bad default configuration of "verify-peer=no" passed to QEMU by libvirt resulting in a failure to validate SSL/TLS certificates by default.
3) Resource exhaustion (CVE-ID: CVE-2018-5748)
CWE-ID: CWE-400 - Resource exhaustion
CVSSv4: 8.7 [CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N]
The vulnerability allows a remote attacker to cause DoS condition on the target system.
The weakness exists due to a flaw in qemu/qemu_monitor.c in libvirt. A remote attacker can supply a large QEMU reply, trigger resource exhaustion and cause the service to crash.
4) Security restrictions bypass (CVE-ID: CVE-2018-6764)
CWE-ID: CWE-264 - Permissions, Privileges, and Access Controls
CVSSv4: 8.7 [CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N]
The vulnerability allows an adjacent attacker to bypass security restrictions on the target system.
The weakness exists in the util/virlog.c source code file due to improper determination of hostnames during LXC container startup. An adjacent attacker can bypass security restrictions and execute arbitrary commands.
Remediation
Install update from vendor's website.