CVE-2025-14841: NULL Pointer Dereference in OFFIS DCMTK
A flaw has been found in OFFIS DCMTK up to 3.6.9. The impacted element is the function DcmQueryRetrieveIndexDatabaseHandle::startFindRequest/DcmQueryRetrieveIndexDatabaseHandle::startMoveRequest in the library dcmqrdb/libsrc/dcmqrdbi.cc of the component dcmqrscp. This manipulation causes null pointer dereference. The attack requires local access. Upgrading to version 3.7.0 is sufficient to resolve this issue. Patch name: ffb1a4a37d2c876e3feeb31df4930f2aed7fa030. You should upgrade the affected component.
AI Analysis
Technical Summary
CVE-2025-14841 identifies a null pointer dereference vulnerability in the OFFIS DCMTK library, specifically within the DcmQueryRetrieveIndexDatabaseHandle class's startFindRequest and startMoveRequest functions, located in the dcmqrscp component's source file dcmqrdbi.cc. This flaw arises when these functions handle certain requests, leading to dereferencing a null pointer, which causes the application to crash. The vulnerability requires local access with low privileges and does not require user interaction, making it exploitable by an authenticated local user or process. The impact is primarily a denial of service, as the affected service handling DICOM query/retrieve operations can be terminated unexpectedly. DCMTK is widely used in medical imaging environments for handling DICOM data, including query/retrieve services. The vulnerability affects all versions from 3.6.0 through 3.6.9, with the issue resolved in version 3.7.0. No known exploits have been reported in the wild, and the CVSS v4.0 score is 4.8 (medium severity), reflecting the limited scope and impact. The patch identified by commit ffb1a4a37d2c876e3feeb31df4930f2aed7fa030 addresses the null pointer dereference by adding necessary checks or handling to prevent the crash. Organizations relying on DCMTK for medical imaging workflows should upgrade promptly to avoid service disruptions.
Potential Impact
The primary impact of CVE-2025-14841 is denial of service due to application crashes caused by null pointer dereference in DCMTK's query/retrieve service. For European healthcare organizations, this can disrupt critical medical imaging workflows, potentially delaying diagnosis and treatment. Although the vulnerability does not expose patient data or allow privilege escalation, service unavailability in healthcare environments can have serious operational consequences. Given the reliance on DCMTK in many European hospitals and imaging centers, unpatched systems may experience interruptions in DICOM query/retrieve operations, affecting interoperability and clinical efficiency. The requirement for local access limits remote exploitation, but insider threats or compromised local accounts could trigger the vulnerability. No known exploits in the wild reduce immediate risk, but the potential for denial of service in sensitive environments warrants timely remediation. Compliance with healthcare regulations such as GDPR and medical device directives also necessitates maintaining secure and stable systems, making patching essential.
Mitigation Recommendations
To mitigate CVE-2025-14841, affected organizations should upgrade all DCMTK installations to version 3.7.0 or later, which contains the fix for the null pointer dereference. In environments where immediate upgrade is not feasible, implementing strict access controls to limit local user permissions on systems running DCMTK can reduce exploitation risk. Monitoring and logging local access to DCMTK services should be enhanced to detect unusual activity that might trigger the vulnerability. Additionally, isolating DCMTK services within dedicated, hardened hosts or containers can limit the impact of potential crashes. Regularly reviewing and applying vendor patches and updates is critical. Healthcare organizations should also conduct impact assessments and test the upgraded versions in staging environments to ensure compatibility with existing medical imaging workflows before deployment. Finally, integrating DCMTK service availability monitoring into operational dashboards can provide early warning of service disruptions.
Affected Countries
Germany, France, United Kingdom, Italy, Spain, Netherlands, Sweden, Belgium, Switzerland, Austria
CVE-2025-14841: NULL Pointer Dereference in OFFIS DCMTK
Description
A flaw has been found in OFFIS DCMTK up to 3.6.9. The impacted element is the function DcmQueryRetrieveIndexDatabaseHandle::startFindRequest/DcmQueryRetrieveIndexDatabaseHandle::startMoveRequest in the library dcmqrdb/libsrc/dcmqrdbi.cc of the component dcmqrscp. This manipulation causes null pointer dereference. The attack requires local access. Upgrading to version 3.7.0 is sufficient to resolve this issue. Patch name: ffb1a4a37d2c876e3feeb31df4930f2aed7fa030. You should upgrade the affected component.
AI-Powered Analysis
Technical Analysis
CVE-2025-14841 identifies a null pointer dereference vulnerability in the OFFIS DCMTK library, specifically within the DcmQueryRetrieveIndexDatabaseHandle class's startFindRequest and startMoveRequest functions, located in the dcmqrscp component's source file dcmqrdbi.cc. This flaw arises when these functions handle certain requests, leading to dereferencing a null pointer, which causes the application to crash. The vulnerability requires local access with low privileges and does not require user interaction, making it exploitable by an authenticated local user or process. The impact is primarily a denial of service, as the affected service handling DICOM query/retrieve operations can be terminated unexpectedly. DCMTK is widely used in medical imaging environments for handling DICOM data, including query/retrieve services. The vulnerability affects all versions from 3.6.0 through 3.6.9, with the issue resolved in version 3.7.0. No known exploits have been reported in the wild, and the CVSS v4.0 score is 4.8 (medium severity), reflecting the limited scope and impact. The patch identified by commit ffb1a4a37d2c876e3feeb31df4930f2aed7fa030 addresses the null pointer dereference by adding necessary checks or handling to prevent the crash. Organizations relying on DCMTK for medical imaging workflows should upgrade promptly to avoid service disruptions.
Potential Impact
The primary impact of CVE-2025-14841 is denial of service due to application crashes caused by null pointer dereference in DCMTK's query/retrieve service. For European healthcare organizations, this can disrupt critical medical imaging workflows, potentially delaying diagnosis and treatment. Although the vulnerability does not expose patient data or allow privilege escalation, service unavailability in healthcare environments can have serious operational consequences. Given the reliance on DCMTK in many European hospitals and imaging centers, unpatched systems may experience interruptions in DICOM query/retrieve operations, affecting interoperability and clinical efficiency. The requirement for local access limits remote exploitation, but insider threats or compromised local accounts could trigger the vulnerability. No known exploits in the wild reduce immediate risk, but the potential for denial of service in sensitive environments warrants timely remediation. Compliance with healthcare regulations such as GDPR and medical device directives also necessitates maintaining secure and stable systems, making patching essential.
Mitigation Recommendations
To mitigate CVE-2025-14841, affected organizations should upgrade all DCMTK installations to version 3.7.0 or later, which contains the fix for the null pointer dereference. In environments where immediate upgrade is not feasible, implementing strict access controls to limit local user permissions on systems running DCMTK can reduce exploitation risk. Monitoring and logging local access to DCMTK services should be enhanced to detect unusual activity that might trigger the vulnerability. Additionally, isolating DCMTK services within dedicated, hardened hosts or containers can limit the impact of potential crashes. Regularly reviewing and applying vendor patches and updates is critical. Healthcare organizations should also conduct impact assessments and test the upgraded versions in staging environments to ensure compatibility with existing medical imaging workflows before deployment. Finally, integrating DCMTK service availability monitoring into operational dashboards can provide early warning of service disruptions.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulDB
- Date Reserved
- 2025-12-17T17:45:16.548Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 69434d1ff4a1ba78f2c14a13
Added to database: 12/18/2025, 12:38:55 AM
Last enriched: 12/25/2025, 1:19:22 AM
Last updated: 2/5/2026, 11:54:31 PM
Views: 88
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-23623: CWE-285: Improper Authorization in CollaboraOnline online
MediumCVE-2025-32393: CWE-770: Allocation of Resources Without Limits or Throttling in Significant-Gravitas AutoGPT
HighCVE-2026-24302: CWE-284: Improper Access Control in Microsoft Azure ARC
HighCVE-2026-24300: CWE-284: Improper Access Control in Microsoft Azure Front Door
CriticalCVE-2026-21532: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in Microsoft Azure Functions
HighActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
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.