{"answers":{"affected":"1 open source package ship an affected version, including harfbuzz.","exploited":"There is no known exploitation of OSV-2022-1209 in the wild and no public exploit code.","fix":"No fix has been published for OSV-2022-1209 yet. Limit exposure of the affected software until one is available.","what":"OSV-2022-1209 is a memory corruption vulnerability in harfbuzz, published on 25 Nov 2022."},"fix_prompt":"Check this codebase for OSV-2022-1209 and fix it if it is affected.\n\nWhat it is: OSV-2022-1209 is a memory corruption vulnerability in harfbuzz, published on 25 Nov 2022. \nExploitation: There is no known exploitation of OSV-2022-1209 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- harfbuzz (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-2022-1209/ (Markdown: https://insights.sbomify.com/OSV-2022-1209/index.md)","id":"OSV-2022-1209","markdown":"https://insights.sbomify.com/OSV-2022-1209/index.md","name":"OSV-2022-1209","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"unknown","non_default_config":false,"product_category":"HarfBuzz text shaping","requires_auth":"none","summary":"A heap-buffer-overflow in HarfBuzz allows attackers to cause denial of service or potentially execute code via crafted font data.","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=53714\n\n```\nCrash type: Heap-buffer-overflow READ 4\nCrash state:\nOT::hb_ot_apply_context_t::skipping_iterator_t::next\nOT::Layout::GSUB_impl::Ligature\u003cOT::Layout::SmallTypes\u003e::apply\nbool OT::hb_accelerate_subtables_context_t::apply_to\u003cOT::Layout::GSUB_impl::Liga\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 OT::hb_ot_apply_context_t::skipping_iterator_t::next","id":"OSV-2022-1209","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"OSS-Fuzz","product":null,"products":[],"type":"memory_corruption","year":"2022"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"OSS-Fuzz","fixed":[],"introduced":[],"last_affected":[],"package":"harfbuzz","purl":"pkg:generic/harfbuzz","source":"OSV-2022-1209"}],"products":null,"published":"2022-11-25","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 HarfBuzz allows attackers to cause denial of service or potentially execute code via crafted font data.","url":"https://insights.sbomify.com/OSV-2022-1209/"}