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/13/2025, 13:28:02 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. The flaw resides in the function DcmByteString::makeDicomByteString within the dcmdata component (file dcmdata/libsrc/dcbytstr.cc). This function improperly handles certain input data, leading to memory corruption when processing crafted DICOM byte strings. The vulnerability can be exploited remotely without requiring authentication or user interaction, making it a network-exploitable flaw. The CVSS 4.0 base score of 5.3 reflects a medium severity, considering the attack vector is network-based with low attack complexity and no privileges required, but with limited impact on confidentiality, integrity, and availability. The vulnerability does not require user interaction and affects all DCMTK versions from 3.6.0 through 3.6.9. The issue was patched in version 3.7.0, with the fix identified by commit 4c0e5c10079392c594d6a7abd95dd78ac0aa556a. While no known exploits are currently in the wild, the potential for denial of service or limited code execution exists if exploited. Given DCMTK's role in medical imaging workflows, successful exploitation could disrupt healthcare operations or compromise patient data integrity.

Potential Impact

For European organizations, particularly those in the healthcare sector, this vulnerability poses a risk to the confidentiality, integrity, and availability of medical imaging data. Exploitation could lead to denial of service conditions, interrupting diagnostic workflows and potentially delaying critical patient care. Although the impact on confidentiality and integrity is rated low, any disruption in medical imaging systems can have serious operational consequences. The vulnerability's remote exploitability without authentication increases the risk of attacks originating from external threat actors. Healthcare providers using DCMTK in PACS (Picture Archiving and Communication Systems) or other medical imaging software are especially vulnerable. Additionally, regulatory compliance frameworks such as GDPR and medical device regulations in Europe emphasize the protection of patient data and system availability, making timely remediation critical to avoid legal and reputational repercussions.

Mitigation Recommendations

European healthcare organizations should prioritize upgrading all instances of DCMTK to version 3.7.0 or later to apply the official patch. Network segmentation should be employed to isolate medical imaging systems from untrusted networks, reducing exposure to remote attacks. Implement strict access controls and monitor network traffic for anomalous activity targeting DICOM services. Employ application-layer firewalls or DICOM-aware security gateways to filter and validate incoming DICOM data streams. Regularly audit and update all medical imaging software dependencies to ensure vulnerabilities are promptly addressed. Additionally, incorporate vulnerability scanning and penetration testing focused on medical imaging infrastructure to detect potential exploitation attempts. Establish incident response plans specific to medical device and imaging system compromises to minimize operational impact.

Need more detailed analysis?Get Pro

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/13/2025, 1:28:02 PM

Last updated: 12/14/2025, 4:09:31 AM

Views: 18

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 enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats