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-9732: Memory Corruption in DCMTK

0
Medium
VulnerabilityCVE-2025-9732cvecve-2025-9732
Published: Sun Aug 31 2025 (08/31/2025, 14:02:06 UTC)
Source: CVE Database V5
Product: DCMTK

Description

A vulnerability was identified in DCMTK up to 3.6.9. This affects an unknown function in the library dcmimage/include/dcmtk/dcmimage/diybrpxt.h of the component dcm2img. Such manipulation leads to memory corruption. Local access is required to approach this attack. The name of the patch is 7ad81d69b. It is best practice to apply a patch to resolve this issue.

AI-Powered Analysis

AILast updated: 09/08/2025, 00:37:12 UTC

Technical Analysis

CVE-2025-9732 is a medium-severity memory corruption vulnerability identified in the DCMTK (DICOM Toolkit) library versions 3.6.0 through 3.6.9. The vulnerability resides in an unspecified function within the dcmimage/include/dcmtk/dcmimage/diybrpxt.h file, part of the dcm2img component responsible for image processing. Memory corruption vulnerabilities typically occur when a program writes data outside the boundaries of allocated memory, potentially leading to crashes, data corruption, or arbitrary code execution. However, this specific vulnerability requires local access with low privileges (local attack vector with low privileges) and does not require user interaction or authentication. The CVSS 4.0 base score is 4.8, reflecting a medium severity level, primarily due to the limited attack vector and privileges required. No known exploits are currently reported in the wild. The vulnerability can be mitigated by applying the patch identified by commit 7ad81d69b. DCMTK is widely used in medical imaging environments to handle DICOM files, which are standard for storing and transmitting medical images. The vulnerability could be triggered by manipulating image data processed by the vulnerable function, leading to memory corruption and potential instability or compromise of systems handling medical images.

Potential Impact

For European organizations, especially healthcare providers and medical imaging centers, this vulnerability poses a risk to the confidentiality, integrity, and availability of medical imaging data. Exploitation could lead to application crashes or potentially allow an attacker with local access to execute arbitrary code, compromising patient data or disrupting medical services. Given the critical nature of healthcare operations and strict data protection regulations such as GDPR, any compromise or downtime could have severe operational and legal consequences. Although remote exploitation is not possible, insider threats or attackers who gain local access (e.g., via compromised credentials or physical access) could leverage this vulnerability. The impact extends to any European entity using DCMTK for medical image processing, including hospitals, diagnostic labs, and medical device manufacturers integrating DCMTK in their products.

Mitigation Recommendations

European organizations should immediately identify all systems running DCMTK versions 3.6.0 through 3.6.9 and apply the official patch corresponding to commit 7ad81d69b to remediate the vulnerability. Since local access is required, organizations should strengthen internal access controls, including strict user authentication, role-based access, and monitoring of local user activities on systems processing medical images. Implementing endpoint security solutions that detect anomalous behavior or memory corruption attempts can provide additional defense. Regularly auditing and updating medical imaging software and libraries is essential to prevent exploitation of known vulnerabilities. Additionally, organizations should enforce physical security controls to prevent unauthorized local access to critical systems. Incident response plans should be updated to include detection and mitigation steps for memory corruption exploits in medical imaging environments.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
VulDB
Date Reserved
2025-08-30T14:03:15.522Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 68b45987ad5a09ad00bbef96

Added to database: 8/31/2025, 2:17:43 PM

Last enriched: 9/8/2025, 12:37:12 AM

Last updated: 10/16/2025, 6:21:50 AM

Views: 52

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