{"answers":{"affected":"1 open source package ship an affected version, including libavc.","exploited":"There is no known exploitation of OSV-2020-2188 in the wild and no public exploit code.","fix":"No fix has been published for OSV-2020-2188 yet. Limit exposure of the affected software until one is available.","what":"OSV-2020-2188 is a memory corruption vulnerability in libavc, published on 26 Nov 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for OSV-2020-2188 and fix it if it is affected.\n\nWhat it is: OSV-2020-2188 is a memory corruption vulnerability in libavc, published on 26 Nov 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of OSV-2020-2188 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- libavc (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-2188/ (Markdown: https://insights.sbomify.com/OSV-2020-2188/index.md)","id":"OSV-2020-2188","markdown":"https://insights.sbomify.com/OSV-2020-2188/index.md","name":"OSV-2020-2188","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"H.264 decoder library","requires_auth":"none","summary":"A heap buffer overflow in the H.264 decoder allows attackers to execute arbitrary code or cause denial of service via crafted video 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=27856\n\n```\nCrash type: Heap-buffer-overflow WRITE {*}\nCrash state:\nih264d_parse_pslice\nih264d_parse_decode_slice\nih264d_parse_nal_unit\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 ih264d_parse_pslice","id":"OSV-2020-2188","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":"libavc","purl":"pkg:generic/libavc","source":"OSV-2020-2188"}],"products":null,"published":"2020-11-26","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 H.264 decoder allows attackers to execute arbitrary code or cause denial of service via crafted video files.","url":"https://insights.sbomify.com/OSV-2020-2188/"}