Code execution via unvalidated CIM file length
Published Dec 7, 2022 · Updated Apr 16, 2025
Out-of-bounds write in GE CIMPLICITY 2022 and earlier allows remote attackers to execute arbitrary code through a crafted CIM file. The CIM file parser copies user-supplied data into a heap buffer without first validating its length, permitting memory corruption. Exploitation requires a user to visit a malicious page or open a malicious file and runs code in the current process context.
Summary
What happened
Out-of-bounds write in GE CIMPLICITY 2022 and earlier allows remote attackers to execute arbitrary code through a crafted CIM file. The CIM file parser copies user-supplied data into a heap buffer without first validating its length, permitting memory corruption. Exploitation requires a user to visit a malicious page or open a malicious file and runs code in the current process context.
The record
- CVE
- CVE-2022-3092
- Published
- Dec 7, 2022
- Updated
- Apr 16, 2025
- Vendor
- GE Digital
- Product
- CIMPLICITY
- Classifications
- CWE-787, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 7, 2022CVE publishedPublication date reported by the CVE source.
- Apr 16, 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=0 <=v2022
What conditions does exploitation require?
What is affected?
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