Skip to content
Infrastructure

CVE-2017-20237

9.3
Critical
EPSS 0.96%Apr 4, 2026

Auth bypass in Hirschmann HiVision enables unauthenticated remote code execution.

common questions

Is CVE-2017-20237 being exploited?

Not confirmed. CVE-2017-20237 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.96% probability of exploitation in the next 30 days.

How severe is CVE-2017-20237?

CVE-2017-20237 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2017-20237?

Not known from our data. No patch reference has been recorded for CVE-2017-20237, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2017-20237 affect?

CVE-2017-20237 affects Hirschmann Industrial HiVision (versions prior to 06.0.07 and 07.0.03). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2017-20237?

Upgrade to latest HiVision version per vendor guidance

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Hirschmann Industrial HiVision (versions prior to 06.0.07 and 07.0.03)
impact

Remote RCE with admin privileges via exposed remote service; could take control of the host.

action required

Immediate action required

affected versions
Belden Hirschmann Industrial HiVision
  • affected<= 06.0.06
  • affected<= 07.0.02
vendor says fixed in06.0.07, 07.0.03

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free