Connectport Lts FirmwareOperating system · Digi

CVE-2024-50626

HIGH · 8.8 CVSS v3.1 Published 2024-12-09
Fix available
A fix is available. Upgrade to 1.4.12 or later.
See remediation →
93/100
Remediation priority · Urgent
No privileges 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
An issue was discovered in Digi ConnectPort LTS before 1.4.12. A Directory Traversal vulnerability exists in WebFS. This allows an attacker on the local area network to manipulate URLs to include traversal sequences, potentially leading to unauthorized access to data.

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 exists in the WebFS component of Digi ConnectPort LTS firmware versions before 1.4.12. An attacker on the local network can manipulate HTTP requests by inserting '../' sequences into URLs to traverse directories and access sensitive files outside the web root, potentially exposing configuration files, credentials, or other system data.

MitigationUpdate Digi ConnectPort LTS to firmware version 1.4.12 or later. If immediate patching is not feasible, restrict network access to the WebFS interface using firewall rules or network segmentation to limit exposure to trusted users only.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Connectport Lts FirmwareOperating system
Affected:< 1.4.12

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/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. Confirm device model is Digi ConnectPort LTS
    Access the device web interface or check the device label to verify the exact model number matches Digi ConnectPort LTS
    Affected if Device is not a Digi ConnectPort LTS unit
  2. Check firmware version
    Log into the device web interface and navigate to System > Firmware or Status page to view the installed firmware version number
    Affected if Firmware version is displayed as lower than 1.4.12 (e.g., 1.4.11, 1.4.10, etc.)
  3. Verify WebFS interface is enabled
    Check device configuration pages for WebFS or File Server settings; look for options like 'Enable WebFS' or 'Web-based File System' set to enabled
    Affected if WebFS component is enabled and accessible via HTTP
  4. Confirm network accessibility
    Attempt to reach the device web interface from a network-connected host using HTTP to the device IP address
    Affected if Device web interface is reachable from local network (attacker needs local network access)

Device is affected if it is a Digi ConnectPort LTS with firmware version before 1.4.12 and the WebFS interface is enabled and accessible on the network.

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
Upgrade available Upgrade to 1.4.12 or later
Fixed in 1.4.12
Interim mitigation

Update Digi ConnectPort LTS to firmware version 1.4.12 or later. If immediate patching is not feasible, restrict network access to the WebFS interface using firewall rules or network segmentation to limit exposure to trusted users only.

Recommended fix High confidence

Firmware version 1.4.12

  1. Download the Digi ConnectPort LTS firmware version 1.4.12 or later from the official Digi website (www.digi.com)
  2. Access the ConnectPort LTS web management interface
  3. Navigate to the firmware upgrade section in the device settings
  4. Upload and install the firmware version 1.4.12
  5. After installation, verify the firmware version has been updated and the device is functioning properly
  6. Confirm the WebFS directory traversal vulnerability is no longer exploitable
Caveat Standard firmware upgrade risks apply - ensure backup of configuration and plan for brief downtime

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

Fix this in Connectport Lts Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-50626 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