{"answers":{"affected":"1 open source package ship an affected version, including htslib.","exploited":"There is no known exploitation of OSV-2021-229 in the wild and no public exploit code.","fix":"No fix has been published for OSV-2021-229 yet. Limit exposure of the affected software until one is available.","what":"OSV-2021-229 is a memory corruption vulnerability in htslib, published on 24 Jan 2021."},"fix_prompt":"Check this codebase for OSV-2021-229 and fix it if it is affected.\n\nWhat it is: OSV-2021-229 is a memory corruption vulnerability in htslib, published on 24 Jan 2021. \nExploitation: There is no known exploitation of OSV-2021-229 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- htslib (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-229/ (Markdown: https://insights.sbomify.com/OSV-2021-229/index.md)","id":"OSV-2021-229","markdown":"https://insights.sbomify.com/OSV-2021-229/index.md","name":"OSV-2021-229","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"unknown","non_default_config":false,"product_category":"CRAM file library","requires_auth":"none","summary":"A heap buffer overflow in the CRAM decoder allows attackers to cause denial of service or potentially execute code via malicious files.","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=29827\n\n```\nCrash type: Heap-buffer-overflow WRITE 4\nCrash state:\ncram_xpack_decode_init\ncram_decoder_init\ncram_decode_compression_header\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 cram_xpack_decode_init","id":"OSV-2021-229","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":"htslib","purl":"pkg:generic/htslib","source":"OSV-2021-229"}],"products":null,"published":"2021-01-24","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 CRAM decoder allows attackers to cause denial of service or potentially execute code via malicious files.","url":"https://insights.sbomify.com/OSV-2021-229/"}