Code execution via uninitialized DOE parser memory
Published Dec 19, 2024 · Updated Mar 20, 2025
Code execution in Rockwell Automation Arena Simulation 16.20.06 and earlier allows attackers to run code when a user opens a crafted DOE file. The DOE parser accesses memory for a variable before initializing it, allowing file-controlled parsing state to corrupt execution. Exploitation requires a legitimate user to open the malicious file, and resulting code runs in the context of the Arena process.
Summary
What happened
Code execution in Rockwell Automation Arena Simulation 16.20.06 and earlier allows attackers to run code when a user opens a crafted DOE file. The DOE parser accesses memory for a variable before initializing it, allowing file-controlled parsing state to corrupt execution. Exploitation requires a legitimate user to open the malicious file, and resulting code runs in the context of the Arena process.
The record
- CVE
- CVE-2024-11364
- Published
- Dec 19, 2024
- Updated
- Mar 20, 2025
- Vendor
- Rockwell Automation
- Product
- Arena Simulation
- Classifications
- CWE-908, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 19, 2024CVE publishedPublication date reported by the CVE source.
- Mar 20, 2025Record 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=All versions 16.20.06 and prior
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