{"answers":{"affected":"1 open source package ship an affected version, including exiv2.","exploited":"There is no known exploitation of OSV-2024-340 in the wild and no public exploit code.","fix":"No fix has been published for OSV-2024-340 yet. Limit exposure of the affected software until one is available.","what":"OSV-2024-340 is a memory corruption vulnerability in exiv2, published on 30 Apr 2024."},"fix_prompt":"Check this codebase for OSV-2024-340 and fix it if it is affected.\n\nWhat it is: OSV-2024-340 is a memory corruption vulnerability in exiv2, published on 30 Apr 2024. \nExploitation: There is no known exploitation of OSV-2024-340 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- exiv2 (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-2024-340/ (Markdown: https://insights.sbomify.com/OSV-2024-340/index.md)","id":"OSV-2024-340","markdown":"https://insights.sbomify.com/OSV-2024-340/index.md","name":"OSV-2024-340","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service","code_execution"],"network_reachable":"unknown","non_default_config":false,"product_category":"Exiv2 image library","requires_auth":"none","summary":"A heap-buffer-overflow in Exiv2's ASF video parser allows attackers to cause crashes or potentially execute code via malicious files.","user_interaction":"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=68210\n\n```\nCrash type: Heap-buffer-overflow READ 8\nCrash state:\nExiv2::AsfVideo::GUIDTag::GUIDTag\nExiv2::AsfVideo::streamProperties\nExiv2::AsfVideo::decodeBlock\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 Exiv2::AsfVideo::GUIDTag::GUIDTag","id":"OSV-2024-340","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"OSS-Fuzz","product":null,"products":[],"type":"memory_corruption","year":"2024"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"OSS-Fuzz","fixed":[],"introduced":[],"last_affected":[],"package":"exiv2","purl":"pkg:generic/exiv2","source":"OSV-2024-340"}],"products":null,"published":"2024-04-30","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 Exiv2's ASF video parser allows attackers to cause crashes or potentially execute code via malicious files.","url":"https://insights.sbomify.com/OSV-2024-340/"}