Skip to content
Fencer Intel
high 7.3

CVE-2020-12028 in the critical feed json

Rockwell Automation FactoryTalk View SE

published 6y ago modified 4mo ago also EUVD-2020-4344

cvss
7.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
53.0%
EPSS 53.0% chance of exploitation in 30 days, percentile 98%
public exploits
1
Metasploit

Summary

In all versions of FactoryTalk View SEA remote, an authenticated attacker may be able to utilize certain handlers to interact with the data on the remote endpoint since those handlers do not enforce appropriate permissions. Rockwell Automation recommends enabling built in security features found within FactoryTalk View SE. Users should follow guidance found in knowledge base articles 109056 and 1126943 to set up IPSec and/or HTTPs.

Is CVE-2020-12028 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-20-170-05 updated cvss 7.3

Rockwell Automation FactoryTalk View SE

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

Timeline

  1. First public exploit (Metasploit exploit/windows/scada/rockwell_factorytalk_rce)
  2. Published

Exploit prediction

53.03% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

CVSS scores

assigned by version score vector
CNA 3.1 7.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N
NVD 3.1 8.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
NVD 2.0 5.5 AV:N/AC:L/Au:S/C:P/I:P/A:N

Affected products

  • Rockwell Automation FactoryTalk View SE

Classification

Weakness
  • CWE-264 Permissions, Privileges, and Access Controls
  • CWE-306 Missing Authentication for Critical Functionality

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.