libvirt up to 6.0.x qemu/qemu_driver.c qemuDomainGetStatsIOThread memory leak
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in libvirt up to 6.0.x. It has been classified as problematic. This impacts the function qemuDomainGetStatsIOThread of the file qemu/qemu_driver.c. This manipulation causes memory leak.
This vulnerability is tracked as CVE-2020-12430. The attack is possible to be carried out remotely. No exploit exists.
Upgrading the affected component is recommended.
Details
A vulnerability was found in libvirt up to 6.0.x (Virtualization Software). It has been declared as problematic. Affected by this vulnerability is the function qemuDomainGetStatsIOThread of the file qemu/qemu_driver.c. The manipulation with an unknown input leads to a memory leak vulnerability. The CWE definition for the vulnerability is CWE-401. The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory. As an impact it is known to affect availability. The summary by CVE is:
An issue was discovered in qemuDomainGetStatsIOThread in qemu/qemu_driver.c in libvirt 4.10.0 though 6.x before 6.1.0. A memory leak was found in the virDomainListGetStats libvirt API that is responsible for retrieving domain statistics when managing QEMU guests. This flaw allows unprivileged users with a read-only connection to cause a memory leak in the domstats command, resulting in a potential denial of service.
The weakness was disclosed 04/28/2020. This vulnerability is known as CVE-2020-12430 since 04/28/2020. The exploitation appears to be easy. The attack can be launched remotely. The requirement for exploitation is a single authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1499 for this issue.
The vulnerability scanner Nessus provides a plugin with the ID 209571 (Oracle Linux 8 : virt:kvm_utils3 (ELSA-2024-12792)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 4.10.0 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at Tenable (209571). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Memory leakCWE: CWE-401 / 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-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 209571
Nessus Name: Oracle Linux 8 : virt:kvm_utils3 (ELSA-2024-12792)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: libvirt 4.10.0
Patch: 9bf9e0ae6af38c806f4672ca7b12a6b38d5a9581
Timeline
04/28/2020 🔍04/28/2020 🔍
04/29/2020 🔍
10/25/2024 🔍
Sources
Advisory: USN-4371-1Status: Confirmed
Confirmation: 🔍
CVE: CVE-2020-12430 (🔍)
GCVE (CVE): GCVE-0-2020-12430
GCVE (VulDB): GCVE-100-154537
Entry
Created: 04/29/2020 08:12Updated: 10/25/2024 05:47
Changes: 04/29/2020 08:12 (37), 04/29/2020 08:17 (18), 10/14/2020 05:53 (1), 06/04/2024 09:08 (21), 10/25/2024 05:47 (4)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.