dbcve.org
Path TraversalWeakness · CWE-22

CVE-2024-25386

HIGH · 8.8 CVSS v3.1 Published 2024-03-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A directory traversal vulnerability in the format_logfile.pl script of DICOM Connectivity Framework versions before 2.7.6b allows remote attackers to manipulate file path references to access files outside the intended directory, potentially leading to arbitrary code execution.

MitigationUpgrade to DICOM Connectivity Framework v2.7.6b or later. If immediate patching is not feasible, disable or remove the format_logfile.pl script and implement network segmentation to limit exposure of the affected service.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify DICOM Connectivity Framework installation
    Locate the DICOM Connectivity Framework installation directory and check for version identifiers in product documentation, installation logs, or version files typically found in the application root directory
    Affected if The installed version cannot be determined or is found to be earlier than 2.7.6b
  2. Locate format_logfile.pl script
    Search for the format_logfile.pl script within the DICOM Connectivity Framework installation directory, typically in a scripts, tools, or bin subdirectory
    Affected if The format_logfile.pl script exists in the installation
  3. Verify script accessibility
    Check file permissions and network exposure of the format_logfile.pl script to determine if it is executable and accessible remotely or by untrusted users
    Affected if The script has execute permissions and is accessible to unauthorized users or exposed over the network
  4. Compare version to affected range
    Use the identified version of DICOM Connectivity Framework and compare it against the vulnerable range: versions before 2.7.6b
    Affected if The installed version is lower than 2.7.6b (e.g., 2.7.5, 2.7.0, or any 2.x version prior to 2.7.6b)

A user is affected if the DICOM Connectivity Framework version is identified as lower than 2.7.6b AND the format_logfile.pl script exists and is accessible in the environment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to DICOM Connectivity Framework v2.7.6b or later. If immediate patching is not feasible, disable or remove the format_logfile.pl script and implement network segmentation to limit exposure of the affected service.

Recommended fix Moderate confidence

v2.7.6b (or later) of DICOM Connectivity Framework by laurelbridge

  1. 1. Back up the current DICOM Connectivity Framework installation and all associated configuration files.
  2. 2. Obtain the fixed version (v2.7.6b or later) from the official laurelbridge vendor (laurelbridge.com).
  3. 3. Uninstall or remove the existing vulnerable version of the DICOM Connectivity Framework.
  4. 4. Install the patched version v2.7.6b following the vendor's installation documentation.
  5. 5. Restore any custom configuration settings from the backup.
  6. 6. Restart all DICOM services to load the updated software.
  7. 7. Verify the installation by confirming the version number matches v2.7.6b or later.
  8. 8. Test that the format_logfile.pl functionality works correctly with the patched version.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-25386 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-25386 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data