{"answers":{"affected":"1 open source package ship an affected version, including qemu.","exploited":"There is no known exploitation of OSV-2020-2223 in the wild and no public exploit code.","fix":"No fix has been published for OSV-2020-2223 yet. Limit exposure of the affected software until one is available.","what":"OSV-2020-2223 is an use after free vulnerability in qemu, published on 4 Dec 2020. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for OSV-2020-2223 and fix it if it is affected.\n\nWhat it is: OSV-2020-2223 is an use after free vulnerability in qemu, published on 4 Dec 2020. 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 OSV-2020-2223 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- qemu (OSS-Fuzz): affected all versions; no fix listed\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/OSV-2020-2223/ (Markdown: https://insights.sbomify.com/OSV-2020-2223/index.md)","id":"OSV-2020-2223","markdown":"https://insights.sbomify.com/OSV-2020-2223/index.md","name":"OSV-2020-2223","record":{"aliases":[],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"QEMU e1000e driver","requires_auth":"none","summary":"A heap-use-after-free in the QEMU e1000e network driver allows attackers to cause denial of service or potentially execute code via crafted packets.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=28194\n\n```\nCrash type: Heap-use-after-free READ 8\nCrash state:\ne1000e_write_packet_to_guest\ne1000e_receive_iov\ne1000e_nc_receive_iov\n```","ecosystems":["OSS-Fuzz"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":false,"headline":"Heap-use-after-free in e1000e_write_packet_to_guest","id":"OSV-2020-2223","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"OSS-Fuzz","product":null,"products":[],"type":"use_after_free","year":"2020"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"OSS-Fuzz","fixed":[],"introduced":[],"last_affected":[],"package":"qemu","purl":"pkg:generic/qemu","source":"OSV-2020-2223"}],"products":null,"published":"2020-12-04","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"OSS-Fuzz","prefix":"OSV"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"A heap-use-after-free in the QEMU e1000e network driver allows attackers to cause denial of service or potentially execute code via crafted packets.","url":"https://insights.sbomify.com/OSV-2020-2223/"}