Security readout for executives and security teams
Plain-English summary
DCMTK versions 3.6.3 and earlier can overflow memory while processing certain DICOM data. The reported impact includes confirmed denial of service and possible code execution. Organizations that convert, import, or otherwise process DICOM files with DCMTK should treat this as a serious file-processing risk.
Executive priority
Prioritize remediation where DCMTK processes DICOM files from outside trusted clinical or operational boundaries. The main business risk is service disruption, with possible code execution reported but not fully scored in the provided sources.
Technical view
The reported vulnerable component is DcmRLEDecoder::decompress() in dcrledec.h. The attack vector is DICOM file processing, including DICOM-to-image conversion. The source bundle states the fix is DCMTK 3.6.4 after commit 40917614e, but provides no CVSS score or CWE mapping.
Likely exposure
Exposure is most likely in applications, services, or imaging workflows that use DCMTK 3.6.3 or earlier to parse, decode, convert, or ingest DICOM files, especially files from external or semi-trusted sources.
Exploitation context
The bundle does not cite active exploitation, and KEV status is false. Exploitation would require a crafted DICOM processing path reaching the vulnerable RLE decompression code. Public evidence in the bundle supports denial of service and possible code execution, but not weaponization status.
Researcher notes
Key unknowns remain: no CVSS vector, no CWE assignment, and no cited active exploitation. Focus validation on version identification, bundled dependencies, and DICOM processing paths that can reach DcmRLEDecoder::decompress().
Mitigation direction
- Upgrade DCMTK to version 3.6.4 or later where feasible.
- Confirm downstream products are not bundling DCMTK 3.6.3 or earlier.
- Restrict DICOM ingestion to trusted sources until vendor fixes are confirmed.
- Check vendor guidance for product-specific patches or compensating controls.
Validation and detection
- Inventory applications and packages that include or link against DCMTK.
- Verify the deployed DCMTK version is 3.6.4 or later.
- Review DICOM conversion and ingestion services for external file exposure.
- Confirm Fedora or vendor advisory updates are applied where relevant.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
Execution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2019-1010228 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://support.dcmtk.org/redmine/issues/858CVE reference · x_refsource_MISC
- FEDORA-2019-12650a34d8CVE reference · vendor-advisory, x_refsource_FEDORA
- FEDORA-2019-4349fc0afbCVE reference · vendor-advisory, x_refsource_FEDORA
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
