{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2010-2223 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2010-2223 is a low-severity vulnerability in n/a, published on 24 Jun 2010. 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-2010-2223 and fix it if it is affected.\n\nWhat it is: CVE-2010-2223 is a low-severity vulnerability in n/a, published on 24 Jun 2010. 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-2010-2223 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2010-2223/ (Markdown: https://insights.sbomify.com/CVE-2010-2223/index.md)","id":"CVE-2010-2223","markdown":"https://insights.sbomify.com/CVE-2010-2223/index.md","name":"CVE-2010-2223","record":{"aliases":["GHSA-q8g8-jjw3-wwpx","RHSA-2010:0473"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"RHEV Hypervisor","requires_auth":"low_privilege","summary":"Guest OS users can obtain sensitive information from deleted virtual machine disk blocks due to improper data zeroing in RHEV Hypervisor.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"enterprise_virtualization_hypervisor","vendor":"redhat"}],"cvss":{"score":2.1,"severity":"low","source":"nvd","vector":"AV:L/AC:L/Au:N/C:P/I:N/A:N","version":"2.0"},"cwes":[{"id":"CWE-264","name":null}],"description":"Virtual Desktop Server Manager (VDSM) in Red Hat Enterprise Virtualization Hypervisor (aka RHEV-H or rhev-hypervisor) before 5.5-2.2 does not properly perform VM post-zeroing after the removal of a virtual machine's data, which allows guest OS users to obtain sensitive information by examining the disk blocks associated with a deleted virtual machine.","ecosystems":["Red Hat:enterprise_linux:5::hypervisor"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Information disclosure in n/a","id":"CVE-2010-2223","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2010"},"n_packages":3,"n_references":5,"next":{"headline":"Information disclosure in n/a","id":"CVE-2010-2224"},"packages":[{"ecosystem":"Red Hat:enterprise_linux:5::hypervisor","fixed":["0:4.5-62.el5rhev"],"introduced":["0"],"last_affected":[],"package":"vdsm22","purl":"pkg:rpm/redhat/vdsm22","source":"RHSA-2010:0473"},{"ecosystem":"Red Hat:enterprise_linux:5::hypervisor","fixed":["0:4.5-62.el5rhev"],"introduced":["0"],"last_affected":[],"package":"vdsm22-cli","purl":"pkg:rpm/redhat/vdsm22-cli","source":"RHSA-2010:0473"},{"ecosystem":"Red Hat:enterprise_linux:5::hypervisor","fixed":["0:4.5-62.el5rhev"],"introduced":["0"],"last_affected":[],"package":"vdsm22-debuginfo","purl":"pkg:rpm/redhat/vdsm22-debuginfo","source":"RHSA-2010:0473"}],"prev":{"headline":"Null dereference in Red Hat Directory Server","id":"CVE-2010-2222"},"products":["n/a"],"published":"2010-06-24","related":[{"cvss_score":7.4,"headline":"Memory corruption in n/a","id":"CVE-2010-0430","kev_date_added":null,"published":"2013-12-27"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"Red Hat","prefix":"RHSA"},{"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Guest OS users can obtain sensitive information from deleted virtual machine disk blocks due to improper data zeroing in RHEV Hypervisor.","url":"https://insights.sbomify.com/CVE-2010-2223/"}