Factorytalk Linx vulnerabilitiesRanked by how likely they are to be used.
Factorytalk Linx is made by Rockwellautomation. We track 14 published vulnerabilities listed under that exact name, across 9 versions. None of them is on the list of flaws known to be exploited today. Rockwellautomation lists newer releases under their own names, such as Factorytalk Linx Gateway, so check those pages too.
We keep watching the known-exploited list.
Is Factorytalk Linx listed under other names? Yes.
Rockwellautomation also lists Factorytalk Linx under more specific names, such as Factorytalk Linx Gateway. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.
Which Factorytalk Linx vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Factorytalk Linx's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Factorytalk Linx flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 45%CVE-2020-5802High
An attacker-controlled memory allocation size can be passed to the C++ new operator in RnaDaSvr.dll by sending a specially crafted ConfigureItems message to TCP port 4241.
- 30%CVE-2020-5801High
An attacker can craft and send an OpenNamespace message to port 4241 with valid session-id that triggers an unhandled exception in CFTLDManager::HandleRequest function in RnaDaSvr.dll, resulting in process termination.
- 15%CVE-2023-29464Critical
FactoryTalk Linx, in the Rockwell Automation PanelView Plus, allows an unauthenticated threat actor to read data from memory via crafted malicious packets.
- 6.8%CVE-2020-27251Critical
A heap overflow vulnerability exists within FactoryTalk Linx Version 6.11 and prior.
- 4.8%CVE-2020-5806Medium
An attacker-controlled memory allocation size can be passed to the C++ new operator in the CServerManager::HandleBrowseLoadIconStreamRequest in messaging.dll.
- 3.9%CVE-2020-27255High
A heap overflow vulnerability exists within FactoryTalk Linx Version 6.11 and prior.
- 1.9%CVE-2020-27253High
A flaw exists in the Ingress/Egress checks routine of FactoryTalk Linx Version 6.11 and prior.
Running Factorytalk Linx? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
An attacker-controlled memory allocation size can be passed to the C++ new operator in RnaDaSvr.dll by sending a specially crafted ConfigureItems message to TCP port 4241. This will cause an unhandled exception, resulting in termination of RSLinxNG.exe. Observed in FactoryTalk 6.11. All versions of FactoryTalk Linx are affected.
- Matched to
- Factorytalk Linx on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 14 published vulnerabilities listed under the name Factorytalk Linx, across 9 versions.
None of Factorytalk Linx's vulnerabilities is on the list of flaws known to be exploited today.
Rockwellautomation also lists Factorytalk Linx under more specific names, such as Factorytalk Linx Gateway. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.
Create a Precursor Intelligence account and track Factorytalk Linx. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.