{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-5092 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-5092 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-5092 is a high-severity memory corruption vulnerability in LEADTOOLS, published on 11 Dec 2019. 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 CVE-2019-5092 and fix it if it is affected.\n\nWhat it is: CVE-2019-5092 is a high-severity memory corruption vulnerability in LEADTOOLS, published on 11 Dec 2019. 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 CVE-2019-5092 in the wild and no public exploit code.\n\nAffected product: LEADTOOLS. No package-level version data is available, so check the vendor advisory linked from the reference page.\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/CVE-2019-5092/ (Markdown: https://insights.sbomify.com/CVE-2019-5092/index.md)","id":"CVE-2019-5092","markdown":"https://insights.sbomify.com/CVE-2019-5092/index.md","name":"CVE-2019-5092","record":{"aliases":["GHSA-frj8-cjrv-7f9q"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"LEADTOOLS imaging library","requires_auth":"none","summary":"A heap out-of-bounds write in LEADTOOLS DICOM parsing allows attackers to execute arbitrary code via a crafted image.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"talos","cpe":[{"product":"leadtools","vendor":"leadtools"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"An exploitable heap out of bounds write vulnerability exists in the UI tag parsing functionality of the DICOM image format of LEADTOOLS 20.0.2019.3.15. A specially crafted DICOM image can cause an offset beyond the bounds of a heap allocation to be written, potentially resulting in code execution. An attacker can specially craft a DICOM image to trigger this vulnerability.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Memory corruption in LEADTOOLS","id":"CVE-2019-5092","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Integer overflow in LEADTOOLS libltdic.so","id":"CVE-2019-5093"},"packages":[],"prev":{"headline":"Denial of service in LEADTOOLS libltdic.so","id":"CVE-2019-5091"},"products":["LEADTOOLS"],"published":"2019-12-11","related":[{"cvss_score":9.8,"headline":"Integer overflow in LEADTOOLS libltdic.so","id":"CVE-2019-5085","kev_date_added":null,"published":"2019-12-11"},{"cvss_score":9.1,"headline":"Information disclosure in LEADTOOLS libltdic.so","id":"CVE-2019-5090","kev_date_added":null,"published":"2019-12-11"},{"cvss_score":8.8,"headline":"Integer overflow in Leadtools","id":"CVE-2022-21154","kev_date_added":null,"published":"2022-04-14"},{"cvss_score":8.8,"headline":"Memory corruption in Leadtools","id":"CVE-2020-6089","kev_date_added":null,"published":"2020-07-01"},{"cvss_score":8.8,"headline":"Memory corruption in LEADTOOLS","id":"CVE-2019-5154","kev_date_added":null,"published":"2019-12-11"},{"cvss_score":8.8,"headline":"Memory corruption in LEADTOOLS","id":"CVE-2019-5084","kev_date_added":null,"published":"2019-11-06"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"A heap out-of-bounds write in LEADTOOLS DICOM parsing allows attackers to execute arbitrary code via a crafted image.","url":"https://insights.sbomify.com/CVE-2019-5092/"}