dbcve.org
Industrial Gateway ServerApplication · Ge

CVE-2020-27265

CRITICAL · 9.8 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 stack-based buffer overflow. Opening a specifically crafted OPC UA message could allow an attacker to crash the server and remotely execute code.

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 stack-based buffer overflow vulnerability exists in multiple OPC UA server products from various vendors. The flaw is triggered when processing a specifically crafted OPC UA message, allowing an attacker to overflow a stack buffer and potentially achieve remote code execution or crash the affected server.

MitigationApply available vendor patches or updates to all affected products. If patching is not immediately feasible, implement network segmentation and restrict OPC UA access to trusted clients only to reduce attack surface.

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
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 the installed OPC UA server product
    Inspect installed programs or running services to determine which OPC UA server is in use. Common product names include: GE Industrial Gateway Server, PTC Kepserverex, PTC OPC Aggregator, PTC Thingworx Industrial Connectivity, PTC Thingworx Kepware Server, Rockwellautomation Kepserver Enterprise, or Softwaretoolbox Top Server.
    Affected if Any of the listed products are installed and running as an OPC UA server
  2. Check the installed version number
    Use the product's UI, about dialog, or check the version in Windows Programs and Features. For command-line inspection, examine the executable properties or check registry keys if applicable to the product.
    Affected if Version matches the affected ranges: GE Industrial Gateway Server 7.66 or 7.68.804; PTC Kepserverex 6.0 through 6.9; PTC Thingworx Kepware Server 6.8 or 6.9; Rockwellautomation Kepserver Enterprise 6.6.504.0 through 6.9.572.0; Softwaretoolbox Top Server 6.0 through 6.9; or any version of PTC OPC Agg
  3. Verify OPC UA server functionality is enabled
    Check the product configuration for OPC UA server enablement status. This is typically found in the product's runtime or settings configuration where OPC UA protocols are activated.
    Affected if OPC UA server protocol is enabled and the product is listening for OPC UA connections
  4. Confirm network exposure of the OPC UA service
    Review network configuration and firewall rules to determine if the OPC UA server port (default 4840) is accessible from external or untrusted network segments.
    Affected if The OPC UA server port is exposed to untrusted network segments or the internet

A user is affected if they have any of the listed products installed with a version matching the affected ranges (or all versions for PTC OPC Aggregator and PTC Thingworx Industrial Connectivity) and the OPC UA server functionality is enabled.

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 available vendor patches or updates to all affected products. If patching is not immediately feasible, implement network segmentation and restrict OPC UA access to trusted clients only to reduce attack surface.

Fix this in Industrial Gateway Server Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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