Skip to main content
CVE-2024-25386VulnerabilityPublished Updated

CVE-2024-25386: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 06:26 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Mar 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 2026-10-26.

What to do

AI-suggested

To mitigate CVE-2024-25386, organizations should implement the following specific measures: 1) Immediately restrict network access to the DICOM Connectivity Framework services, especially the format_logfile.pl endpoint, using firewalls or network segmentation to limit exposure to trusted hosts only. 2) Monitor system and application logs for unusual directory access patterns or unexpected execution of scripts related to format_logfile.pl. 3) Employ application-layer filtering or web application firewalls (WAFs) to detect and block directory traversal attempts targeting the vulnerable script. 4) Coordinate with laurelbridge for official patches or updates and apply them promptly once available. 5) Conduct thorough security assessments and penetration testing focused on directory traversal and code execution vulnerabilities within the DICOM framework. 6) Educate IT and security teams about this vulnerability to ensure rapid detection and response. 7) Consider deploying intrusion detection/prevention systems (IDS/IPS) with signatures tuned to detect exploitation attempts of this vulnerability. These targeted actions go beyond generic advice and address the specific attack vector and environment.

Description

Directory Traversal vulnerability in DICOM® Connectivity Framework by laurelbridge before v.2.7.6b allows a remote attacker to execute arbitrary code via the format_logfile.pl file.

References

Community reviews

Loading reviews…