MicroDicom vulnerabilities
We track 7 vulnerabilities in MicroDicom products. 7 are rated high or critical, and none are known to be exploited. The most recent was published on June 10, 2025.
Latest MicroDicom vulnerabilities
- 8.8 High severity
DICOM Viewer: Out-of-bounds Write
MicroDicom DICOM Viewer suffers from an out-of-bounds write vulnerability. Remote attackers are able to exploit this issue to potentially execute arbitrary code on affected installations of DICOM Viewer. User interaction is required to exploit the vulnerabilit
- 8.8 High severity
DICOM Viewer: Out-of-bounds Read
MicroDicom DICOM Viewer is vulnerable to an out-of-bounds read which may allow an attacker to cause memory corruption within the application. The user must open a malicious DCM file for exploitation.
- 8.8 High severity
DICOM Viewer: Out-of-bounds Write
MicroDicom DICOM Viewer is vulnerable to an out-of-bounds write which may allow an attacker to execute arbitrary code. The user must open a malicious DCM file for exploitation.
- 8.8 High severity
DICOM Viewer: Missing Authorization
An attacker could retrieve sensitive files (medical images) as well as plant new medical images or overwrite existing medical images on a MicroDicom DICOM Viewer system. User interaction is required to exploit this vulnerability.
- 8.8 High severity
DICOM Viewer: Out-of-bounds Write
MicroDicom DICOM Viewer is vulnerable to a stack-based buffer overflow, which may allow an attacker to execute arbitrary code on affected installations of DICOM Viewer. User interaction is required to exploit this vulnerability.
- 7.8 High severity
DICOM Viewer: Out-of-bounds Write
MicroDicom DICOM Viewer versions 2023.3 (Build 9342) and prior contain a lack of proper validation of user-supplied data, which could result in memory corruption within the application.
- 7.8 High severity
DICOM Viewer: Out-of-bounds Write
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