Code execution via DOE file type confusion
Published Jan 27, 2020 · Updated Aug 4, 2024
Type confusion in Rockwell Automation Arena Simulation Software 16.00.00 and earlier allows remote attackers to execute code via a crafted DOE file. The DOE parser fails to validate user-supplied data before interpreting it as an incompatible type, enabling memory corruption in the current process. Exploitation requires a user to open the file; successful attacks can compromise the workstation, while failed attempts can crash Arena and lose unsaved data.
Summary
What happened
Type confusion in Rockwell Automation Arena Simulation Software 16.00.00 and earlier allows remote attackers to execute code via a crafted DOE file. The DOE parser fails to validate user-supplied data before interpreting it as an incompatible type, enabling memory corruption in the current process. Exploitation requires a user to open the file; successful attacks can compromise the workstation, while failed attempts can crash Arena and lose unsaved data.
The record
- CVE
- CVE-2019-13519
- Published
- Jan 27, 2020
- Updated
- Aug 4, 2024
- Vendor
- Rockwell Automation
- Product
- Arena Simulation Software
- Classifications
- CWE-843, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 27, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Versions 16.00.00 and earlier
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo