{"answers":{"affected":"1 open source package ship an affected version, including opencv.","exploited":"There is no known exploitation of OSV-2020-1819 in the wild and no public exploit code.","fix":"No fix has been published for OSV-2020-1819 yet. Limit exposure of the affected software until one is available.","what":"OSV-2020-1819 is a memory corruption vulnerability in opencv, published on 21 Sep 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for OSV-2020-1819 and fix it if it is affected.\n\nWhat it is: OSV-2020-1819 is a memory corruption vulnerability in opencv, published on 21 Sep 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of OSV-2020-1819 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- opencv (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-1819/ (Markdown: https://insights.sbomify.com/OSV-2020-1819/index.md)","id":"OSV-2020-1819","markdown":"https://insights.sbomify.com/OSV-2020-1819/index.md","name":"OSV-2020-1819","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"OpenCV image library","requires_auth":"none","summary":"A heap buffer overflow in OpenCV's JPEG2000 decoder allows attackers to cause crashes or potentially execute code via malicious images.","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=25779\n\n```\nCrash type: Heap-buffer-overflow READ 4\nCrash state:\nvoid cv::copyToMat\u003cint\u003e\ncv::decodeSRGBData\ncv::Jpeg2KOpjDecoder::readData\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 void cv::copyToMat\u003cint\u003e","id":"OSV-2020-1819","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":"opencv","purl":"pkg:generic/opencv","source":"OSV-2020-1819"}],"products":null,"published":"2020-09-21","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 OpenCV's JPEG2000 decoder allows attackers to cause crashes or potentially execute code via malicious images.","url":"https://insights.sbomify.com/OSV-2020-1819/"}