CVE-2024-50628
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 the web services of Digi ConnectPort LTS before 1.4.12. It allows an attacker on the local area network to achieve unauthorized manipulation of resources, which may lead to remote code execution when combined with other issues.
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 confidenceDigi ConnectPort LTS web services before version 1.4.12 contain a vulnerability allowing local network attackers to perform unauthorized manipulation of resources. The CVSS 8.8 score indicates high severity, and the description notes this can potentially lead to remote code execution when combined with other issues, suggesting the vulnerability may involve command injection, improper authentication bypass, or similar exploitation vector in the device's web interface.
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 device modelLocate the physical device or check network inventory to confirm the device is a Digi ConnectPort LTS gatewayAffected if The device is not a Digi ConnectPort LTS model, then this CVE does not apply
-
Determine the installed firmware versionAccess the device's web interface, CLI, or administrative console and locate the firmware version information, typically found in the System, Status, or About sectionAffected if The firmware version is lower than 1.4.12 (for example, 1.4.10, 1.3.x, or earlier)
-
Verify the web services component is enabledCheck the device configuration or settings to confirm the web interface or web services are currently enabled and accessibleAffected if The web services component is enabled and reachable on the network
The device is affected if it is a Digi ConnectPort LTS running firmware version prior to 1.4.12 and has its web services component enabled and accessible.
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 firmware to version 1.4.12 or later. Additionally, restrict network access to the device's web services to trusted internal networks only, as the attack vector is described as local area network-based.
1.4.12 or later
- Download the firmware version 1.4.12 or later from the official Digi website (www.digi.com)
- Access the ConnectPort LTS web management interface using an administrative account
- Navigate to the Firmware Update or System Maintenance section
- Upload the downloaded firmware file (1.4.12 or later)
- Confirm the firmware update and wait for the device to reboot
- Verify the firmware version has been updated successfully
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-50628 — 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-50628 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