dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2024-14034

CRITICAL · 9.8 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 →
100/100
Remediation priority · Urgent
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 HiEOS devices versions prior to 01.1.00 contain an authentication bypass vulnerability in the HTTP(S) management module that allows unauthenticated remote attackers to gain administrative access by sending specially crafted HTTP(S) requests. Attackers can exploit improper authentication handling to obtain elevated privileges and perform unauthorized actions including configuration download or upload and firmware modification.

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

Hirschmann HiEOS devices versions prior to 01.1.00 contain an authentication bypass vulnerability in the HTTP(S) management module. Unauthenticated remote attackers can gain administrative access by sending specially crafted HTTP(S) requests, enabling configuration download/upload and firmware modification.

MitigationUpgrade HiEOS devices to version 01.1.00 or later. Until patched, restrict management interface access to trusted networks using firewall rules or VLAN segmentation.

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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 checks

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

  1. Confirm Hirschmann HiEOS device in use
    Identify the device model and confirm it runs the HiEOS firmware. Check device documentation, web interface, or system information pages.
    Affected if Device is a Hirschmann HiEOS device and version is below 01.1.00
  2. Check installed HiEOS version
    Access the device management interface or use CLI commands (such as 'show version' or 'system info') to retrieve the running HiEOS version number.
    Affected if Version is below 01.1.00 (for example, 01.0.x or earlier)
  3. Verify HTTP(S) management interface is enabled
    Check device configuration for HTTP or HTTPS management interface settings. Look for web-based management, web UI, or remote management options in the device settings.
    Affected if HTTP or HTTPS management interface is enabled and accessible
  4. Assess network exposure of management interface
    Determine if the management interface is reachable from untrusted networks. Check firewall rules, VLAN configuration, or access control lists that govern access to the device web interface.
    Affected if Management interface is exposed to untrusted or external networks without proper access controls

The environment is affected if the device runs HiEOS version below 01.1.00 AND the HTTP(S) management interface is enabled and reachable by attackers.

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 HiEOS devices to version 01.1.00 or later. Until patched, restrict management interface access to trusted networks using firewall rules or VLAN segmentation.

Recommended fix Moderate confidence

Hirschmann HiEOS firmware version 01.1.00 or later

  1. Identify the specific Hirschmann HiEOS device model in your environment
  2. Check the current firmware version by accessing the device management interface or using CLI commands
  3. Review Belden/Hirschmann's official firmware release notes for version 01.1.00 or later to confirm the fix is included
  4. Schedule a maintenance window as firmware upgrades may cause brief service interruption
  5. Download the firmware version 01.1.00 or later from Belden's official support portal (assets.belden.com)
  6. Follow the vendor's official firmware upgrade procedure documented in the HiEOS administration guide
  7. After upgrade, verify the new version is installed and the HTTP(S) management interface is functioning correctly
  8. Test that authentication is now properly enforced by confirming unauthenticated requests are rejected
Caveat Review vendor release notes for any configuration or feature changes between current version and 01.1.00; test in staging environment before production deployment

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-14034 — 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-14034 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