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

Machine-generated threat intelligence

AILast updated: 02/24/2026, 22:58:53 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 vulnerability resides in the function DcmByteString::makeDicomByteString within the dcmdata component (file dcmdata/libsrc/dcbytstr.cc). This function is responsible for creating DICOM byte strings, and improper handling of input data leads to memory corruption. The flaw can be triggered remotely by sending crafted DICOM data to an application using the vulnerable DCMTK versions 3.6.0 through 3.6.9. The attack requires no user interaction and no elevated privileges, making it easier to exploit in networked environments. The memory corruption could potentially be leveraged to crash the application (denial of service) or, with further exploitation, execute arbitrary code, although the CVSS vector indicates limited impact on confidentiality, integrity, and availability. The vulnerability has been patched in version 3.7.0, with the fix identified by commit 4c0e5c10079392c594d6a7abd95dd78ac0aa556a. No known exploits have been reported in the wild as of the publication date. Given DCMTK's role in medical imaging workflows, this vulnerability poses a risk to healthcare providers and systems processing DICOM files.

Potential Impact

The primary impact of CVE-2025-14607 is the potential for remote attackers to cause memory corruption in applications using vulnerable DCMTK versions, which can lead to denial of service through application crashes or potentially arbitrary code execution if exploited further. This can disrupt medical imaging workflows, delay diagnosis and treatment, and compromise patient care. Confidentiality and integrity impacts are limited but cannot be fully ruled out if an attacker achieves code execution. The vulnerability affects a critical component in healthcare IT infrastructure, increasing the risk to hospitals, clinics, and medical device manufacturers relying on DCMTK for DICOM processing. The medium CVSS score reflects moderate risk, but the healthcare sector's sensitivity elevates the operational impact. Organizations worldwide that integrate DCMTK into their imaging systems or PACS (Picture Archiving and Communication Systems) are at risk of service disruption and potential security breaches if unpatched.

Mitigation Recommendations

To mitigate CVE-2025-14607, organizations should immediately upgrade all instances of OFFIS DCMTK to version 3.7.0 or later, which contains the official patch for this vulnerability. In addition, network-level protections should be implemented to restrict access to DICOM services only to trusted and authenticated users and systems, reducing exposure to remote attacks. Employing application-layer firewalls or DICOM-aware security gateways can help detect and block malformed DICOM data that might trigger the vulnerability. Regularly audit and monitor logs for unusual activity or crashes related to DICOM processing. For environments where immediate upgrade is not feasible, consider isolating vulnerable systems from untrusted networks and applying strict network segmentation. Finally, maintain an incident response plan tailored to healthcare IT environments to quickly address potential exploitation attempts.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to 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: 2/24/2026, 10:58:53 PM

Last updated: 3/24/2026, 9:54:04 PM

Views: 143

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 for AI refresh and higher limits.

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

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses