dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2017-20237

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 Industrial HiVision versions prior to 06.0.07 and 07.0.03 contains an authentication bypass vulnerability in the master service that allows unauthenticated remote attackers to execute arbitrary commands with administrative privileges. Attackers can invoke exposed interface methods over the remote service to bypass authentication and achieve remote code execution on the underlying operating system.

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 Industrial HiVision versions prior to 06.0.07 and 07.0.03 contain an authentication bypass vulnerability in the master service that allows unauthenticated remote attackers to invoke exposed interface methods, bypassing authentication to execute arbitrary commands with administrative privileges and achieve remote code execution on the underlying operating system.

MitigationUpgrade to HiVision version 06.0.07 or 07.0.03 or later to remediate the authentication bypass. If immediate upgrade is not feasible, network segmentation and restricting access to the master service port should be implemented as compensating controls.

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 HiVision is installed
    Inspect the system for HiVision installation directories (typically under C:\Program Files\HiVision or similar), or check running processes for 'HiVision' or 'master' service entries.
    Affected if HiVision software is found on the system
  2. Identify the installed HiVision version
    Check the installed version through the program's About dialog, version info in the installation directory, or Windows Programs and Features list. Compare this version number against the fixed releases (06.0.07 and 07.0.03).
    Affected if The installed version is lower than 06.0.07 or 07.0.03 (for example, any 06.0.x below 06.0.07, or any version below 06.0.00)
  3. Determine if the master service is running
    Check Windows services or running processes for the HiVision Master service. Look for a service named 'HiVision Master' or similar that handles the master service functionality.
    Affected if The master service is installed and currently running
  4. Check network exposure of the master service
    Use netstat or similar tools to identify if the master service port is listening on network interfaces. The service typically listens on a dedicated port for remote management. Verify if it binds to 0.0.0.0 or external IPs rather than localhost only.
    Affected if The master service is listening on accessible network interfaces (not localhost only)

The environment is affected if Hirschmann HiVision is installed with a version below 06.0.07 or 07.0.03 and the master service is running and network-accessible.

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 to HiVision version 06.0.07 or 07.0.03 or later to remediate the authentication bypass. If immediate upgrade is not feasible, network segmentation and restricting access to the master service port should be implemented as compensating controls.

Recommended fix High confidence

Hirschmann Industrial HiVision 06.0.07 or 07.0.03 (or later stable release)

  1. Identify the current installed version of Hirschmann Industrial HiVision
  2. Determine which version branch (06.x or 07.x) is currently in use
  3. If on 06.x branch: upgrade to version 06.0.07 or later
  4. If on 07.x branch: upgrade to version 07.0.03 or later
  5. After upgrade, verify the master service is running the patched version
  6. Test that authentication is now properly required for the master service interface

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

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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