Code execution via corrupted model file
Published Mar 26, 2024 · Updated Aug 6, 2024
Memory corruption in Arena Simulation 16.00 through 16.20.02 allows context-dependent attackers to execute code via a corrupted model file. Rockwell Automation has not identified the affected parser or operation beyond memory corruption that triggers an access violation during file handling. Exploitation requires a user to open an attacker-supplied file, after which code runs on the Windows host with the application's privileges.
Summary
What happened
Memory corruption in Arena Simulation 16.00 through 16.20.02 allows context-dependent attackers to execute code via a corrupted model file. Rockwell Automation has not identified the affected parser or operation beyond memory corruption that triggers an access violation during file handling. Exploitation requires a user to open an attacker-supplied file, after which code runs on the Windows host with the application's privileges.
The record
- CVE
- CVE-2024-2929
- Published
- Mar 26, 2024
- Updated
- Aug 6, 2024
- Vendor
- Rockwell Automation
- Product
- Arena Simulation Software
- Classifications
- CWE-119, CAPEC-100, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 26, 2024CVE publishedPublication date reported by the CVE source.
- Aug 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=16 <=16.20.02
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