dbcve.org
Opc Ua TunnellerApplication · Honeywell

CVE-2020-27297

CRITICAL · 9.8 CVSS v3.1 Published 2021-01-26
Fix available
A fix is available. Upgrade to 6.3.0.8233 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
The affected product is vulnerable to a heap-based buffer overflow, which may allow an attacker to manipulate memory with controlled values and remotely execute code on the OPC UA Tunneller (versions prior to 6.3.0.8233).

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

Heap-based buffer overflow in OPC UA Tunneller versions prior to 6.3.0.8233 allows remote attackers to manipulate heap memory with controlled values, enabling remote code execution.

MitigationUpdate OPC UA Tunneller to version 6.3.0.8233 or later to remediate the vulnerability.

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
Opc Ua TunnellerApplication
Affected:< 6.3.0.8233

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. Locate Honeywell OPC UA Tunneller installation
    Search for OPC UA Tunneller files on the system using file explorer or command-line tools (e.g., find command, directory listings). Look for directories or executables containing 'OPC UA Tunneller' or 'OpcUaTunneller' in their name.
    Affected if The software is found on the system, proceed to version check.
  2. Determine installed version
    Right-click the main executable or look for a version property in the program's directory. Common locations include the installation folder, program files, or the bin directory within the installation path. Check for a version resource, readme file, or version info displayed in the application.
    Affected if A version number is identified and is less than 6.3.0.8233, proceed to confirm the vulnerability applies.
  3. Verify version is within vulnerable range
    Compare your identified version number against the affected range: any version prior to 6.3.0.8233 is vulnerable. This includes version 6.3.0.8232, 6.2.x, 6.1.x, 6.0.x, and earlier releases.
    Affected if The installed version is lower than 6.3.0.8233, the environment is affected by this CVE.
  4. Confirm OPC UA Tunneller is in use
    Check if the OPC UA Tunneller service or process is actively running on the system. Look for processes named 'OpcUaTunneller', 'OPC UA Tunneller', or related services in Task Manager or system process lists.
    Affected if The service or process is running and the version is below 6.3.0.8233, the vulnerability is exploitable in this environment.

If the installed version of Honeywell OPC UA Tunneller is lower than 6.3.0.8233, the environment is affected by this heap-based buffer overflow vulnerability.

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
Upgrade available Upgrade to 6.3.0.8233 or later
Fixed in 6.3.0.8233
Interim mitigation

Update OPC UA Tunneller to version 6.3.0.8233 or later to remediate the vulnerability.

Recommended fix Moderate confidence

6.3.0.8233

  1. 1. Identify the current version of OPC UA Tunneller installed in your environment
  2. 2. Download OPC UA Tunneller version 6.3.0.8233 or later from the official vendor source
  3. 3. Review the vendor release notes for version 6.3.0.8233 to understand changes and requirements
  4. 4. Create a backup of the current OPC UA Tunneller configuration and data
  5. 5. Stop the OPC UA Tunneller service before upgrading
  6. 6. Install version 6.3.0.8233 following the vendor's installation documentation
  7. 7. Restore the configuration from the backup if needed
  8. 8. Restart the OPC UA Tunneller service
Caveat Review vendor release notes for any configuration or compatibility changes between your current version and 6.3.0.8233

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

Fix this in Opc Ua Tunneller Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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