CVE-2024-14028
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 · uneditedUse after free vulnerability in Softing smartLink HW-DP or smartLink HW-PN webserver allows HTTP DoS. This issue affects: smartLink HW-DP: through 1.31 smartLink HW-PN: before 1.02.
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 confidenceUse-after-free vulnerability in the webserver component of Softing smartLink HW-DP (through v1.31) and smartLink HW-PN (before v1.02) industrial gateways allows remote attackers to cause HTTP denial of service via specially crafted HTTP requests.
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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/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 modelAccess the device web interface, CLI, or management console and confirm the exact model is either smartLink HW-DP or smartLink HW-PN industrial gatewayAffected if Device is a Softing smartLink HW-DP or smartLink HW-PN gateway
-
Retrieve the installed firmware versionLocate the firmware version information in the device web interface system status page, or via CLI command (consult device documentation for exact command)Affected if Unable to determine the firmware version from the device
-
Check smartLink HW-DP versionFor smartLink HW-DP devices, compare your installed firmware version against the affected range: any version through v1.31Affected if smartLink HW-DP with firmware v1.31 or any earlier version
-
Check smartLink HW-PN versionFor smartLink HW-PN devices, compare your installed firmware version against the affected range: versions before v1.02Affected if smartLink HW-PN with firmware version v1.01, v1.00, or earlier
-
Verify webserver is exposedConfirm the webserver component is accessible on the device (typically ports 80 or 443) and not disabled or restricted via access controlsAffected if Webserver is accessible and device firmware is in an affected version range
Device is affected if it is a Softing smartLink HW-DP with firmware v1.31 or earlier, or smartLink HW-PN with firmware before v1.02, and the webserver component is 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.
From vendor dataUpdate firmware to vendor-supplied patched versions for both smartLink HW-DP and smartLink HW-PN devices; if no patch available, consider network segmentation to limit webserver exposure.
- Consultation4.0 h
- Implementation4.0 h
- Testing3.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,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-14028 — 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-14028 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