An attacker can exploit this by crafting a malicious DICOM file containing a deliberately mismatched NumberOfFrames field. When an application utilizing this library parses the malformed file, it triggers an out-of-bounds read on the heap. This behavior may result in a crash of the service processing the DICOM data or, in specific memory layouts, the disclosure of sensitive data residing in adjacent memory segments. Given that DCMTK is widely used in medical imaging software and PACS (Picture Archiving and Communication Systems) infrastructures, this vulnerability poses a significant risk to the confidentiality and availability of sensitive patient imaging data.

Impact

Successful exploitation allows for memory content disclosure or denial-of-service via application crash. The impact is significant for organizations operating medical imaging environments, as any downstream application integrating the vulnerable DCMTK library is susceptible to attacks via maliciously crafted DICOM files.

Recommendation

Prioritized actions focus on identifying and upgrading vulnerable library dependencies within the software supply chain:

• Audit all internal and third-party software deployments to identify applications that statically or dynamically link against DCMTK version 3.7.0 or earlier.
• Prioritize patching for internet-facing or externally accessible image processing services that ingest DICOM files from untrusted sources.
• Monitor vendor security advisories from OFFIS regarding the release of a patched version of DCMTK that implements proper buffer length validation for the ConcatenationLoader.