{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-21154 exists.","fix":"No fix has been published for CVE-2022-21154 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-21154 is a high-severity vulnerability in Leadtools, published on 14 Apr 2022. 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-2022-21154 and fix it if it is affected.\n\nWhat it is: CVE-2022-21154 is a high-severity vulnerability in Leadtools, published on 14 Apr 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-21154 exists.\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-2022-21154/ (Markdown: https://insights.sbomify.com/CVE-2022-21154/index.md)","id":"CVE-2022-21154","markdown":"https://insights.sbomify.com/CVE-2022-21154/index.md","name":"CVE-2022-21154","record":{"aliases":["GHSA-cm54-xvgq-698c"],"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":"An attacker can trigger a buffer overflow via a malicious BMP file, potentially leading to code execution in applications using the Leadtools library.","user_interaction":"required","vuln_class":"integer_overflow"},"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-190","name":"Integer Overflow or Wraparound"}],"description":"An integer overflow vulnerability exists in the fltSaveCMP functionality of Leadtools 22. A specially-crafted BMP file can lead to an integer overflow, that in turn causes a buffer overflow. An attacker can provide a malicious BMP file to trigger this vulnerability.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Integer overflow in Leadtools","id":"CVE-2022-21154","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Fernhill SCADA Uncontrolled Resource Consumption","id":"CVE-2022-21155"},"packages":[],"prev":{"headline":"Information disclosure in Intel(R) Capital Global Summit Android application","id":"CVE-2022-21153"},"products":["Leadtools"],"published":"2022-04-14","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":"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-5092","kev_date_added":null,"published":"2019-12-11"},{"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":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-15","vendors":["Leadtools"]},"summary":"An attacker can trigger a buffer overflow via a malicious BMP file, potentially leading to code execution in applications using the Leadtools library.","url":"https://insights.sbomify.com/CVE-2022-21154/"}