Security readout for executives and security teams
Plain-English summary
DCMTK can receive medical imaging files. In vulnerable versions before 3.6.7, a remote attacker on an adjacent network could abuse path handling to place DICOM files in unintended directories, potentially leading to serious system compromise. This matters most where DCMTK SCP services receive untrusted DICOM traffic.
Executive priority
Prioritize remediation for healthcare and imaging environments where DICOM receivers are network-accessible. Treat this as high urgency for exposed SCP services because impact may include arbitrary file placement and possible remote code execution.
Technical view
CVE-2022-2119 is a CWE-22 path traversal issue in OFFIS DCMTK SCP before 3.6.7. The CVSS 3.1 vector is 7.5 high: adjacent attack vector, high complexity, no privileges, no user interaction, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is likely in medical imaging, PACS, research, or healthcare systems running DCMTK SCP versions before 3.6.7. Risk is higher where DICOM receiver services are reachable from partner, modality, clinical, or less-trusted adjacent networks.
Exploitation context
The source bundle does not show CISA KEV listing or public active exploitation. The CVSS vector indicates exploitation requires adjacent network access and high attack complexity, but no credentials or user interaction.
Researcher notes
The affected product is OFFIS DCMTK before 3.6.7. The bundle does not provide exploit details, confirmed exploitation, or precise vulnerable configurations beyond SCP path traversal. Validate exposure by version, service role, and network reachability.
Mitigation direction
- Upgrade OFFIS DCMTK to version 3.6.7 or later where applicable.
- Apply relevant Debian LTS packages if DCMTK is installed from Debian repositories.
- Restrict DICOM SCP exposure to trusted systems and clinical network segments.
- Review OFFIS, CISA, and distribution guidance for deployment-specific mitigations.
- Avoid internet exposure for DICOM receiver services unless explicitly required.
Validation and detection
- Inventory systems running DCMTK or applications bundling DCMTK SCP functionality.
- Confirm installed DCMTK versions are 3.6.7 or later.
- Identify reachable DICOM SCP services and their network trust boundaries.
- Review package advisories for Debian-managed installations.
- Check logs and file locations for unexpected DICOM writes outside expected storage paths.
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.
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution 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 lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2022-2119 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
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
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 vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H1.65.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://www.cisa.gov/uscert/ics/advisories/icsma-22-174-01CVE reference · x_refsource_MISC
- https://lists.debian.org/debian-lts-announce/2025/06/msg00025.htmlCVE reference
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.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.