Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-14607: Memory Corruption in OFFIS DCMTK

0
Medium
VulnerabilityCVE-2025-14607cvecve-2025-14607
Published: Sat Dec 13 2025 (12/13/2025, 13:02:07 UTC)
Source: CVE Database V5
Vendor/Project: OFFIS
Product: DCMTK

Description

A vulnerability was detected in OFFIS DCMTK up to 3.6.9. Affected by this issue is the function DcmByteString::makeDicomByteString of the file dcmdata/libsrc/dcbytstr.cc of the component dcmdata. The manipulation results in memory corruption. The attack can be launched remotely. Upgrading to version 3.7.0 can resolve this issue. The patch is identified as 4c0e5c10079392c594d6a7abd95dd78ac0aa556a. You should upgrade the affected component.

AI-Powered Analysis

AILast updated: 12/20/2025, 14:12:36 UTC

Technical Analysis

CVE-2025-14607 is a memory corruption vulnerability identified in the OFFIS DCMTK library, a widely used open-source toolkit for handling DICOM (Digital Imaging and Communications in Medicine) files, which are standard in medical imaging. The vulnerability resides in the function DcmByteString::makeDicomByteString within the dcmdata component (file dcbytstr.cc). This function improperly handles certain byte string manipulations, leading to memory corruption when processing crafted DICOM data. The flaw can be triggered remotely by an attacker sending malicious DICOM data to an application using vulnerable DCMTK versions (3.6.0 through 3.6.9). No user interaction or elevated privileges are required, increasing the risk profile. The CVSS 4.0 base score is 5.3 (medium severity), reflecting network attack vector, low complexity, no privileges or user interaction needed, but limited impact on confidentiality, integrity, and availability. The vulnerability could cause application crashes or potentially allow limited code execution depending on the context of use. The issue is fixed in DCMTK version 3.7.0, with the patch identified by commit 4c0e5c10079392c594d6a7abd95dd78ac0aa556a. No known exploits have been reported in the wild yet, but the critical role of DCMTK in medical imaging systems makes this a significant concern for healthcare providers and software vendors integrating DCMTK.

Potential Impact

The primary impact of CVE-2025-14607 is on the availability and integrity of medical imaging systems that rely on the DCMTK library for processing DICOM files. Successful exploitation could lead to application crashes (denial of service), disrupting clinical workflows and delaying diagnosis or treatment. In some scenarios, memory corruption might be leveraged for limited code execution, potentially allowing attackers to manipulate or exfiltrate sensitive patient data, impacting confidentiality. European healthcare organizations are particularly vulnerable due to the widespread use of DICOM standards and DCMTK in medical imaging devices, PACS (Picture Archiving and Communication Systems), and radiology software. Disruptions could affect hospitals, diagnostic centers, and telemedicine services, leading to patient safety risks and regulatory compliance issues under GDPR and medical device regulations. The remote attack vector and lack of required user interaction increase the threat level. Although no active exploits are known, the vulnerability could be targeted by threat actors aiming to disrupt healthcare services or steal sensitive health information.

Mitigation Recommendations

1. Immediate upgrade of all DCMTK deployments to version 3.7.0 or later to apply the official patch. 2. For organizations unable to upgrade immediately, implement network-level controls to restrict access to systems processing DICOM data, including segmentation and firewall rules limiting inbound connections to trusted sources. 3. Employ input validation and sanitization on DICOM data where possible, using application-layer filters or proxy solutions to detect malformed or suspicious DICOM files. 4. Monitor logs and system behavior for signs of crashes or anomalous activity related to DICOM processing components. 5. Coordinate with medical device vendors and PACS providers to ensure their products incorporate the patched DCMTK version or equivalent mitigations. 6. Conduct security awareness and incident response exercises focused on medical imaging infrastructure. 7. Maintain up-to-date backups and recovery plans for critical imaging systems to minimize downtime in case of exploitation.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
VulDB
Date Reserved
2025-12-12T19:54:18.039Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 693d666c38f0070a6570c1da

Added to database: 12/13/2025, 1:13:16 PM

Last enriched: 12/20/2025, 2:12:36 PM

Last updated: 2/7/2026, 9:40:43 AM

Views: 95

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats