{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-32847 exists.","fix":"No fix has been published for CVE-2021-32847 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-32847 is a high-severity vulnerability in moby hyperkit, published on 20 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-32847 and fix it if it is affected.\n\nWhat it is: CVE-2021-32847 is a high-severity vulnerability in moby hyperkit, published on 20 Feb 2023. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-32847 exists.\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-32847/ (Markdown: https://insights.sbomify.com/CVE-2021-32847/index.md)","id":"CVE-2021-32847","markdown":"https://insights.sbomify.com/CVE-2021-32847/index.md","name":"CVE-2021-32847","record":{"aliases":["GHSA-gpgx-6j76-jh6m"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"HyperKit hypervisor","requires_auth":"none","summary":"A malicious guest can trigger uninitialized memory use in HyperKit to disclose host memory, requiring a patch to prevent data leakage.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"hyperkit","vendor":"mobyproject"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"HyperKit is a toolkit for embedding hypervisor capabilities in an application. In versions 0.20210107 and prior, a malicious guest can trigger a vulnerability in the host by abusing the disk driver that may lead to the disclosure of the host memory into the virtualized guest. This issue is fixed in commit cf60095a4d8c3cb2e182a14415467afd356e982f.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Moby HyperKit uninitialized memory use in virtio-sock pci_vtsock_proc_tx","id":"CVE-2021-32847","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2021"},"n_packages":0,"n_references":3,"next":{"headline":"Octobox ReDoS vulnerability","id":"CVE-2021-32848"},"packages":[],"prev":{"headline":"Moby HyperKit uninitialized memory use in virtio-sock pci_vtsock_proc_tx","id":"CVE-2021-32846"},"products":["hyperkit"],"published":"2023-02-20","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.7,"headline":"Moby HyperKit uninitialized memory use in virtio-sock pci_vtsock_proc_tx","id":"CVE-2021-32846","kev_date_added":null,"published":"2023-02-17"},{"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-10","vendors":["moby"]},"summary":"A malicious guest can trigger uninitialized memory use in HyperKit to disclose host memory, requiring a patch to prevent data leakage.","url":"https://insights.sbomify.com/CVE-2021-32847/"}