CVE-2024-28130VulnerabilityPublished 23 Apr 2024Updated 4 Nov 2025

CVE-2024-28130: OFFIS DCMTK · Incorrect Type Conversion or Cast

Affects OFFIS DCMTKSource CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 1.6% chance of exploitation in 30 days – higher than 76% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 23 Apr 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Debiandebian/dcmtk`pkg:deb/debian/dcmtk`Other threats	Affected =3.6.8	Fixed in–

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

AI-suggested

1. Monitor OFFIS and related security advisories closely for the release of official patches addressing CVE-2024-28130 and apply them promptly. 2. Until patches are available, implement strict input validation and sanitization on all DICOM files before processing, ideally using whitelisting approaches to reject malformed or suspicious files. 3. Employ sandboxing or containerization techniques to isolate the DCMTK processing environment, limiting the potential impact of arbitrary code execution. 4. Restrict network access to systems processing DICOM files, especially from untrusted sources, and enforce strict access controls on PACS and imaging devices. 5. Conduct regular security audits and penetration tests focusing on medical imaging infrastructure to detect potential exploitation attempts. 6. Educate healthcare IT staff about this vulnerability and encourage vigilance when handling external imaging data. 7. Consider deploying network-level detection tools capable of identifying anomalous DICOM file traffic or malformed file patterns associated with this vulnerability.

Description

An incorrect type conversion vulnerability exists in the DVPSSoftcopyVOI_PList::createFromImage functionality of OFFIS DCMTK 3.6.8. A specially crafted malformed file can lead to arbitrary code execution. An attacker can provide a malicious file to trigger this vulnerability.

Impact

The primary impact of CVE-2024-28130 on European organizations lies in the healthcare sector, where DCMTK is commonly used for processing medical imaging data. Exploitation could lead to arbitrary code execution, potentially resulting in denial of service or unauthorized control over systems handling sensitive patient data. This could disrupt medical workflows, delay diagnostics and treatment, and compromise patient safety. Although confidentiality and integrity impacts are not explicitly stated, the ability to execute arbitrary code could be leveraged for further attacks, including data exfiltration or ransomware deployment. The lack of required privileges or user interaction means attackers could exploit this vulnerability remotely by delivering malicious DICOM files via network vectors such as PACS servers or medical imaging devices connected to hospital networks. Given the critical nature of healthcare services and strict regulatory requirements in Europe (e.g., GDPR, NIS Directive), exploitation could also lead to significant legal and reputational consequences.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Nov 2025, 01:33 UTC

WeaknessesCWE-704

Technical details

References

Community reviews

Related threats