CVE-2019-11687 Other in n/a
The DICOM standard allows executable code in file preambles, enabling attackers to distribute malicious files that execute code when opened by medical systems.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2019-11687?
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.
Official 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.
Weakness: CWE-20
Which versions are affected by CVE-2019-11687?
It affects 1 product.
Products include Nema Dicom Standard.
How do I fix CVE-2019-11687?
No fix has been published for CVE-2019-11687 yet. Limit exposure of the affected software until one is available.
Is CVE-2019-11687 being exploited?
There is no known exploitation of CVE-2019-11687 in the wild and no public exploit code.
Public exploit code: 1 proofs of concept on GitHub.
Sources
Also known as GHSA-9f2r-228g-m882.