{"answers":{"affected":"1 open source package ship an affected version, including openthread.","exploited":"There is no known exploitation of OSV-2020-721 in the wild and no public exploit code.","fix":"No fix has been published for OSV-2020-721 yet. Limit exposure of the affected software until one is available.","what":"OSV-2020-721 is a memory corruption vulnerability in openthread, published on 1 Jul 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-721 and fix it if it is affected.\n\nWhat it is: OSV-2020-721 is a memory corruption vulnerability in openthread, published on 1 Jul 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-721 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- openthread (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-721/ (Markdown: https://insights.sbomify.com/OSV-2020-721/index.md)","id":"OSV-2020-721","markdown":"https://insights.sbomify.com/OSV-2020-721/index.md","name":"OSV-2020-721","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":"Thread network stack","requires_auth":"none","summary":"A stack buffer overflow in the Thread network data handling allows attackers to cause denial of service or potentially execute code via crafted network packets.","user_interaction":"not_required","vuln_class":"memory_corruption"},"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=13334\n\n```\nCrash type: Stack-buffer-overflow WRITE {*}\nCrash state:\not::NetworkData::NetworkData::GetNextOnMeshPrefix\not::Dhcp6::Dhcp6Client::UpdateAddresses\not::Mle::Mle::HandleStateChanged\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":"Stack-buffer-overflow in ot::NetworkData::NetworkData::GetNextOnMeshPrefix","id":"OSV-2020-721","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"OSS-Fuzz","product":null,"products":[],"type":"memory_corruption","year":"2020"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"OSS-Fuzz","fixed":[],"introduced":[],"last_affected":[],"package":"openthread","purl":"pkg:generic/openthread","source":"OSV-2020-721"}],"products":null,"published":"2020-07-01","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 stack buffer overflow in the Thread network data handling allows attackers to cause denial of service or potentially execute code via crafted network packets.","url":"https://insights.sbomify.com/OSV-2020-721/"}