Skip to content
Fencer Intel
low 3.3

CVE-2019-13511 json

Rockwell Automation Arena Simulation Software versions 16.00.00 and earlier contain an INFORMATION EXPOSURE CWE-200.

published 7y ago modified 4mo ago also EUVD-2019-4966

cvss
3.3
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
5.8%
EPSS 5.8% chance of exploitation in 30 days, percentile 93%
public exploits
0
none known

Summary

Rockwell Automation Arena Simulation Software versions 16.00.00 and earlier contain an INFORMATION EXPOSURE CWE-200. A maliciously crafted Arena file opened by an unsuspecting user may result in the limited exposure of information related to the targeted workstation.

Is CVE-2019-13511 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-19-213-05 updated cvss 3.3

Rockwell Automation Arena Simulation Software (Update B)

  • Rockwell Automation Arena Simulation Software for Manufacturing Cat. 9502-Ax <= 16.00.00
    affected: mitigation “Rockwell Automation has released Version 16.00.01 of Arena Simulation Software to address the reported vulnerabilities.” 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

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

CVSS scores

assigned by version score vector
NVD 3.1 3.3 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:P/I:N/A:N

Affected products

  • n/a Rockwell Automation Arena Simulation Software versions 16.00.00 and earlier

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
  • CWE-416 Use After Free

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.