dbcve.org
Uncontrolled Resource ConsumptionWeakness · CWE-400

CVE-2024-14033

HIGH · 7.5 CVSS v3.1 Published 2026-04-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable 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
Hirschmann EagleSDV firmware prior to 05.4.02 contains a denial-of-service vulnerability in TLS session establishment. Attackers can crash the device during TLS handshake by exploiting protocol downgrades to TLS 1.0 or TLS 1.1, interrupting service availability.

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

The Hirschmann EagleSDV industrial firewall contains a denial-of-service vulnerability in its TLS implementation. Attackers can trigger a device crash by forcing TLS protocol downgrade to TLS 1.0 or TLS 1.1 during the handshake process, causing the device to become unresponsive and interrupting network services.

MitigationUpgrade Hirschmann EagleSDV firmware to version 05.4.02 or later, which addresses the TLS protocol handling vulnerability. Prior to upgrade, verify in a staging environment and schedule during a planned maintenance window.

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
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm device model is Hirschmann EagleSDV
    Identify the specific hardware model by checking the device label, web interface, or SNMP inventory. This vulnerability only affects EagleSDV devices, not other Hirschmann products.
    Affected if The device is NOT a Hirschmann EagleSDV unit - the CVE does not apply to other models.
  2. Retrieve installed firmware version
    Access the device's web interface, CLI, or management console and locate the firmware version information. Compare against the reported affected version 05.4.02.
    Affected if The installed firmware version is any version prior to 05.4.02 (for example, 05.4.00, 05.3.x, or earlier).
  3. Verify TLS protocol configuration
    Access the device's SSL/TLS settings through the web management interface or CLI. Check which TLS protocol versions are enabled or allowed for incoming connections.
    Affected if TLS 1.0 or TLS 1.1 is enabled or permitted on the device - either as the only option or as a fallback in the protocol negotiation settings.
  4. Assess network exposure
    Determine if the device management interface is accessible from untrusted networks. Review firewall rules and access control lists protecting the device.
    Affected if The device TLS ports are exposed to untrusted or external networks where an attacker could initiate the protocol downgrade attack.

A user is affected if the device is a Hirschmann EagleSDV running firmware prior to 05.4.02 AND TLS 1.0 or TLS 1.1 is enabled, with the management interface accessible to attackers who could trigger the DoS via protocol downgrade.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Hirschmann EagleSDV firmware to version 05.4.02 or later, which addresses the TLS protocol handling vulnerability. Prior to upgrade, verify in a staging environment and schedule during a planned maintenance window.

Recommended fix Moderate confidence

Hirschmann EagleSDV firmware 05.4.02

  1. Obtain the Hirschmann EagleSDV firmware version 05.4.02 from the official Belden support portal (assets.belden.com) or Hirschmann support channels
  2. Review the EagleSDV firmware upgrade documentation for specific installation instructions
  3. Upload the firmware 05.4.02 to the EagleSDV device using the device's web interface or management console
  4. Allow the device to complete the firmware upgrade process and reboot
  5. After reboot, verify the device is running firmware 05.4.02 and TLS handshake functionality is restored
  6. As an additional hardening measure, disable TLS 1.0 and TLS 1.1 protocol support in the device configuration to prevent future protocol downgrade attacks

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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