HyperKit up to 0.20210107 pci_vtrnd_notify return uninitialized resource
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.9 | $0-$5k | 0.00 |
Summary
A vulnerability was found in HyperKit up to 0.20210107. It has been rated as problematic. This impacts the function pci_vtrnd_notify. The manipulation of the argument return leads to uninitialized resource.
This vulnerability is uniquely identified as CVE-2021-32845. Local access is required to approach this attack. No exploit exists.
It is suggested to install a patch to address this issue.
Details
A vulnerability was found in HyperKit up to 0.20210107. It has been rated as problematic. This issue affects the function pci_vtrnd_notify. The manipulation of the argument return with an unknown input leads to a uninitialized resource vulnerability. Using CWE to declare the problem leads to CWE-908. The product uses or accesses a resource that has not been initialized. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
HyperKit is a toolkit for embedding hypervisor capabilities in an application. In versions 0.20210107 and prior of HyperKit, the implementation of `qnotify` at `pci_vtrnd_notify` fails to check the return value of `vq_getchain`. This leads to `struct iovec iov;` being uninitialized and used to read memory in `len = (int) read(sc->vrsc_fd, iov.iov_base, iov.iov_len);` when an attacker is able to make `vq_getchain` fail. This issue may lead to a guest crashing the host causing a denial of service and, under certain circumstance, memory corruption. This issue is fixed in commit 41272a980197917df8e58ff90642d14dec8fe948.
The weakness was disclosed 02/18/2023 as GHSL-2021-054. The advisory is shared at securitylab.github.com. The identification of this vulnerability is CVE-2021-32845 since 05/12/2021. Technical details are known, but no exploit is available.
Applying the patch 41272a980197917df8e58ff90642d14dec8fe948 is able to eliminate this problem. The bugfix is ready for download at github.com.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.9VulDB Meta Temp Score: 6.9
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.8
NVD Vector: 🔍
CNA Base Score: 7.7
CNA Vector (GitHub, Inc.): 🔍
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: 🔍
Exploiting
Class: Uninitialized resourceCWE: CWE-908
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔍
Patch: 41272a980197917df8e58ff90642d14dec8fe948
Timeline
05/12/2021 🔍02/18/2023 🔍
02/18/2023 🔍
03/18/2023 🔍
Sources
Advisory: GHSL-2021-054Status: Confirmed
CVE: CVE-2021-32845 (🔍)
GCVE (CVE): GCVE-0-2021-32845
GCVE (VulDB): GCVE-100-221417
Entry
Created: 02/18/2023 08:07Updated: 03/18/2023 16:26
Changes: 02/18/2023 08:07 (51), 03/18/2023 16:26 (11)
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.