CVE-2020-5802 in the critical feed json
An attacker-controlled memory allocation size can be passed to the C++ new operator in RnaDaSvr.dll by sending a specially crafted Configur…
published 2020-12-29 5 y ago modified 2026-06-17 4 mo ago also EUVD-2020-26959
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 44.7%
- EPSS 44.7% chance of exploitation in 30 days, percentile 98%
- public exploits
- 0
- none known
Summary
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.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-21-028-01 updated cvss 7.5
Rockwell Automation FactoryTalk Linx and FactoryTalk Services Platform
-
Rockwell Automation FactoryTalk Linx software <= 6.20affected: mitigation “Rockwell Automation published PN1540 to inform users of the risk of these vulnerabilities and instruct users on the proper use of patches.” rockwellautomation.custhelp.com
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
Exploit prediction
44.70% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
Affected products
- n/a Rockwell FactoryTalk Linx
Classification
- Weakness
-
- CWE-770 Allocation of Resources Without Limits or Throttling
References
-
tenable.com
/security/research/tra-2020-71
third-party-advisory
Sources
- CVE List CVE-2020-5802
- NVD CVE-2020-5802
Fencer Vulns 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.