Code execution via out-of-bounds DOE file write
Published Dec 19, 2024 · Updated Dec 20, 2024
Out-of-bounds write in Rockwell Automation Arena Simulation 16.20.07 and earlier allows attackers to execute code via a crafted DOE file. The 32-bit edition writes beyond allocated memory while parsing a DOE model file; Rockwell identifies the affected code only as a third-party component. A legitimate user must open the crafted file, after which attacker-controlled code executes with that user's application privileges.
Summary
What happened
Out-of-bounds write in Rockwell Automation Arena Simulation 16.20.07 and earlier allows attackers to execute code via a crafted DOE file. The 32-bit edition writes beyond allocated memory while parsing a DOE model file; Rockwell identifies the affected code only as a third-party component. A legitimate user must open the crafted file, after which attacker-controlled code executes with that user's application privileges.
The record
- CVE
- CVE-2024-12672
- Published
- Dec 19, 2024
- Updated
- Dec 20, 2024
- Vendor
- Rockwell Automation
- Product
- Arena Simulation
- Classifications
- CWE-1395, CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 19, 2024CVE publishedPublication date reported by the CVE source.
- Dec 20, 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=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