CVE-2020-27299
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 · uneditedThe affected product is vulnerable to an out-of-bounds read, which may allow an attacker to obtain and disclose sensitive data information or cause the device to crash 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 · moderate confidenceOPC UA Tunneller versions prior to 6.3.0.8233 contain an out-of-bounds read vulnerability that allows reading beyond allocated memory boundaries. This can enable an attacker to potentially obtain and disclose sensitive data from memory or cause the device to crash, resulting in denial of service.
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< 6.3.0.8233CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Locate the OPC UA Tunneller installationSearch for the Honeywell OPC UA Tunneller executable or service on the system. Common locations include C:\Program Files\Honeywell\ or C:\Program Files (x86)\Honeywell\, or check Windows Services for a service named 'OPC UA Tunneller' or similar.Affected if The software is not found or the product name does not match Honeywell OPC UA Tunneller.
-
Identify the installed versionRight-click the tunneller executable (commonly named OpcUaTunneller.exe or similar) and select Properties, then view the Details tab to see the File Version or Product Version. Alternatively, run 'wmic product where "name like '%OPC%UA%Tunneller%'" get version' in Command Prompt if available.Affected if The version displayed is lower than 6.3.0.8233.
-
Verify the service is running (if applicable)Open Services (services.msc) and locate the OPC UA Tunneller service. Check its status. If it is a command-line tool, check if the process is running via Task Manager.Affected if The service or process is actively running and the version is below 6.3.0.8233.
-
Check the actual tunneller configurationLocate the configuration files for the OPC UA Tunneller (typically in the installation directory or a config subfolder). Look for configuration files related to the tunneller component that handle UA connection forwarding.Affected if The tunneller is configured and actively handling UA connections, and the version is below 6.3.0.8233.
The system is affected if Honeywell OPC UA Tunneller is installed and the installed version is lower than 6.3.0.8233, regardless of whether the service is currently running.
Generated from the published advisory. Verify against your own configuration.
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 · scoped6.3.0.8233
Upgrade OPC UA Tunneller to version 6.3.0.8233 or later to remediate this vulnerability.
OPC UA Tunneller version 6.3.0.8233 or later
- 1. Identify the current version of OPC UA Tunneller installed in your environment
- 2. If the installed version is prior to 6.3.0.8233, download the updated OPC UA Tunneller version 6.3.0.8233 or later from the official Softing Industrial Automation or appropriate vendor source
- 3. Before applying the upgrade, review release notes for any specific installation requirements or prerequisites
- 4. Perform the upgrade following standard deployment procedures for your environment
- 5. After upgrading, verify that the new version is running and confirm the vulnerability is remediated
- 6. Document the upgrade for change management and compliance purposes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-27299 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-27299 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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