{"answers":{"affected":"1 open source package ship an affected version, including c-blosc2.","exploited":"There is no known exploitation of OSV-2021-1663 in the wild and no public exploit code.","fix":"No fix has been published for OSV-2021-1663 yet. Limit exposure of the affected software until one is available.","what":"OSV-2021-1663 is a memory corruption vulnerability in c-blosc2, published on 10 Dec 2021."},"fix_prompt":"Check this codebase for OSV-2021-1663 and fix it if it is affected.\n\nWhat it is: OSV-2021-1663 is a memory corruption vulnerability in c-blosc2, published on 10 Dec 2021. \nExploitation: There is no known exploitation of OSV-2021-1663 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- c-blosc2 (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-2021-1663/ (Markdown: https://insights.sbomify.com/OSV-2021-1663/index.md)","id":"OSV-2021-1663","markdown":"https://insights.sbomify.com/OSV-2021-1663/index.md","name":"OSV-2021-1663","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"unknown","non_default_config":false,"product_category":"Blosc compression library","requires_auth":"none","summary":"A heap-buffer-overflow in the ndlz4_decompress function of the Blosc library allows attackers to cause memory corruption, potentially leading to code execution or crashes.","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=42131\n\n```\nCrash type: Heap-buffer-overflow WRITE {*}\nCrash state:\nndlz4_decompress\nblosc_d\ndo_job\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-buffer-overflow in ndlz4_decompress","id":"OSV-2021-1663","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"OSS-Fuzz","product":null,"products":[],"type":"memory_corruption","year":"2021"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"OSS-Fuzz","fixed":[],"introduced":[],"last_affected":[],"package":"c-blosc2","purl":"pkg:generic/c-blosc2","source":"OSV-2021-1663"}],"products":null,"published":"2021-12-10","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-buffer-overflow in the ndlz4_decompress function of the Blosc library allows attackers to cause memory corruption, potentially leading to code execution or crashes.","url":"https://insights.sbomify.com/OSV-2021-1663/"}