{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-11687 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-11687 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-11687 is a high-severity vulnerability in n/a, published on 2 May 2019. 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-2019-11687 and fix it if it is affected.\n\nWhat it is: CVE-2019-11687 is a high-severity vulnerability in n/a, published on 2 May 2019. 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-2019-11687 in the wild and no public exploit code.\n\nAffected product: n/a. 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-11687/ (Markdown: https://insights.sbomify.com/CVE-2019-11687/index.md)","id":"CVE-2019-11687","markdown":"https://insights.sbomify.com/CVE-2019-11687/index.md","name":"CVE-2019-11687","record":{"aliases":["GHSA-9f2r-228g-m882"],"analysis":{"component_type":"other","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"DICOM standard","requires_auth":"none","summary":"The DICOM standard allows executable code in file preambles, enabling attackers to distribute malicious files that execute code when opened by medical systems.","user_interaction":"required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"dicom_standard","vendor":"nema"}],"cvss":{"score":7.8,"severity":"high","source":"cisa-adp","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-20","name":"Improper Input Validation"}],"description":"An issue was discovered in the DICOM Part 10 File Format in the NEMA DICOM Standard 1995 through 2019b and continuing in current implementations. The 128-byte preamble of a DICOM file that complies with this specification can contain arbitrary executable headers for multiple operating systems, including Portable Executable (PE) files for Windows and Executable and Linkable Format (ELF) files for Linux-based systems. This space is left unspecified so that dual-purpose files can be created. For example, dual-purpose TIFF/DICOM files are used in digital whole slide imaging applications in medicine. This design flaw enables system-wide compromise as malicious DICOM files are routinely shared between medical devices and hospital systems and transported via removable media for patient care coordination. To exploit this vulnerability, someone must execute the maliciously crafted file. These files can be executable even with the .dcm file extension. Anti-malware configurations at healthcare facilities often ignore medical imagery. DICOM files exist on systems that process protected health information, and successful exploitation could result in violations of regulatory compliance requirements such as HIPAA and FDA postmarket obligations.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2019-12-15","github_poc":1,"max_poc_stars":6,"metasploit":0,"nuclei":0,"refs":[{"date":"2019-12-15T08:52:17Z","kind":"github_poc","ref":"https://github.com/kosmokato/bad-dicom","stars":6,"title":"Explotation framework for CVE-2019-11687"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Other in n/a","id":"CVE-2019-11687","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2019"},"n_packages":0,"n_references":5,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2019-11688"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2019-11686"},"products":["n/a"],"published":"2019-05-02","related":[],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-06-02","vendors":["n/a"]},"summary":"The DICOM standard allows executable code in file preambles, enabling attackers to distribute malicious files that execute code when opened by medical systems.","url":"https://insights.sbomify.com/CVE-2019-11687/"}