Code execution via uninitialized memory in DOE parser
Published Dec 5, 2024 · Updated Dec 6, 2024
Improper initialization in Rockwell Automation Arena Simulation 16.20.00 and earlier allows attackers to execute code via a crafted DOE file. The DOE file parser accesses memory before initializing it, allowing attacker-controlled file contents to influence code execution in the current process. Exploitation requires a legitimate user to open the malicious file, and the resulting code runs with that user's process privileges.
Summary
What happened
Improper initialization in Rockwell Automation Arena Simulation 16.20.00 and earlier allows attackers to execute code via a crafted DOE file. The DOE file parser accesses memory before initializing it, allowing attacker-controlled file contents to influence code execution in the current process. Exploitation requires a legitimate user to open the malicious file, and the resulting code runs with that user's process privileges.
The record
- CVE
- CVE-2024-11158
- Published
- Dec 5, 2024
- Updated
- Dec 6, 2024
- Vendor
- Rockwell Automation
- Product
- Arena Simulation
- Classifications
- CWE-665, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 5, 2024CVE publishedPublication date reported by the CVE source.
- Dec 6, 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=0 <16.20.00
- Affected versionversion=All versions 16.20.00 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