{"answers":{"affected":"1 open source package ship an affected version, including libavc.","exploited":"There is no known exploitation of OSV-2023-117 in the wild and no public exploit code.","fix":"No fix has been published for OSV-2023-117 yet. Limit exposure of the affected software until one is available.","what":"OSV-2023-117 is a memory corruption vulnerability in libavc, published on 28 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for OSV-2023-117 and fix it if it is affected.\n\nWhat it is: OSV-2023-117 is a memory corruption vulnerability in libavc, published on 28 Feb 2023. 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-2023-117 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-2023-117/ (Markdown: https://insights.sbomify.com/OSV-2023-117/index.md)","id":"OSV-2023-117","markdown":"https://insights.sbomify.com/OSV-2023-117/index.md","name":"OSV-2023-117","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Video codec library","requires_auth":"none","summary":"A heap buffer overflow in the video codec library allows attackers to execute arbitrary code or cause denial of service via crafted media 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=56386\n\n```\nCrash type: Heap-buffer-overflow WRITE 4\nCrash state:\nisvcd_nal_byte_swap_emulation\nisvcd_nal_parse_non_vcl_nal\nisvcd_pre_parse_refine_au\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 isvcd_nal_byte_swap_emulation","id":"OSV-2023-117","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"OSS-Fuzz","product":null,"products":[],"type":"memory_corruption","year":"2023"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"OSS-Fuzz","fixed":[],"introduced":[],"last_affected":[],"package":"libavc","purl":"pkg:generic/libavc","source":"OSV-2023-117"}],"products":null,"published":"2023-02-28","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 video codec library allows attackers to execute arbitrary code or cause denial of service via crafted media files.","url":"https://insights.sbomify.com/OSV-2023-117/"}