Skip to main content
VulnerabilityPublished Updated

CVE-2024-27629: dcm2niix · Improper Encoding or Escaping of Output

Affects dcm2niixSource CVE Database V5

0

Not known to be exploited · CVSS 7.8 High : upgrade to 1.0.20240202 soon.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.0.20240202
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Jun 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade rordenlab/dcm2niix to 1.0.20240202.

Affected software

ProductAffectedFixed in
GitHubrordenlab/dcm2niixpkg:github/rordenlab/dcm2niixOther threatsAffected
  • <1.0.20240202
Fixed in
  • 1.0.20240202

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should immediately upgrade dc2niix to version 1.0.20240202 or later where the vulnerability is patched. If upgrading is not immediately feasible, restrict local access to systems running dc2niix to trusted users only and implement strict access controls and monitoring. Employ application whitelisting and endpoint detection to identify suspicious command executions. Review and harden system call usage policies and sanitize inputs in any custom scripts interacting with dc2niix outputs. Regularly audit local user privileges and remove unnecessary accounts to reduce attack surface. Additionally, isolate medical imaging processing environments from general user workstations to limit potential exploitation vectors. Maintain up-to-date backups of critical data to enable recovery in case of compromise.

Description

An issue in dc2niix before v.1.0.20240202 allows a local attacker to execute arbitrary code via the generated file name is not properly escaped and injected into a system call when certain types of compression are used.

References

Community reviews

Loading reviews…