OFFIS DCMTK dcmdata dcbytstr.cc makeDicomByteString memory corruption
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- —
- Confidentiality · integrity · availability
- Low · Low · Low
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA.
Summary
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
- Fix · CNA DCMTK (OFFIS) Fixed in 3.7.0
Vendor assessments
Timeline
- 2026-10-02 Threatist record created from CVE-2025-14607
- 2026-10-03 Alias added: GHSA-8cqp-6cwx-f84x
References
More OFFIS vulnerabilities
- TI-2026-10943 OFFIS DCMTK ofxml.cc parseFile heap-based overflow CVSS 4.0MEDIUM 5.3
- TI-2025-08922 DCMTK dcm2img diybrpxt.h memory corruption CVSS 4.0MEDIUM 4.8
- TI-2022-04568 DCMTK dcmqrscp dcmqrcnf.cc readPeerList null pointer dereference CVSS 4.0MEDIUM 4.8
- TI-2020-18990 DCMTK dcmqrscp parseQuota stack-based overflow CVSS 4.0MEDIUM 4.8
- TI-2024-22823 dcmnet in DCMTK before 3.6.9 has a segmentation fault via an invalid DIMSE message. CVSS 3.1MEDIUM 4.3
- TI-2019-16028 Out-of-bounds write in OFFIS.de DCMTK CVSS 3.1CRITICAL 9.8
Sources
- CVE-2025-14607 · CVE Program
- CVE-2025-14607 · NVD
- FIRST EPSS
- GHSA-8cqp-6cwx-f84x · GitHub Advisory Database · CC BY 4.0
- CVE-2025-14607 · Red Hat security data · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences