CVE-2024-50627
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 Privilege Escalation vulnerability exists in the file upload feature. It allows an attacker on the local area network (with specific permissions) to upload and execute malicious files, potentially leading to unauthorized system access.
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 confidenceA privilege escalation vulnerability in Digi ConnectPort LTS versions before 1.4.12 allows an authenticated attacker on the local network to exploit the file upload feature. The application fails to properly validate uploaded files, enabling the attacker to upload and execute malicious files, thereby gaining unauthorized system access.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed firmware versionAccess the Digi ConnectPort LTS admin interface and navigate to System > Firmware or Status page to view the current firmware version. Alternatively, check via CLI using 'show version' or 'get firmware version' command if SSH/telnet access is available.Affected if The installed firmware version is lower than 1.4.12 (for example, 1.4.10, 1.3.x, or earlier).
-
Verify if the file upload feature is enabledIn the admin web interface, navigate to Administration > File Management or similar section. Check if file upload functionality is available or enabled for authenticated users.Affected if The file upload feature is exposed and accessible to authenticated users on the local network.
-
Inspect authentication configuration for file operationsReview user account permissions and access control settings in the admin interface under Users, Access Control, or Security settings. Determine which authenticated users have permission to upload files.Affected if Authenticated users with file upload permissions exist on the device, particularly non-administrator accounts.
The environment is affected if the Digi ConnectPort LTS firmware version is below 1.4.12 and the file upload feature is accessible to authenticated users on the local 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
Update Digi ConnectPort LTS to firmware version 1.4.12 or later, which contains the fix for the insecure file upload handling. Restrict network access to trusted personnel and follow least-privilege principles for user accounts.
Firmware version 1.4.12
- Navigate to the official Digi support website and locate the ConnectPort LTS firmware download page
- Download firmware version 1.4.12 or later from the official Digi website
- Access the ConnectPort LTS web management interface using an administrator account
- Navigate to the Administration or System Maintenance section of the web interface
- Locate the Firmware Upgrade or Update option
- Upload the downloaded firmware file (1.4.12) and initiate the upgrade process
- Wait for the firmware upload and installation to complete - do not power off the device during this process
- After the device reboots, verify the firmware version has been updated to 1.4.12 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.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,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-50627 — 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-50627 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