VulnerabilityPublished 21 Mar 2025Updated 3 Nov 2025

CVE-2025-2581: xmedcon · Integer Underflow

Affects xmedconSource CVE Database V5

Compare

Not known to be exploited · CVSS 5.3 Medium · fixed in 0.25.1 : update xmedcon when convenient.

Data as of 29 Oct 2026, 14:41 UTC

CVSS 4.0 base score

5.3Medium

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

EPSS: 0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 0.25.1

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: Passive
Vulnerable system confidentiality: None
Vulnerable system integrity: None
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

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

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, 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: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 21 Mar 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 29 Oct 2026.

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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity 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/xmedcon`pkg:deb/debian/xmedcon`Other threats	Affected =0.25.0	Fixed in–

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

AI-suggested

The primary mitigation is to upgrade xmedcon to version 0.25.1, which contains the patch addressing the integer underflow issue. Organizations should implement strict controls on the sources of DICOM files, validating and sanitizing inputs before processing to reduce exposure to maliciously crafted files. Deploy network segmentation and access controls to limit exposure of xmedcon systems to untrusted networks. Employ endpoint protection solutions capable of detecting anomalous behavior or memory corruption attempts in medical imaging applications. Conduct user awareness training for healthcare staff to recognize suspicious files and avoid opening untrusted DICOM files. Regularly audit and monitor logs for unusual application crashes or errors related to DICOM processing. In environments where immediate patching is not feasible, consider isolating vulnerable systems and restricting file transfers to trusted channels only. Collaborate with medical device and software vendors to ensure timely updates and vulnerability disclosures.

Description

A vulnerability has been found in xmedcon 0.25.0 and classified as problematic. Affected by this vulnerability is the function malloc of the component DICOM File Handler. The manipulation leads to integer underflow. The attack can be launched remotely. Upgrading to version 0.25.1 is able to address this issue. It is recommended to upgrade the affected component.

Impact

For European organizations, particularly those in the healthcare sector, this vulnerability could disrupt medical imaging workflows by causing application crashes or memory corruption when processing DICOM files. This may lead to denial of service conditions affecting diagnostic capabilities and patient care. Although no known exploits exist currently, the ease of remote exploitation without authentication means attackers could potentially target vulnerable systems via crafted DICOM files, possibly distributed through phishing or compromised medical data exchanges. Confidentiality risks are moderate since memory corruption could be leveraged to execute arbitrary code or access sensitive patient data, though this is less certain without confirmed exploit code. The availability impact is more immediate, as service interruptions in medical imaging can delay diagnosis and treatment. European healthcare providers using xmedcon 0.25.0 should consider this a significant operational risk, especially in hospitals and clinics with high volumes of DICOM file processing. The vulnerability also raises compliance concerns under GDPR if patient data integrity or availability is compromised.

References

Community reviews

Loading reviews…