libvirt up to 4.1.x Incomplete Fix CVE-2018-5748 resource consumption

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.3$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as problematic, has been found in libvirt up to 4.1.x. Affected by this issue is some unknown functionality of the component Incomplete Fix CVE-2018-5748. The manipulation leads to resource consumption. This vulnerability is listed as CVE-2018-1064. The attack may be initiated remotely. There is no available exploit. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in libvirt up to 4.1.x (Virtualization Software). This issue affects an unknown functionality of the component Incomplete Fix CVE-2018-5748. The manipulation with an unknown input leads to a resource consumption vulnerability. Using CWE to declare the problem leads to CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. Impacted is availability. The summary by CVE is:

libvirt version before 4.2.0-rc1 is vulnerable to a resource exhaustion as a result of an incomplete fix for CVE-2018-5748 that affects QEMU monitor but now also triggered via QEMU guest agent.

The bug was discovered 03/01/2018. The weakness was presented 03/28/2018 by Jann Horn (Mike) with Google Project Zero as Bug 1550672 as confirmed bug report (Bugzilla). The advisory is shared at bugzilla.redhat.com. The identification of this vulnerability is CVE-2018-1064 since 12/04/2017. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1499 for this issue.

The vulnerability was handled as a non-public zero-day exploit for at least 27 days. During that time the estimated underground price was around $0-$5k. The vulnerability scanner Nessus provides a plugin with the ID 110706 (Oracle Linux 6 : libvirt (ELSA-2018-1929)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Oracle Linux Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 197168 (Ubuntu Security Notification for Libvirt Vulnerability And Update (USN-3680-1)).

Upgrading to version 4.2.0-rc1 eliminates this vulnerability. A possible mitigation has been published 4 months after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (110706) and SecurityFocus (BID 102376†). See VDB-112184, VDB-113748 and VDB-137899 for similar entries. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.4
VulDB Meta Temp Score: 6.3

VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.5
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Resource consumption
CWE: CWE-400 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 110706
Nessus Name: Oracle Linux 6 : libvirt (ELSA-2018-1929)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 66409
OpenVAS Name: Debian Security Advisory DSA 4137-1 (libvirt - security update)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Upgrade: libvirt 4.2.0-rc1
Patch: fbf31e1a4cd19d6f6e33e0937a009775cd7d9513

Timelineinfo

12/04/2017 🔍
01/03/2018 +30 days 🔍
03/01/2018 +57 days 🔍
03/28/2018 +27 days 🔍
03/28/2018 +0 days 🔍
03/29/2018 +1 days 🔍
06/26/2018 +89 days 🔍
06/27/2018 +1 days 🔍
02/24/2023 +1703 days 🔍

Sourcesinfo

Advisory: Bug 1550672
Researcher: Jann Horn (Mike)
Organization: Google Project Zero
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2018-1064 (🔍)
GCVE (CVE): GCVE-0-2018-1064
GCVE (VulDB): GCVE-100-115193

OVAL: 🔍

SecurityFocus: 102376 - Multiple CPU Hardware CVE-2017-5715 Information Disclosure Vulnerability

See also: 🔍

Entryinfo

Created: 03/29/2018 10:29
Updated: 02/24/2023 14:20
Changes: 03/29/2018 10:29 (79), 01/18/2020 07:04 (8), 02/24/2023 14:20 (5)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!