dbcve.org
Classic Buffer OverflowWeakness · CWE-120

CVE-2018-25237

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-03
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 HiSecOS devices versions prior to 05.3.03 contain a buffer overflow vulnerability in the HTTPS login interface when RADIUS authentication is enabled that allows remote attackers to crash the device or execute arbitrary code by submitting a password longer than 128 characters. Attackers can exploit improper bounds checking in password handling to overflow a fixed-size buffer and achieve denial of service or remote code execution.

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 HiSecOS devices prior to version 05.3.03 contain a buffer overflow in the HTTPS login interface when RADIUS authentication is enabled. The vulnerability stems from improper bounds checking that allows a password exceeding 128 characters to overflow a fixed-size buffer, potentially causing denial of service or remote code execution.

MitigationUpgrade HiSecOS to version 05.3.03 or later. As an interim measure, disable RADIUS authentication if not required, and restrict management interface access to trusted networks.

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. Identify HiSecOS version
    Access the device management interface or check the firmware version through the system information page or CLI command (e.g., 'show system' or similar). Compare the installed version number against 05.3.03.
    Affected if The device runs HiSecOS version prior to 05.3.03 (versions like 05.x.x below 05.3.03, or any version prior to the 05.x release line).
  2. Verify RADIUS authentication is enabled
    Access the device authentication settings in the management interface or check the RADIUS configuration via CLI. Look for RADIUS server configuration or authentication method settings.
    Affected if RADIUS authentication is enabled and configured on the device.
  3. Confirm HTTPS login interface is accessible
    Verify that the web-based management interface is accessible over HTTPS. The vulnerability exists in the HTTPS login component when processing RADIUS authentication.
    Affected if The device exposes an HTTPS login interface accessible from the network.

The device is affected if it runs HiSecOS versions prior to 05.3.03 AND has RADIUS authentication enabled, with the HTTPS login interface accessible over the network.

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 HiSecOS to version 05.3.03 or later. As an interim measure, disable RADIUS authentication if not required, and restrict management interface access to trusted networks.

Recommended fix High confidence

HiSecOS firmware version 05.3.03 or later

  1. 1. Identify the specific Hirschmann HiSecOS device model and current firmware version via the web interface or CLI
  2. 2. Navigate to Belden's official support portal (belden.com) and locate the firmware download section for Hirschmann industrial switches
  3. 3. Download HiSecOS firmware version 05.3.03 or later for your specific device model
  4. 4. Review Belden's firmware upgrade instructions and ensure proper backup of current configuration
  5. 5. Upload and apply the new firmware through the device's web interface or TFTP/FTP method following the documented procedure
  6. 6. After reboot, verify the new firmware version is 05.3.03 or later in the device status
  7. 7. Restore the configuration and verify normal operation
  8. 8. As an additional defense-in-depth measure, if RADIUS authentication is not required, consider disabling it in the authentication settings
Caveat Test the firmware upgrade in a non-production environment first as firmware updates may affect device behavior or feature compatibility

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
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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