{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-22100 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-22100 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-22100 is a high-severity memory corruption vulnerability in MicroDicom DICOM Viewer, published on 1 Mar 2024. 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-2024-22100 and fix it if it is affected.\n\nWhat it is: CVE-2024-22100 is a high-severity memory corruption vulnerability in MicroDicom DICOM Viewer, published on 1 Mar 2024. 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-2024-22100 in the wild and no public exploit code.\n\nAffected product: MicroDicom DICOM Viewer. 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-2024-22100/ (Markdown: https://insights.sbomify.com/CVE-2024-22100/index.md)","id":"CVE-2024-22100","markdown":"https://insights.sbomify.com/CVE-2024-22100/index.md","name":"CVE-2024-22100","record":{"aliases":["GHSA-236w-6xxf-5g8v"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"DICOM Viewer","requires_auth":"none","summary":"A heap-based buffer overflow in MicroDicom DICOM Viewer allows arbitrary code execution when a user opens a malicious DCM file.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"icscert","cpe":[{"product":"dicom_viewer","vendor":"microdicom"}],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"},{"id":"CWE-122","name":"Heap-based Buffer Overflow"}],"description":"MicroDicom DICOM Viewer versions 2023.3 (Build 9342) and prior are affected by a heap-based buffer overflow vulnerability, which could allow an attacker to execute arbitrary code on affected installations of DICOM Viewer. A user must open a malicious DCM file in order to exploit the 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":"MicroDicom DICOM Heap-based Buffer Overflow","id":"CVE-2024-22100","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Denial of service in n/a","id":"CVE-2024-22102"},"packages":[],"prev":{"headline":"NULL pointer deference in rfcomm_check_security in Linux kernel","id":"CVE-2024-22099"},"products":["DICOM Viewer"],"published":"2024-03-01","related":[{"cvss_score":8.7,"headline":"MicroDicom DICOM Viewer Stack-based Buffer Overflow","id":"CVE-2024-28877","kev_date_added":null,"published":"2024-06-11"},{"cvss_score":8.6,"headline":"MicroDicom DICOM Viewer Improper Authorization in Handler for Custom URL Scheme","id":"CVE-2024-33606","kev_date_added":null,"published":"2024-06-11"},{"cvss_score":7.8,"headline":"MicroDicom DICOM Viewer Out-of-Bounds Write","id":"CVE-2024-25578","kev_date_added":null,"published":"2024-03-01"},{"cvss_score":5.7,"headline":"MicroDicom DICOM Viewer Improper Certificate Validation","id":"CVE-2025-1002","kev_date_added":null,"published":"2025-02-10"}],"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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-08-12","vendors":["MicroDicom"]},"summary":"A heap-based buffer overflow in MicroDicom DICOM Viewer allows arbitrary code execution when a user opens a malicious DCM file.","url":"https://insights.sbomify.com/CVE-2024-22100/"}