# CVE-2017-20237: Hirschmann Industrial HiVision Authentication Bypass Remote Code Execution

> Unauthenticated attackers can bypass authentication in Hirschmann Industrial HiVision to execute arbitrary commands with administrative privileges.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Apr 2026
- **Updated:** 14 May 2026
- **Also known as:** GHSA-27cv-h3wc-24hg

## What is CVE-2017-20237?

CVE-2017-20237 is a critical authentication bypass vulnerability in Belden Hirschmann Industrial HiVision, published on 3 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2017-20237?


## How do I fix CVE-2017-20237?

No fix has been published for CVE-2017-20237 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-20237 being exploited?

There is no known exploitation of CVE-2017-20237 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-20237 and fix it if it is affected.

What it is: CVE-2017-20237 is a critical authentication bypass vulnerability in Belden Hirschmann Industrial HiVision, published on 3 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-20237 in the wild and no public exploit code.

Affected product: Belden Hirschmann Industrial HiVision. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-20237/ (Markdown: https://insights.sbomify.com/CVE-2017-20237/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-20237
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-20237
- OSV: https://osv.dev/vulnerability/CVE-2017-20237

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-20237/
Summaries are generated and may contain mistakes; the official description above is the record.