dbcve.org
Factorytalk Services PlatformApplication · Rockwellautomation

CVE-2020-6967

CRITICAL · 9.8 CVSS v3.1 Published 2020-03-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
In Rockwell Automation all versions of FactoryTalk Diagnostics software, a subsystem of the FactoryTalk Services Platform, FactoryTalk Diagnostics exposes a .NET Remoting endpoint via RNADiagnosticsSrv.exe at TCPtcp/8082, which can insecurely deserialize untrusted 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

FactoryTalk Diagnostics software exposes a .NET Remoting endpoint (RNADiagnosticsSrv.exe) on TCP port 8082 that insecurely deserializes untrusted data. This allows remote unauthenticated attackers to execute arbitrary code by sending malicious serialized .NET objects to the endpoint.

MitigationIsolate the affected system on a restricted network segment and block TCP/8082 at the firewall. Contact Rockwell Automation for patched versions or guidance on migrating away from the deprecated .NET Remoting architecture.

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
Factorytalk Services PlatformApplication
Affected:all versions

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 if FactoryTalk Services Platform is installed
    Check system for presence of Rockwell Automation FactoryTalk Services Platform by reviewing installed programs in Control Panel > Programs and Features, or check for FactoryTalk-related directories in C:\Program Files\Rockwell Software\
    Affected if FactoryTalk Services Platform appears in installed programs or related directories exist on the system
  2. Locate and verify RNADiagnosticsSrv.exe
    Search for the file RNADiagnosticsSrv.exe in the FactoryTalk installation directory, typically under C:\Program Files\Rockwell Software\FactoryTalk Services Platform\Diagnostics\ or similar paths
    Affected if RNADiagnosticsSrv.exe file exists on the system
  3. Verify if the Diagnostics service is running
    Open Windows Task Manager or use command 'tasklist | findstr RNADiagnosticsSrv' to check if RNADiagnosticsSrv.exe process is currently active
    Affected if RNADiagnosticsSrv.exe process is running as a service
  4. Check if TCP port 8082 is listening
    Use command 'netstat -an | findstr :8082' or run 'netsh interface tcp show global' to determine if port 8082 is open and listening on applicable network interfaces
    Affected if Port 8082 shows as LISTENING or ESTABLISHED in netstat output, indicating the .NET Remoting endpoint is exposed
  5. Confirm network accessibility of the vulnerable endpoint
    Use 'telnet localhost 8082' or 'Test-NetConnection -Port 8082 localhost' from external hosts to verify the port accepts connections from non-localhost sources
    Affected if Port 8082 is accessible from network hosts, meaning the deserialization endpoint accepts remote connections

If FactoryTalk Services Platform is installed with RNADiagnosticsSrv.exe running and TCP port 8082 is open and accessible, the system is vulnerable to CVE-2020-6967 remote code execution via insecure .NET Remoting deserialization.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Isolate the affected system on a restricted network segment and block TCP/8082 at the firewall. Contact Rockwell Automation for patched versions or guidance on migrating away from the deprecated .NET Remoting architecture.

Fix this in Factorytalk Services Platform Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing16.0 h
  • Review / QA8.0 h
48.0 hours of engineering $8,320
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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