LiveActive security incident?Get immediate response
CVE Record

CVE-2022-2121: OFFIS DCMTK NULL Pointer Dereference

OFFIS DCMTK's (All versions prior to 3.6.7) has a NULL pointer dereference vulnerability while processing DICOM files, which may result in a denial-of-service condition.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

DCMTK is software used to handle medical DICOM imaging files. Versions before 3.6.7 can crash when processing a malformed DICOM file. The main business risk is disruption to imaging workflows or systems that rely on DCMTK to import, convert, or validate DICOM data.

Executive priority

Treat as a high-priority availability risk for imaging workflows, especially where DICOM files cross organizational boundaries. Patch directly managed DCMTK first, then verify embedded copies through vendor support channels.

Technical view

CVE-2022-2121 is a CWE-476 NULL pointer dereference in OFFIS DCMTK before 3.6.7 during DICOM file processing. The supplied record describes a denial-of-service condition. CVSS 3.1 is 7.5, with adjacent network attack vector, high complexity, no privileges, and no user interaction.

Likely exposure

Exposure is likely where OFFIS DCMTK before 3.6.7 processes DICOM files, especially ingestion paths receiving external, partner, device, or patient imaging data. Embedded use inside other applications must be inventoried because the bundle only identifies OFFIS DCMTK, not downstream products.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. Exploitation would require reaching a DCMTK DICOM processing path with a crafted file. The public sources provided support denial of service, not confirmed compromise or weaponized exploitation.

Researcher notes

Evidence is limited to advisory-level detail. The description supports NULL pointer dereference during DICOM processing and denial of service for versions before 3.6.7. Do not infer affected downstream products, active exploitation, or broader impact beyond the cited sources.

Mitigation direction

  • Upgrade OFFIS DCMTK to 3.6.7 or later where directly managed.
  • Apply fixed Debian dcmtk packages where using Debian LTS distributions.
  • Check vendor guidance for products embedding DCMTK before assuming patch status.
  • Limit untrusted DICOM file ingestion to necessary trusted sources.
  • Prioritize systems where DICOM processing supports clinical or operational availability.

Validation and detection

  • Inventory DCMTK library and tool versions across servers, containers, and appliances.
  • Identify applications that process DICOM files using bundled or statically linked DCMTK.
  • Confirm package versions against OFFIS, CISA, or Debian security guidance.
  • Review DICOM ingestion points exposed to external partners or adjacent networks.
  • Run vendor-supported regression tests with benign DICOM sample sets after patching.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CWE-476: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookup
cve · low confidence lookup

CVE-2022-2121 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
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

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H1.65.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2022-2121Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
OFFISDCMTKunspecifiedListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-476 · source CWE mapping

NULL Pointer Dereference

NULL Pointer Dereference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.