CVE-2024-50625
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 · uneditedAn issue was discovered in Digi ConnectPort LTS before 1.4.12. A vulnerability in the file upload handling of a web application allows manipulation of file paths via POST requests. This can lead to arbitrary file uploads within specific directories, potentially enabling privilege escalation when combined with other vulnerabilities.
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 · moderate confidenceA path traversal vulnerability in the web application's file upload functionality allows attackers to manipulate file paths via POST requests, enabling arbitrary file uploads within specific directories on Digi ConnectPort LTS devices before version 1.4.12. This can lead to privilege escalation when chained with other vulnerabilities.
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< 1.4.12CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm device model is Digi ConnectPort LTSAccess the device web interface or use SNMP/CLI to retrieve the device model identifier. Look for 'ConnectPort LTS' in the system information or device status page.Affected if The device is not a Digi ConnectPort LTS (the vulnerability only affects this specific product line)
-
Check installed firmware versionNavigate to the device web interface System or Administration section to view the firmware version. Alternatively, access the device via CLI and run 'show version' or 'get version' command.Affected if The firmware version is lower than 1.4.12 (versions 1.4.12 and later contain the fix)
-
Verify web application is accessibleAttempt to reach the device's web interface over HTTP/HTTPS on the configured management port (typically 80 or 443). Confirm the login page or status page loads.Affected if The web application interface is exposed and reachable on the network
-
Confirm file upload functionality is enabledLog into the web interface and look for file upload, firmware upgrade, configuration import, or similar features in the Administration or System settings menus.Affected if File upload or firmware upgrade features are accessible and enabled for authenticated users
A user is affected if they have a Digi ConnectPort LTS device running firmware version below 1.4.12 with the web interface and its file upload feature accessible on the network.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.4.12
Upgrade Digi ConnectPort LTS to version 1.4.12 or later to remediate the vulnerability. If immediate upgrading is not feasible, restrict or disable the web application's file upload feature and implement file upload validation controls.
Firmware 1.4.12 or later
- Check the current firmware version on the Digi ConnectPort LTS device via the web interface or console
- Navigate to Digi's official support page at www.digi.com and locate the ConnectPort LTS firmware download section
- Download firmware version 1.4.12 or later for your specific ConnectPort LTS model
- Access the device's web management interface and navigate to the firmware upgrade section
- Upload and install the downloaded firmware file following the on-screen instructions
- After the device reboots, verify the firmware has been updated by checking the version number in the web interface
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-50625 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-50625 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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