{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-32846 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-32846 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-32846 is a high-severity memory corruption vulnerability in moby hyperkit, published on 17 Feb 2023. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-32846 and fix it if it is affected.\n\nWhat it is: CVE-2021-32846 is a high-severity memory corruption vulnerability in moby hyperkit, published on 17 Feb 2023. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-32846 in the wild and no public exploit code.\n\nAffected product: moby hyperkit. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2021-32846/ (Markdown: https://insights.sbomify.com/CVE-2021-32846/index.md)","id":"CVE-2021-32846","markdown":"https://insights.sbomify.com/CVE-2021-32846/index.md","name":"CVE-2021-32846","record":{"aliases":["GHSA-8j79-g729-4vv7"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"HyperKit hypervisor","requires_auth":"none","summary":"A guest VM can crash the host or potentially execute code via uninitialized memory use in HyperKit's virtio-sock implementation.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"hyperkit","vendor":"mobyproject"}],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-754","name":"Improper Check for Unusual or Exceptional Conditions"},{"id":"CWE-908","name":"Use of Uninitialized Resource"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Moby HyperKit uninitialized memory use in virtio-sock pci_vtsock_proc_tx","id":"CVE-2021-32846","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2021"},"n_packages":0,"n_references":3,"next":{"headline":"Moby HyperKit uninitialized memory use in virtio-sock pci_vtsock_proc_tx","id":"CVE-2021-32847"},"packages":[],"prev":{"headline":"Moby HyperKit uninitialized memory use vtrnd pci_vtrnd_notify","id":"CVE-2021-32845"},"products":["hyperkit"],"published":"2023-02-17","related":[{"cvss_score":7.7,"headline":"Moby HyperKit uninitialized memory use vtrnd pci_vtrnd_notify","id":"CVE-2021-32845","kev_date_added":null,"published":"2023-02-17"},{"cvss_score":7.1,"headline":"Moby HyperKit uninitialized memory use in virtio-sock pci_vtsock_proc_tx","id":"CVE-2021-32847","kev_date_added":null,"published":"2023-02-20"},{"cvss_score":6.2,"headline":"Null dereference in hyperkit","id":"CVE-2021-32843","kev_date_added":null,"published":"2023-02-17"},{"cvss_score":6.2,"headline":"Null dereference in hyperkit","id":"CVE-2021-32844","kev_date_added":null,"published":"2023-02-17"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-10","vendors":["moby"]},"summary":"A guest VM can crash the host or potentially execute code via uninitialized memory use in HyperKit's virtio-sock implementation.","url":"https://insights.sbomify.com/CVE-2021-32846/"}