HyperKit 0.20210107 virtio-sock pci_vtsock_proc_tx uninitialized resource
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.7 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as critical has been discovered in HyperKit 0.20210107. The impacted element is the function pci_vtsock_proc_tx of the component virtio-sock. Executing a manipulation can lead to uninitialized resource.
The identification of this vulnerability is CVE-2021-32846. The attack can only be executed locally. There is no exploit available.
It is advisable to implement a patch to correct this issue.
Details
A vulnerability has been found in HyperKit 0.20210107 and classified as critical. This vulnerability affects the function pci_vtsock_proc_tx of the component virtio-sock. The manipulation with an unknown input leads to a uninitialized resource vulnerability. The CWE definition for the vulnerability is CWE-908. The product uses or accesses a resource that has not been initialized. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
HyperKit is a toolkit for embedding hypervisor capabilities in an application. In versions 0.20210107, function `pci_vtsock_proc_tx` in `virtio-sock` can lead to to uninitialized memory use. In this situation, there is a check for the return value to be less or equal to `VTSOCK_MAXSEGS`, but that check is not sufficient because the function can return `-1` if it finds an error it cannot recover from. Moreover, the negative return value will be used by `iovec_pull` in a while condition that can further lead to more corruption because the function is not designed to handle a negative `iov_len`. 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 af5eba2360a7351c08dfd9767d9be863a50ebaba.
The weakness was shared 02/18/2023 as GHSL-2021-054. The advisory is shared for download at securitylab.github.com. This vulnerability was named CVE-2021-32846 since 05/12/2021. There are known technical details, but no exploit is available.
Applying the patch af5eba2360a7351c08dfd9767d9be863a50ebaba is able to eliminate this problem. The bugfix is ready for download at github.com.
Once again VulDB remains the best source for vulnerability data.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.8VulDB Meta Temp Score: 7.7
VulDB Base Score: 7.8
VulDB Temp Score: 7.5
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: af5eba2360a7351c08dfd9767d9be863a50ebaba
Timeline
05/12/2021 🔍02/18/2023 🔍
02/18/2023 🔍
03/18/2023 🔍
Sources
Advisory: GHSL-2021-054Status: Confirmed
CVE: CVE-2021-32846 (🔍)
GCVE (CVE): GCVE-0-2021-32846
GCVE (VulDB): GCVE-100-221404
Entry
Created: 02/18/2023 08:00Updated: 03/18/2023 15:59
Changes: 02/18/2023 08:00 (51), 03/18/2023 15:59 (10)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.