{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-24064 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-24064 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-24064 is a high-severity memory corruption vulnerability in Sante DICOM Viewer Pro, published on 18 Feb 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-24064 and fix it if it is affected.\n\nWhat it is: CVE-2022-24064 is a high-severity memory corruption vulnerability in Sante DICOM Viewer Pro, published on 18 Feb 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-24064 in the wild and no public exploit code.\n\nAffected product: Sante DICOM Viewer Pro. 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-24064/ (Markdown: https://insights.sbomify.com/CVE-2022-24064/index.md)","id":"CVE-2022-24064","markdown":"https://insights.sbomify.com/CVE-2022-24064/index.md","name":"CVE-2022-24064","record":{"aliases":["GHSA-2rq2-48fh-56v5"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"DICOM Viewer Pro","requires_auth":"none","summary":"Remote attackers can execute arbitrary code via crafted J2K images in Sante DICOM Viewer Pro, requiring user interaction to open a malicious file.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"zdi","cpe":[{"product":"dicom_viewer_pro","vendor":"santesoft"}],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:L/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":"This vulnerability allows remote attackers to execute arbitrary code on affected installations of Sante DICOM Viewer Pro 11.8.8.0. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the parsing of J2K images. Crafted data in a J2K file can trigger a write past the end of an allocated buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-15161.","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 DICOM Viewer Pro","id":"CVE-2022-24064","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Command Injection","id":"CVE-2022-24065"},"packages":[],"prev":{"headline":"Memory corruption in DICOM Viewer Pro","id":"CVE-2022-24063"},"products":["DICOM Viewer Pro"],"published":"2022-02-18","related":[{"cvss_score":8.4,"headline":"Santesoft Sante DICOM Viewer Pro Out-of-bounds Read","id":"CVE-2025-5307","kev_date_added":null,"published":"2025-05-29"},{"cvss_score":8.4,"headline":"Santesoft Sante DICOM Viewer Pro Out-of-bounds Write","id":"CVE-2025-2480","kev_date_added":null,"published":"2025-03-20"},{"cvss_score":7.8,"headline":"Sante DICOM Viewer Pro DCM File Parsing Buffer Overflow Remote Code Execution Vulnerability","id":"CVE-2026-2034","kev_date_added":null,"published":"2026-02-20"},{"cvss_score":7.8,"headline":"Sante DICOM Viewer Pro DCM File Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability","id":"CVE-2025-5481","kev_date_added":null,"published":"2025-06-06"},{"cvss_score":7.8,"headline":"Sante DICOM Viewer Pro DCM File Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability","id":"CVE-2023-34295","kev_date_added":null,"published":"2024-05-03"},{"cvss_score":7.8,"headline":"Sante DICOM Viewer Pro DCM File Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability","id":"CVE-2023-34296","kev_date_added":null,"published":"2024-05-03"},{"cvss_score":7.8,"headline":"Sante DICOM Viewer Pro JP2 File Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability","id":"CVE-2023-34297","kev_date_added":null,"published":"2024-05-03"}],"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-03","vendors":["Sante"]},"summary":"Remote attackers can execute arbitrary code via crafted J2K images in Sante DICOM Viewer Pro, requiring user interaction to open a malicious file.","url":"https://insights.sbomify.com/CVE-2022-24064/"}