dbcve.org
Industrial Gateway ServerApplication · Ge

CVE-2020-27263

CRITICAL · 9.1 CVSS v3.1 Published 2021-01-14
Fix available
A fix is available. Upgrade to after 6.9 or later.
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
KEPServerEX: v6.0 to v6.9, ThingWorx Kepware Server: v6.8 and v6.9, ThingWorx Industrial Connectivity: All versions, OPC-Aggregator: All versions, Rockwell Automation KEPServer Enterprise, GE Digital Industrial Gateway Server: v7.68.804 and v7.66, Software Toolbox TOP Server: All 6.x versions, are vulnerable to a heap-based buffer overflow. Opening a specifically crafted OPC UA message could allow an attacker to crash the server and potentially leak data.

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

A heap-based buffer overflow vulnerability in multiple OPC UA server products (KEPServerEX, ThingWorx Kepware Server, and related industrial connectivity solutions) allows remote attackers to crash the server and potentially leak sensitive data by sending a specifically crafted OPC UA message. The vulnerability exists in the message parsing component of the affected OPC UA servers.

MitigationApply vendor-provided patches to all affected versions; if patches are unavailable, implement network segmentation to restrict OPC UA communication to trusted clients only and monitor for indicators of compromise.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Industrial Gateway ServerApplication
Affected:= 7.66= 7.68.804
Kepware KepserverexApplication
Affected:= 6.0= 6.9
Opc AggregatorApplication
Affected:all versions
Thingworx Industrial ConnectivityApplication
Affected:all versions
Thingworx Kepware ServerApplication
Affected:= 6.8= 6.9
Kepserver EnterpriseApplication
Affected:= 6.6.504.0= 6.9.572.0
Top ServerApplication
Affected:>= 6.0, <= 6.9

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 installed OPC UA server product
    Check installed programs or running services for KEPServerEX, ThingWorx Kepware Server, Kepserver Enterprise, Top Server, OPC Aggregator, ThingWorx Industrial Connectivity, or Ge Industrial Gateway Server. Look in Program Files, Windows Services, or industrial software inventories.
    Affected if Any of these products are installed
  2. Determine the installed version
    Open the product's About or Help dialog, check the Windows Programs list, or examine the executable's file properties (right-click the main .exe file and select Properties > Details). Compare the version number to the affected ranges.
    Affected if Version matches: GE Industrial Gateway Server 7.66 or 7.68.804; Kepserverex 6.0-6.9; OPC Aggregator any version; ThingWorx Industrial Connectivity any version; ThingWorx Kepware Server 6.8-6.9; Kepserver Enterprise 6.6.504.0-6.9.572.0; Top Server 6.0-6.9
  3. Verify OPC UA server interface is enabled
    Check the product's runtime configuration, server settings, or channel properties to confirm the OPC UA server interface is enabled and listening on a UA port (typically 49320 or similar). This is often found in the project's runtime settings or server configuration pane.
    Affected if OPC UA server interface is enabled and configured to accept connections
  4. Confirm the service is running and exposed
    Check Windows Services or the product's runtime status to verify the OPC UA server process is active. Use netstat or the product's diagnostic tools to confirm it is listening on a network port accessible to clients.
    Affected if The OPC UA server service is running and bound to a reachable network interface

Your environment is affected if you have any of the listed products installed, the version falls within the affected ranges, and the OPC UA server interface is enabled and running.

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.

From vendor data
Upgrade available Upgrade to a release after 6.9
Interim mitigation

Apply vendor-provided patches to all affected versions; if patches are unavailable, implement network segmentation to restrict OPC UA communication to trusted clients only and monitor for indicators of compromise.

Fix this in Industrial Gateway Server Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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